Heuristics
You should always write Gherkin for the examples that you got our of the discovery phase. Writing the examples as Gherkin get's you new insights. You don't need to use it to automate.
When doing Behaviour-Driven Development we want to formalise our examples so we can possibly use these to automate them.
Read our latest news from Virtual DDD on any of these social networks!
How do you guide people toward different architectural approaches without simply imposing your solution?
How do you gain organizational support for uncertain architectural experiments?
How do you help people understand complex system changes when explanations and models aren’t landing?
Sorry, no results found!
Whoops... we couldn't find what you're looking for