the docs for stringspec state that it does not support neste

Question

the docs for stringspec state that it does not support nested tests is that still true <https github com kotest kotest blob master doc styles md string spec>

dave08 · Answer

It seems that stringspec with nesting is the whole point of freespec

sam · Answer

Correct

christophsturm · Answer

in a new project i took over that has a kotest test suite they use nested string specs that look like this ``` class FetcherSpec StringSpec init a public key fetcher should return the public key ```

christophsturm · Answer

and it seems to work

christophsturm · Answer

but I m not really sure if its really always doing the right thing

christophsturm · Answer

it seems that thats WordSpec syntax but it also works with StringSpec

sam · Answer

Yeah that is odd

sam · Answer

Aren t you just going to migrate it to failfast slightly smiling face

christophsturm · Answer

not on my second day slightly smiling face

sam · Answer

oh new job slightly smiling face

sam · Answer

yeah wait until 3rd day at least wink

christophsturm · Answer

but i had an idea for a failfast feature already something like git bisect but it runs all combinations of tests simultanously to show you which ones share state

christophsturm · Answer

btw what is ``` ExperimentalKotest open val concurrentSpecs Int = null ExperimentalKotest open val concurrentTests Int = null```

sam · Answer

It s the new in 4 4 concurrency support

sam · Answer

but it s marked experimental while we garner feedback

christophsturm · Answer

is it for running specs inside a class concurrently

christophsturm · Answer

and is it documented anywhere

sam · Answer

yes and yes

christophsturm · Answer

its the only two options in the config object that have no kdoc

sam · Answer

sam · Answer

Maybe this awesome feature is what gets you onto the kotest team joy

christophsturm · Answer

hmm that page mentions concurrencyMode and that seems to be no longer present in AbstractProjectConfig

sam · Answer

those docs are hidden and probably slightly out of date

sam · Answer

basically concurrentSpecs concurrentTests set how many specs tests should be launched at the same time

christophsturm · Answer

ok and concurrencyMode is gone

sam · Answer

so if you set it to 4 2 you d get 4 specs launched and inside each spec 2 tests would be launched concurrently

sam · Answer

yea

christophsturm · Answer

ah ok

sam · Answer

concurrencyMode was never released

christophsturm · Answer

for me it was a bit confusing because for me spec is a synonym for test

sam · Answer

It was around in a snapshot while I worked on this concurrency stuff but settled on the two flags

christophsturm · Answer

so spec = context in that context

sam · Answer

spec = class file

sam · Answer

everything inside a spec is a test

christophsturm · Answer

cool

christophsturm · Answer

so if i set both to MaxInt i get unlimited concurrency

sam · Answer

yep and we have a constant for that MaxConcurrency

sam · Answer

now of course increasing those doesn t mean parallel

sam · Answer

you also need to increase the threads

sam · Answer

because threads is orthogonal to concurrent dispatching of coroutines

christophsturm · Answer

`override val parallelism = 8`

sam · Answer

yep you an do that

sam · Answer

you can even provide your own spec launcher which creates the coroutines

sam · Answer

remember these are all marked with ExperimentalKotest for a reason slightly smiling face

christophsturm · Answer

ok

christophsturm · Answer

any known problems

sam · Answer

not so far

christophsturm · Answer

do i also have to set the Allow parallel run checkbox in the run config or do the settings override that

sam · Answer

that just means allowing you to run more than one run at teh same time and is nothing to do with kotest

christophsturm · Answer

thanks that setting has been confusing me for quite some time