Whenever a single test fails, gradle (or kotest?) ...
# kotest
a
Whenever a single test fails, gradle (or kotest?) reports two failures. It seems like once there is a failure, "doubles up" as
executionError
as if that was an additional failing test. Any idea why? (2 actually failing tests gets reported as 3 failures)
s
Which spec style
p
I see this as well using StringSpec when running in gradle.
a
FreeSpec
s
I can't see the executionError in your screenshot mind