Hello Kotest magicians, I'm looking into the Kotest and trying to understand the best practices The Groovy Spock is the main testing framework for me at the moment, and I like it a lot. However, the groovy dependencies generate an unreasonable level of discomfort in my kotlin projects. Therefore I'm looking for a replacement and Kotest looks awesome and super promising. But I can find good examples for Data Driver Testing with Kotest. https://spockframework.org/spock/docs/1.0/data_driven_testing.html My perfect scenario will be the next one: • Keep the usage of

Given When Then

- it is covered by

BehaviorSpec

• Usage of something similar to

Data Tables

from Spock but in Kotest -

io.kotest.data.forAll

looks similar Can anyone please point me to any well written example? Because I end-up with a

callback hell

all the time Thank you in advance!

Do you have an example of what you have at the moment

Of course! Unfortunately I had to remove meaningful parts of the test body, however, the skeleton is the same

class SomeDataTest : BehaviorSpec({

    Given("...") {
        When("...") {
            forAll(
                table(
                    headers("frontPageKey", "pageUrl", "expected result"),
                    row(null, null, null),
                    row("key", "key", "something"),
                    row(null, "something", null),
                )
            ) { key1: String?, key2: String?, expectedResult: String? ->
                Then("...") {
                    
                }
            }
        }
    }
})

Ok, that looks right. And what is the issue exactly - that you think it's a bit verbose ?

I think he means it's too much nesting, contrary to the linear get when then in spock

Ah I see. Well you don't have to use behavior spec, can use fun spec, and with the latest data driving stuff in 4.4 you don't even need to have any nesting at all.

I've seen some libs that tried given("") { }.when("") { }.then("") { } kind of style with less nesting, but I'm not sure it would be possible in kotest

@dave08 yes, you pointed the main problem here. The BehaviorSpec has over too much nesting level especially with additional `And`(s)

The truth is, that if the main thing you need to identify the test is

"maximum of two numbers"

, then you could just do:

init {
   test("maximum of two numbers") {
       // given -- maybe the table here?

       // when -- run the SUT

       // use the forAll
    }
}

with those comments there to delimit the sections, but then it just boils down to JUnit with an additional bell-and-whistle of forAll...

Thank you for your suggestions @dave08, I will try to play a bit more with Kotest in the minor projects, however unfortunately I feel Spock will remain a company-wise standard