Is there a way to break down `test`s into phases/steps using some kotest semantics, purely for bette...

# kotest

[Kirill Zhukov]

Is there a way to break down `test`s into phases/steps using some kotest semantics, purely for better readability experience?

test("foo") {
  step("do something") {
    // ...
  }

  step("do something else") {
    // ...
  }
}

[Emil Kantis]

Does withClue match what you want?

[Klitos Kyriacou]

You can also use `FreeSpec`:

class MyTest: FreeSpec({
    "foo" - {
        "do something" {
            /...
        }
        "do something else" {
            /...
        }
    }
})

[Shervin]

Or BehaviourSpec with Given, When, Then + my favorite one: And ?

[sam]

FunSpec allows

context("foo") { 
  test("bar") {}
  test("baz") {}
}

[Kirill Zhukov]

withClue is what I was looking for 🙂

[Klitos Kyriacou]

While on the subject of withClue, sometimes I wish there was a way to add the text after the assertion instead of having to always put it before. For example, it would be nice if there was an "otherwise" like <actual> shouldBe <expected> otherwise "<actual> is the wrong value!". I think that would read nicer.

[sam]

Funny you say that because there's a ticket someone opened to "fix" it so its before on all assertions.

[Klitos Kyriacou]

I think that's a different issue (assuming you're referring to https://github.com/kotest/kotest/issues/3694?). I was talking about where the clue appears in the source code, not in the failure message.