BDD in Kotlin: The Options, and How to Choose
· 9 min read
I've been writing acceptance tests on the JVM since 2009. Concordion first, then Cucumber on the teams around me, then Yatspec, and eventually I wrote my own.
Yatspec's trick was that it read the test method itself. You wrote:
given(orchestration.sends(anOrder));
and the report showed:
Given orchestration sends an order
No feature file, no step definitions, no glue. The test was the sentence.
That's the idea I've been chasing ever since, and it's why I wrote Kensa. So this is a biased guide. It's also a short one.