Gaspar is the creator and main contributor of SpecFlow, a regular conference speaker, blogger (http://gasparnagy.com), editor of the BDD Addict monthly newsletter (http://bddaddict.com), and co-author of the BDD Books series ("Discovery - Explore behaviour using Examples"; "Formulation - Express examples using Given/When/Then" (http://bddbooks.com)).
Gaspar is an independent coach, trainer, and test automation expert focusing on helping teams implement BDD and SpecFlow. Gaspar has more than 20 years of experience in enterprise software development where he worked as an architect and agile developer coach.
He is an approved training provider of the Agile Testing Fellowship: he is a trainer of the Agile Testing course developed by Janet Gregory and Lisa Crispin.
Gaspar has been developing a synchronization tool called SpecSync that integrates Gherkin-based scenarios into Azure DevOps (TFS). He is also working on a feature file editor tool called Deveroom, a new Visual Studio extension for SpecFlow.
Tue, September 20
2:00 pm - 3:00 pm
BDD Scenarios in a Testing & Traceability Strategy
Behaviour Driven Development (BDD) is becoming more and more popular nowadays. BDD, if done well, improves team collaboration and helps to get a better understanding of the requirements. The produced BDD scenarios can drive the development, but later they are going to serve as regression tests. However, BDD scenarios alone would not be enough to meet quality expectations, so the question remains: what is the role and purpose of these BDD-routed regression tests? How do they work together (or against) other test types?
There are no ready-to-use answers and recipes for these questions, although many teams try to read out answers from models like the test automation pyramid.
This talk is no different. Don’t expect canned answers from it. Instead, it shows how the testing and quality considerations have been made in the case of a real product by focusing on the following questions:
What kind of tests are needed? How to decide what is the right way to specify and test a concrete function?
What kind of feedback can we get from the different tests and how? Do they form a test automation pyramid?
How are the requirements expressed in BDD scenarios and how are they connected to the other development artifacts?
How can the impact of the test automation decisions be measured in reaction time, build quality or support tickets?
The talk discusses test automation and test architecture questions, but it is platform-agnostic and can be followed by attendees without coding skills as well.