Fork me on GitHub
#kaocha
<
2022-05-19
>
onetom12:05:45

https://clojurians.slack.com/archives/CCY2V0U6A/p1618607713056000?thread_ts=1618510748.047900&amp;cid=CCY2V0U6A is this still an issue, that i don't get profiling information, if i just use kaocha.repl/run?

onetom12:05:39

i see, i should have searched for kaocha.repl/run, but i only search the issues for profiling. sorry for the noise and thanks for the quick response!

plexus12:05:37

no worries, this is also on the kaocha-cloverage repo, I guess you were looking at the Kaocha repo? Probably not unfixable, but I don't expect it to be trivial either. Cloverage does some pretty special things, it's gonna take some figuring out how best to do this. Currently not super high on our priority list.

plexus12:05:07

Cloverage works by implementing its own loading-and-instrumenting logic, so it has to reload all your namespaces anyway.

onetom03:05:47

yes, that too, i was just searching on the lambdaisland/kaocha repo. we are not using cloverage. tried it on a former project, but it didn't bring enough benefits. or any benefits really.

onetom03:05:30

but at least it complicated and slowed down the testing feedback loop 😉

imre11:05:02

I ran into this implementing polylith-kaocha and ended up copying what kaocha's own -X entry point does: https://github.com/imrekoszo/polylith-kaocha/blob/master/components/kaocha-wrapper/src/polylith_kaocha/kaocha_wrapper/runner.clj#L37-L44

imre12:05:42

so I guess if one doesn't insist on using repl/run, it's doable