Ranie Jade Ramiso

> Document that @Tag and filter by class name doesn't work with Spek Or eventually support filter by class name and/or @Tag I think we need to disambiguate in the...

AFAIK JUnit 5's dynamic tests doesn't support groups. `ExecutorService`s will just complicate things, since tests are created dynamically we need a reliable way to tell Spek that all tests are...

@artem-zinnatullin Why is that?

Ahh, yep definitely. What I meant was you can do more complex test setup with coroutines compared to the control flows (which we currently have).

One thing I can think via extensions that allow to tap into Spek's lifecycle. Been playing around with extending Spek, here's what I have so far https://github.com/JetBrains/spek/blob/master/spek-junit-platform-engine/src/test/kotlin/org/jetbrains/spek/engine/ExtensionTest.kt.

@corlaez When this ticket was created the plan is to have test scope level parallelism, not just class level. I might have to re-think this a bit further - the...

@CzBiX yes, it's still in our backlog.

I'm not really keen on adding new methods, we could just add a parameter to the `afterEachTest` blocks that contains information about the test (description, failure, etc..).

@peterholak this will be fixed in the `2.0.3` release. > it is not possible to create a run configuration for all tests, the Path field is not editable Known issue,...

@JackED42 see `InstanceFactory` and `@CreateWith` since most likely you will need to use custom class loaders.