the docs for stringspec state that it does not sup...

# kotest

[christophsturm]

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]

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

[sam]

Correct

[christophsturm]

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]

and it seems to work.

[christophsturm]

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

[christophsturm]

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

[sam]

Yeah that is odd.

[sam]

Aren't you just going to migrate it to failfast 🙂

[christophsturm]

not on my second day 🙂

[sam]

oh new job 🙂

[sam]

yeah wait until 3rd day at least 😉

[christophsturm]

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]

btw, what is

@ExperimentalKotest
   open val concurrentSpecs: Int? = null

   @ExperimentalKotest
   open val concurrentTests: Int? = null

[sam]

It's the new in 4.4 concurrency support

[sam]

but it's marked experimental while we garner feedback

[christophsturm]

is it for running specs inside a class concurrently?

[christophsturm]

and is it documented anywhere?

[sam]

yes and yes

[christophsturm]

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

[sam]

https://kotest.io/docs/framework/concurrency.html

[sam]

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

[christophsturm]

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

[sam]

those docs are hidden and probably slightly out of date

[sam]

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

[christophsturm]

ok and concurrencyMode is gone?

[sam]

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]

yea

[christophsturm]

ah ok

[sam]

concurrencyMode was never released

[christophsturm]

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

[sam]

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

[christophsturm]

so spec = context in that context

[sam]

spec = class file

[sam]

everything inside a spec is a test

[christophsturm]

cool

[christophsturm]

so if i set both to MaxInt i get unlimited concurrency?

[sam]

yep, and we have a constant for that, MaxConcurrency

[sam]

now of course, increasing those doesn't mean parallel

[sam]

you also need to increase the threads

[sam]

because threads is orthogonal to concurrent dispatching of coroutines

[christophsturm]

override val parallelism = 8 ?

[sam]

yep you an do that

[sam]

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

[sam]

remember these are all marked with @ExperimentalKotest for a reason 🙂

[christophsturm]

ok

[christophsturm]

any known problems?

[sam]

not so far

[christophsturm]

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

[sam]

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

[christophsturm]

thanks, that setting has been confusing me for quite some time