<https://dev.to/kotest/kotest-release-4-3-2768>
# kotest
t
purely speculative, I did not try it yet, but shouldn’t
Copy code
val employees: List<Employee> = ...
employees.shouldBeSorted()
          shouldHaveSize(4)
          shouldContain(Employee("Sam", "Chicago"))
be
Copy code
val employees: List<Employee> = ...
employees.shouldBeSorted()
         .shouldHaveSize(4)
         .shouldContain(Employee("Sam", "Chicago"))
? in
Matchers return this
example
s
What's the difference
t
extra
.
in front of
should
for second and third expectation
s
Ahh yeah
Is this in the blog post
t
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)
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
s
Appreciate the heads up. I'll fix shortly
j
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
s
nice
wasn't my idea, it was sergei's, he did all the hard work
j
It's the feature I needed and never knew that I did, I'm super stoked on this! 🎉
😂 1