Hi! I generally run kaocha with --watch, do some development, and when I’m done, type CTRL-C (sending SIGINT, I believe). Starting with release vhttps://github.com/lambdaisland/kaocha/releases/tag/v1.79.1270 I’ve started to see the following stacktrace when I exit:

^CException in exit (SIGINT/ShutDown) handler
#error {
 :cause "java.io.OutputStreamWriter cannot be cast to java.io.PrintStream"
 :via
 [{:type java.lang.ClassCastException
   :message "java.io.OutputStreamWriter cannot be cast to java.io.PrintStream"
   :at [kaocha.api$run$fn__3265$fn__3269$fn__3270$on_exit__3271 invoke "api.clj" 125]}]
 :trace
 [[kaocha.api$run$fn__3265$fn__3269$fn__3270$on_exit__3271 invoke "api.clj" 125]
  [kaocha.api$run$fn__3265$fn__3269$fn__3270$fn__3273$fn__3274$fn__3275 invoke "api.clj" 141]
  [kaocha.api$run$fn__3265$fn__3269$fn__3270$fn__3273$fn__3274 invoke "api.clj" 140]
  [kaocha.api.proxy$java.lang.Object$SignalHandler$d8c00ec7 handle nil -1]
  [sun.misc.Signal$1 run "Signal.java" 212]
  [java.lang.Thread run "Thread.java" 750]]}

Thanks @grzm for spotting this, it would be really helpful if you could file this through the issue tracker.

@eugen.stan I believe there's documentation for creating a new test types. See https://cljdoc.org/d/lambdaisland/kaocha/1.83.1314/doc/9-extending Not saying it's exhaustive but it should get you started. It would be helpful to look at the implementation of existing types as well.