<https://dev.to/kotest/kotest-release-4-3-2768>

# kotest

[sam]

https://dev.to/kotest/kotest-release-4-3-2768

[thanksforallthefish]

purely speculative, I did not try it yet, but shouldn’t

val employees: List<Employee> = ...
employees.shouldBeSorted()
          shouldHaveSize(4)
          shouldContain(Employee("Sam", "Chicago"))

be

val employees: List<Employee> = ...
employees.shouldBeSorted()
         .shouldHaveSize(4)
         .shouldContain(Employee("Sam", "Chicago"))

? in Matchers return this example

[sam]

What's the difference

[thanksforallthefish]

extra . in front of should for second and third expectation

[sam]

Ahh yeah

[sam]

Is this in the blog post

[thanksforallthefish]

yes. and btw, also Option to strip whitespace from test names seems a bit odd. The normal output and the removeTestNameWhitespace output looks the same. probably in the first one you mean to have an extra line (again, just guessing, never used multi-line method names)

[thanksforallthefish]

I just wanted to point out a couple of minor errors I saw in the blog post, which are probably obvious to everybody but better safe than sorry

[sam]

Appreciate the heads up. I'll fix shortly

[Jim]

Just want to point out that test case severity feature is 👌 I have a bunch of gradle machinery and test naming conventions to run a test if it's Smoke (Severe) or not (Normal) (essentially) for smoke tests since the severe suite is smaller and faster

[sam]

nice

[sam]

wasn't my idea, it was sergei's, he did all the hard work

[Jim]

It's the feature I needed and never knew that I did, I'm super stoked on this! 🎉