Gáspár Nagy

From Budapest, Hungary, Gáspár Nagy is the creator of SpecFlow, the most widely used BDD framework for .NET; regular conference speaker; blogger; editor of the BDD Addict monthly newsletter, and co-author of the books “Discovery: Explore behaviour using examples” and “Formulation: Document examples with Given/When/Then“. Gáspár is also an independent coach, trainer and test automation expert focused on helping teams implementing BDD and SpecFlow. He has more than 20 years of experience in enterprise software development as he worked as an architect and agile developer coach.


22 November

Testing tools and techniques are flourishing nowadays. We have more and more of them in our toolbelt that we can use to improve software quality. But probably you have also experienced that while these tools and techniques work very well, on a team or product level our quality expectations are not met, even if we spend a lot of time on testing.
The problem might be that these efforts are not coordinated and they do not on the right things. A typical product has areas where they are tested with different techniques redundantly, while there are untested areas. A good testing strategy is structured on the basis of what we want to achieve and not of how we do that. Creating such a strategy should be specific to the project context and created by the entire team collaboratively. Is it difficult? It’s not as difficult as you would think.
In this talk, we will examine problems that have arisen due to a missing strategy and some approaches how you can map out an appropriate testing strategy. We will check out a few commonly used testing tools and techniques and try to match them to our approach. We will also try to unveil the true value of the automation testing pyramid.
Quality is not only testing! It is also about strategy!

21 November - Half Day

Behaviour Driven Development is an agile development technique that improves collaboration between technical and non-­technical members of the team, by exploring the problem using examples. These examples then get turned into executable specifications, often called ‘scenarios’. The scenarios should be easy to read by all team members, but writing them expressively is harder than it looks!
In this workshop you will learn how to write expressive BDD scenarios. We’ll start by giving you a very brief introduction to BDD/ATDD. You’ll then be introduced to different writing styles by reviewing pre­pared scenarios. Finally, you’ll get a chance to write your own scenarios based on examples that we’ll bring along.
We’ll be using Gherkin, the syntax used by Cucumber and SpecFlow ­ but you won’t need a computer. And, you’ll leave with a checklist of tips that you can use the next time you sit down to write a scenario.