Cursive doesn’t do that, do you have another plugin installed which does that?

Oh, I want to hear what that plugin is

I guess they’re ligatures, which is a built-in feature these days: https://www.jetbrains.com/webstorm/guide/tips/font-ligatures/. But there are still things like this around: https://plugins.jetbrains.com/plugin/14736-ligatures-limited

I have a feeling there was also a more Clojure-specific one, but I can’t find it now.

I think you mean this one: https://plugins.jetbrains.com/plugin/8224-clojure-pretty-symbol

Thank you.

I am not aware that I am using some other plug in, will double check now...

yeah it was clojure pretty symbol doing it...Thanks

All those tests are in that module under the test folder, correct? I can’t see any reason why they wouldn’t be found. Is this a public project I could look at?

the schema-test is in the test folder, the rest ist in the src folder as https://github.com/hyperfiddle/rcf macros next to the implementation

the repo ist not public yet, but will be in the next days, I’ll let you know

I'm not convinced Cursive is able to discover those rcf tests

https://cursive-ide.com/userguide/testing.html says Currently the test integration only supports the default clojure.test

ok, fair point, rcf interacts with clojure.test, but if it actually generates clojure tests like deftest does, i don’t know

I guess I need to try with an own test macros what’s possible

I haven’t tried with rcf, but Dustin is a Cursive user, or at least was for a long time.

But I suspect that it might only look for tests under test roots, not source roots - I’d have to check the code for that though.

ok, I could test that hypothesis first (in my evening), if checking the code is too tedious

RCF macroexpands to deftest when a JVM flag is set, i don't see why Cursive shouldn't pick it up, the theory about Cursive not looking in src directory makes the most sense to me

> JVM flag is set curious

It was not our intended use case to integrate with clojure.test at dev time, RCF is meant to be used at the REPL like rich comment forms, the deftest generation is meant for CI use case (to get test runners, reporters, coverage plugins etc). However we've gotten a bit of feedback that people want to integrate RCF into their old workflows. So we may support that officially in the future

yea, I see why it’s no direct concern, because the main usecases CI and REPL are covered. I would still argue that it would feel very natural to have them show up next to the “normal” tests (where people will still likely implement long running or integration tests). It would also be handy for them to be respected in coverage report of the IDE, so that one could easily add tests where coverage is missing. But I’m still very happy without this working, so no worries. For now I’m going to test whether deftests in src will be picked up, and whether rcf tests in test will be picked up.

Ok, RCF tests are picked up in test folder by cursive, but fail. (They succeed when run with clj -M:test ; for config, see above.)

(tests                ; in my case schema_test.clj line 8
  "true is true"
  true := true)

Testing datomic-lacinia.schema-test
.java.lang.ClassCastException: class java.lang.String cannot be cast to class clojure.lang.Symbol (java.lang.String is in module java.base of loader 'bootstrap'; clojure.lang.Symbol is in unnamed module of loader 'app')
 at clojure.core$find_ns.invokeStatic (core.clj:4127)
    clojure.core$the_ns.invokeStatic (core.clj:4161)
    clojure.core$ns_name.invokeStatic (core.clj:4165)
    clojure.core$ns_name.invoke (core.clj:4165)
    cursive.tests.runner$eval577$report__22180__auto____584.invoke (run-tests8310960651276941006.clj:81)
    clojure.test$do_report.invokeStatic (test.clj:357)
    clojure.test$do_report.invoke (test.clj:351)
    datomic_lacinia.schema_test$fn__557.invokeStatic (schema_test.clj:8)
    datomic_lacinia.schema_test/fn (schema_test.clj:8)
    clojure.test$test_var$fn__9856.invoke (test.clj:717)
    ...

Interesting, when I add one deftest to a src namespace, the test is picked up and RCF tests are also run

I like how interactive RCF feels, but I see that simply using deftest next to the implementation in src can feel pretty similar. My solution:

(deftest- uppercase-first-test
  (is (= (uppercase-first "hellO") "HellO"))
  (is (= (uppercase-first "s") "S"))
  (is (= (uppercase-first "S") "S"))
  (is (= (uppercase-first "") ""))
  (is (= (uppercase-first nil) nil)))
;; instead of
(tests
  (lowercase-first "HellO") := "hellO"
  (lowercase-first "S") := "s"
  (lowercase-first "s") := "s"
  (lowercase-first "") := ""
  (lowercase-first nil) := nil)

That exception looks like a bug in Cursive, could you file an issue for that one and I’ll look at it?

yes, I can, will do 🙂

fyi https://github.com/cursive-ide/cursive/issues/2686

Great, thank you!