Dustin Getz

Premise: we want to run RCF in a CI configuration. Problem: not the CI pipeline but feedback loop latency The issue is: we want `(clojure.test/run-tests 'foo)` to work at the...

It's not a _blocker_ because you can run the tests on a file-by-file basis, or you can use a shell script for CI. But that's a worse experience.

Why would tests work at the REPL but not in CI? Because you changed a bunch of namespaces and now we want to run everything one more time to be...

Thanks, we had not seen this yet

Directly configuring :timeout works: ```clojure (tests {:timeout 100} hyperfiddle.rcf/*timeout* := 100 (defn setTimeout [f ms] (js/setTimeout ms f)) (rcf/! 1) (setTimeout 10 (fn [] (rcf/! 2) (setTimeout 200 (fn []...

The issue is that humane-test-output is meant to self-install on require. For RCF to support this, RCF must be changed to support clojure.test/assert-expr, which is the multimethod hook humane-test-output uses...

No it breaks the natural REPL experience

Better example: ```clojure (tests "REPL bindings work" (keyword "a") := :a (keyword "b") := :b (keyword "c") := :c *1 := :c *2 := :b *3 := :a *1 :=...

> First of all it's impossible to align code correctly with it @xificurC can you give me an example of what you mean by this?

Thank you! You're right, we do write trailing := a bit. So many people are asking for this that we are possibly willing to reconsider. So if I can follow...