Hello peeps, inspired by @christophsturm and failfast, I’ve been hacking on Minutest again. I have a plan to create a (slightly) breaking v2.0, which can run all tests in a context in parallel. Combined with JUnit 5 parallel test running this has more than halved the time taken to run Minutests own test suite. I have few user questions. • Should Minutest 2 enable parallel test running by default? • At present I’m using a threadpool. Can anyone convince me that I should be using coroutines concurrency instead?

I think a threadpool is fine. I just used coroutines in failfast because i thought its less tied to the jvm.

Ah, that is a point. I’m trying to wean Minutest off the JVM, maybe I should go that way

Well tbh it probably shouldn't matter to the end user?. Go with threadpool for v2 and then update in a later version?

I’m wondering whether it matters that tests are suspend functions or not. I suppose with the DSL it’s largely hidden, but there are places where we return tests from functions, and their signature might change. Time for some experiments I think

i think with junit you can’t just have one long lasting coroutine context and execute the tests there