@dharrigan we have no plans or intention to further support midje, the recommended migration path is via fudje. Midje is a very weird animal and there's just no way to do it well.

Yeah, it's not well liked at our place, so we are going to start moving across to expectations...

I'm sorry we can't provide a better experience for midje, but it also seems there are better places to put our energy, given that folks are generally moving away from it.

Have you tried fudje? It should be a drop-in replacement that's clojure.test compatible, I'd be curious to hear if that's not your experience.

Yeah, totally understand.

Yeah, couldn't get fudje to work either

I'll have another look to see why

in general, or with kaocha? we do care about working with fudje, but there should not be much (if anything) for us to do, since they are based on clojure.test

Let me get back to you

I'll have to reattempt it again

ok 🙂

For the figwheel folks, it would be helpful to share your config, especially cljs compiler config. Contrary to shadow figwheel uses the vanilla compiler, and so figwheel projects should be able to use kaocha-cljs, but there might be compiler flags that interfere with how kaocha-cljs works. kaocha-cljs2 should be usable in any scenario, it's completely agnostic to how you compile or which runtime env you use, but (I'm aware) it's a PITA to set up. We do plan to do something about that.

The other issue with kaocha-cljs is that it's a pain to debug, because we rely on the cljs prepl which gives very little indication of what the problem is when things go wrong, but for simple setups it's still pretty useful, because it's so much simpler internally compared to kaocha-cljs2.

Please also note that the right place to report things is in the github issues.