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

What's the difference

extra

.

in front of

should

for second and third expectation

Ahh yeah

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)

Appreciate the heads up. I'll fix shortly

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

nice

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