does kotest support mapping like strikt? ```val subject = Pantheon.NORSE expectThat(subject) .get(...

# kotest

[christophsturm]

does kotest support mapping like strikt?

val subject = Pantheon.NORSE
expectThat(subject)
  .get(Pantheon::ruler) // reference to a property
  .get { toString() }   // return type of a method call
  .isEqualTo("Odin")

[sam]

subject.ruler shouldBe "Odin"

[sam]

That would be the equivalent for testing a single property

[MiSikora]

Will it convert ruler to a String or is toString() missing? Seems kind of spooky if it converts

[sam]

I assumed panthon.ruler was a string, so if it's not, then

subject.ruler.toString() shouldBe "Odin"

[christophsturm]

The difference is in the failure message.

[christophsturm]

With the strikt syntax you get something like expected pantheon.Norse to have ruler Odin.

[christophsturm]

I Guess I can just use strikt with kotest

[sam]

Yeah I see what you mean. The word "ruler" won't be present in the kotest error.

[sam]

I think the closest right now would be

withClue("greek ruler") {
   Pantheon.Greek.ruler() shouldBe "Zeus"
}

[sam]

Then your error would be something like

greek ruler
Expected :"Odin"
Actual   :"Zeus"

[sam]

https://kotest.io/clues/

[sam]

Or as you say, you don't have to use kotest assertions (or you can use them and strickt)

[christophsturm]

I’m right now using strikt and minutest, but I’m looking at kotest for the multiplatform support, and because its not junit dependent

[sam]

Right. The JVM support is currently on top of JUnit5, unless you use the experimental gradle plugin, then you can ditch junit completely. The kotest intellij plugin is junit free. Hopefully in 4.4 / 4.5 we can make the JUnit support 2nd class in favour of our native gradle support (the output is much better).

The JS support uses the mocha/karma runners (whichever one the JS plugin pulls down now).