Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Narrative Acceptance Tests River Glide Antony Marcano
Semelhante a Narrative Acceptance Tests River Glide Antony Marcano (20)
Mais de Skills Matter
Mais de Skills Matter (20)
Último
Último (20)
Narrative Acceptance Tests River Glide Antony Marcano
- 1. Narrative Acceptance Tests A Behaviour Driven Approach Antony Marcano & Andy Palmer
- 2. Introduction
- 3. @AntonyMarcano http://antonymarcano.com @AndyPalmer http://andypalmer.com
- 9. Photo taken at www.tnmoc.org on site at www.bletchleypark.org.uk
- 10. Photo taken at www.tnmoc.org on site at www.bletchleypark.org.uk
- 11. Telephone Game We lose information by repeatedly switching between examples and abstractions http://www.brokenpicturetelephone.com/
- 12. Example Driven Approaches Why not just use the same examples for the whole process? The developers might even preserve the language of the business domain
- 13. 2009 Antony Marcano 13
- 14. Example Driven Approaches Common attributes: Desired behaviour is expressed as a concrete example The example is evaluated against the product, demonstrating the absence of the behaviour The behaviour is implemented The example is re-evaluated to determine if the correct behaviour has been implemented Such as: ATDD, TDD, BDD
- 16. User Stories are elaborated with Examples For each story likely to be worked on in next iteration Have a conversation Customer, Developer & Tester Discuss examples & summarise on back of story card Or, one card per example
- 17. Implement story (TDD with unit tests) test should pass Have a conversation For each Example noted earlier Express the example as automated acceptance test Test should fail When all tests pass, story is done (almost) During the iteration
- 18. Given-When-Then Given-When-Then Given some initial context (the givens), When an event occurs, then ensure some outcomes. For example… http://dannorth.net/introducing-bdd
- 22. A Place To Start As a Team Member I want a place to start So that I know that the software is running
- 23. Given thatthe FitNesse wiki was able to start for the first time When the Project Team Member attempts to go to the Home Page Then the content of the Home Page for the Project Team Member should be "Welcome to the Wonderful World of FitNesse!"
- 24. Given that the FitNesse wiki was able to start for the first time When the Project Team Member attempts to go to the Home Page Then the content of the Home Page for the Project Team Membershould be "Welcome to the Wonderful World of FitNesse!"
- 25. Given that the FitNesse wiki was able to start for the first time When the Project Team Member attempts to go to the Home Page Then the content of the Home Pagefor the Project Team Membershould be "Welcome to the Wonderful World of FitNesse!"
- 26. Given that the FitNesse wiki was able to start for the first time When the Project Team Member attempts to go to the Home Page Then the content of the Home Pagefor the Project Team Membershould be "Welcome to the Wonderful World of FitNesse!"
- 27. Edit the Home Page As a Project Team Member I want to edit the Front Page So that it is relevant to my project Let’s leave the slides and do something real…
- 28. Putting it on the table
- 33. A more fluent approach Let’s take a look at JNarrate...
- 34. Other tools and frameworks JBehave Nbehave Cucumber RSpec
- 35. Further reading… Bridging the Communication Gap -Gojko Adzic Agile Testing: A Practical Guide for Testers and Agile Teams -Lisa Crispin & Janet Gregory FIT for Developing Software: Framework for Integrated Tests-Rick Mugridge & Ward Cunningham
- 36. Discussion
- 37. the.guys@pairwith.us http://pairwith.us http://pairwith.us/tv Twitter: @AntonyMarcano @AndyPalmer
Notas do Editor
- Antony Marcano & Andy PalmerExperienced Agile Developers & Coaches for hireCreated http://pairwith.usCreated Narrative Fixture
- Requirements are given to BA as examplesBA infers Abstract RulesDevelopers code Abstract Rules (they test by inferring examples from the rules)Testers use BA rules and the software to infer new examples (edge cases)
- 10-15 Presenters summarise a User Story to the group15-25 Presenters play the role of customer with participants playing the part of the team - guided to ask appropriate questions to capture examples that illustrate the story25-40 Presenters exchange roles with the participants and elaborate the first example for the user story into an acceptance test (captured in plain text)
- It’s technical, aimed at the programmers, not the customerIt doesn’t actually test that you can edit the page (it doesn’t click the save button)