A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
Writing #BDD tests in Gherkin sounds strange to you? Give it a try!
Yes, the underlying implementation that needs to be build will blow your mind.
You need to handle state between and map a linear model of test execution to
something which used to be hierarchical.
But what you get is a living document, which describes the capabilities of your
software, which is always up-to-date because it drives the tests.
And the best part: it is completely decoupled from any API and implementation,
so you get to refactor without having to keep track of all the corner cases you
had in your test suite.
It also can cover an entire system, not just one application, since it operates
on the user-level.
Not convinced? Using BDD your tests become a talk-piece for the Product Owner,
the Tester and you, the Developer:
http://blog.gdinwiddie.com/2009/06/17/if-you-dont-automate-acceptance-tests/