Ólafur Páll Geirsson

MUnit was primarily designed with non-async code in mind, where the parasitic execution context is not a problem. As long as stack traces remain clean for sync tests then I’m...

The reasoning why stdout is current only visible via mouse hover is that you normally don’t need println in worksheets, toplevel values are displayed as decorations by default. It’s certainly...

Thank you for reporting! It would be fantastic if we could add support for global fixtures. As discussed on Discord, one way to accomplish this is to extend `munit.Framework` and...

After a closer look I am concerned this is more tricky than I originally expected. It's easy to acquire global resources but it's tricky to know when to close them....

@keirlawson would you be able to try out the workaround above and report if it works for your codebase?

JUnit 5 has APIs that might make it possible to implement global fixtures, see `ExtensionContext.Store.CloseableResource` (https://junit.org/junit5/docs/5.3.0/api/org/junit/jupiter/api/extension/ExtensionContext.Store.CloseableResource.html). If the JVM shutdown hook works then we could design an MUnit API today...

Here's a draft of a global fixture API that we could expose in MUnit ```scala trait GlobalFixture[A] { def apply(): A def beforeAllTestSuites(): Future[Unit] def afterAllTestSuites(): Future[Unit] } ``` You...

@keirlawson did you enable `fork := true`?

@keirlawson Do you have a minimized example with cats-effect that I could try to reproduce?

@Daenyth the biggest challenge is coming up with a solution that works in all clients (IntelliJ, Gradle, Maven, sbt). This requirement means we need to somehow work within the JUnit...