“You can ask Kotest to run specs in parallel to ta...

# kotest

[christophsturm]

“You can ask Kotest to run specs in parallel to take advantage of modern cpus with several cores by setting the parallelism level (default is 1).. Tests inside a spec are always executed sequentially.” is that still true?

[christophsturm]

it seems running tests of one spec in parallel works only for single instance mode. why is that?

[christophsturm]

oh it seems the 4.4 version has a concurrency mode all. ist that going to work in instance per test mode?

[christophsturm]

i have now converted the test suite from one of my open source project from minutest to kotest and the tests look cleaner but it also takes 20 seconds instead of 8 seconds to run.

[christophsturm]

tried with the 4.4 snapshot. seems to also not run tests of one spec in parallel with instance per test.

[sam]

The 4.4 snapshot isn't ready yet but the new concurrency mode will run all tests in parallel not just specs. Also increase the parallelism settings for more threads

[sam]

What options does minutest have for concurrency and what's the link to your oss project. I'm away atm but I'll look when I'm back unless someone gets there first.

[christophsturm]

minutest just uses junit5, I’m using the parallel test running support from there

[sam]

Ok i see

[christophsturm]

thats my junit5 settings:

junit.jupiter.execution.parallel.enabled=true
junit.jupiter.execution.parallel.mode.default=concurrent

[christophsturm]

anyway if parallel test is planned for 4.4 I’m fine. its ok if the test suite is a bit slower for now

[sam]

Right but the current parallel mode is like junits. The new one is for coroutines and is an addition.

[sam]

Try setting env var kotest.parallelism to 4 or 8 or whatever

[christophsturm]

ok but junit seems to run tests inside one class in parallel while kotest does not.

[sam]

Yeah that's correct

[sam]

4.4 solves that too

[christophsturm]

i have this:

object KotestConfig : AbstractProjectConfig() {
    override val parallelism = Runtime.getRuntime().availableProcessors()

[sam]

It'll be released end of Nov

[christophsturm]

btw does the kotest gradle plugin support test reports? it seems there is a directory but no files in it

[sam]

It currently doesn't generate a report, but one will be added before the final release