Be the first to like this
I'm a developer. Similarly to other developers, I like dealing with technologies, architectures and solutions. I also like thinking about ways how to do this better and better. 2009 was the first time I encountered behavior driven development (BDD) -- as a tool to extend our agile development process to the entire project, including testers and product owners. BDD works like a glue that connects and reinforces agile methods you already use, making one plus one more than two.
BDD is still often regarded as a developer tool, so in this session, I would like to explain why Testers should care about BDD: What it is good for? What benefits you might expect? What is the role and responsibility of a tester in a BDD process? What is Gherkin and why do we care about vegetables at all?