Gáspár is an independent coach, trainer and test automation expert focusing on helping teams implementing BDD and SpecFlow. He has more than 18 years of experience in enterprise software development as he worked as an architect and agile developer coach.

Gáspár Nagy is the creator and main contributor of SpecFlow, regular conference speaker, blogger , editor of the BDD Addict monthly newsletter (http://bddaddict.com), co-author of the "BDD Books - Discovery: Explore behaviour using examples" and "BDD Books - Formulation: Express examples using Given/When/Then" .

For calculations the key examples are usually given as input-output tables that describe what expected calculation result the system should provide for the different input figures. As for these applications even small mistakes can quickly cause big losses, you better describe them in a way that both the business and the development team can understand them. In our projects most of the stakeholders use and like Excel for describing these and they are masters in doing this. Excel seems to be their DSL, so let's try to use it for generating automated tests!

10 years ago, Dan North first came up with the idea of BDD: using examples in conversation to explore the behaviour of systems, then carrying those examples into code. Since then, we've learnt a lot about how BDD works, how it works best, and how it can fail horribly! Even the most experienced BDD practitioners have learnt a lot from their failures... but what were they? And how are we failing now?

This talk will go through the issues we faced, the benefits we weren't realising, and how we changed to get the most out of the ATDD process.

A short time into our journey we started wonder if we were getting the benefits we originally envisaged.. With users still performing manual UAT, Audit still on our back, BA’s creating written procedure documents, and hundreds of tests written in an mix of styles…Clearly we weren't...

Day 1, 3 Apr starts 11:45 (Track 2) Getting the most out of ATDD - it's not just about writing tests! Peter Thomas and Debbie Evans

The tests that I see often remind me of a previous attempt to allow non-technical people to work with computers: Cobol. The features that helped to make it hugely successful, its "English syntax" and flat structure, are also barriers to abstraction and modularity--the techniques we need to cope with scale. Is writing everything out in full the only way we can get our point across?

Pete is active in the Agile/BDD community, speaking at meet-ups and conferences such as DDDX, BDDX and CukeUp. He co-authored SkillsMatter’s BDD Fast Track training course with Jenny Martin, and delivers this regularly.

What makes Pete tick is working with teams to discover and build the technology a business really needs. He's passionate about using collaborative approaches, and believes in the power of examples to give all relevant experts direct involvement in the software under development.

He's not really an expert on anything quite yet, but is working on it.

Pete and Phil will present some new tools for conversations that also readily translate into a highly usable living document that reports status and can be refactored easily.

This talk will show you how to be successful even with the oldest legacy projects out there through the usage of Agile processes and tools like Impact Mapping, Feature Mapping, Example Workshop, Story and Spec BDDs.

14:00

Let me tell you a story Seb Rose cukeup cucumber bdd user-stories Let me tell you a story

Seb Rose Day 1, 3 Apr starts 14:00 (Track 1) Watch now! In this session Seb will dissect a user story and find that they come in several shapes and sizes (that change throughout the project lifecycle). He will walk through the evolution of a feature file and see why so many of the text-book examples actually encourage bad habits. By the end of this session, attendees will walk away being able to describe the multiple uses of user stories as well as understand that misuse is commonplace. They will learn to recognise the value of user stories, appreciate the strengths and weaknesses of typical user story templates, as well as having gained in depth knowledge of the relationship between feature files and user stories. We hope also that attendees will have learnt to identify the shortcomings of typical text-book feature file examples. cukeup cucumber bdd user-stories About the speaker... Seb Rose Regular speaker at conferences and occasional contributor to software journals. Co-author of “BDD Books 1: Discovery” (Leanpub), lead author of “The Cucumber for Java Book” (Pragmatic Programmers), and contributing author to “97 Things Every Programmer Should Know” (O’Reilly). He blogs at cucumber.io and tweets as @sebrose ×