Testable requirements
Download as PPTX, PDF0 likes1,458 views
The document discusses using examples and acceptance criteria to define requirements for software development. It recommends collaborating with business analysts, developers and testers to define examples that specify desired system behaviors in a clear and executable way. Automating acceptance tests based on these examples helps communicate requirements, verify functionality and allow for faster development cycles and deployments. Challenges include maintaining the tests and ensuring they don't become brittle. Strategies like minimizing end-to-end tests and focusing on key user journeys can help address these challenges.
Testable requirements
- 1. Requirements Delivery â Using Examples
- 2. About Us Bharti Rupani @bhartir24 brupani@enterprise-knowledge.com https://www.linkedin.com/in/bhartir Wyn Van Devanter @wynv wyn.vandevanter@excella.com https://www.linkedin.com/in/wyntuition http://www.slideshare.net/wynvandevanter
- 3. Terminology âą Specification by Example âą Executable Specifications âą Automated Acceptance Tests (AAT) âą Behavior Driven Development (BDD) âą Acceptance Test Driven Development (ATDD) âą Testable Requirements
- 4. âSpecifications by examples are acceptance testsâ - Gajko Adzic
- 5. Testable Requirements âą User Journeys âą Deliver business value âą Clear examples âą Executable
- 6. Why should you care? âą Clearly communicate the specifications âą No functional gaps âą Verify business rules âą Build the right thing 6
- 7. Building Quality Plan Collaborate Deliver Build the right thing Build the thing right
- 8. Developing Examples Collaboration Prioritized Backlog Business Goals User Journey User Story 2 Acceptance Criteria 1 Example 1 User Story 1 Acceptance Criteria 1 Example 1 Acceptance Criteria 2 Example 1
- 9. Collaborate How do I code this feature?What are the details of this feature? How do I validate that this work is done?
- 10. Three Amigos âą Business Analyst, Developers and Testers âą Collaborate âą Share knowledge âą Think about the desired outcome âą Shared understanding
- 11. User Journey You are a Business Analyst that is looking for a conference to attend.
- 12. Example of using an Example Attend BA Conference View Results Region Date View DCBADD Details View information about IIBADC View speaker profiles View Cost Select DCBADD Register via Eventbrite Determine Discounts
- 13. User Story As a business analyst, I want to review the various IIBA discounts available so that I can pay a reduced ticket price for DCBADD.
- 14. What is Gherkin? âą Business readable, domain specific language âą Connects human concept of cause and effect to software concept of input/process/output âą Can be interpreted by automation tools to drive acceptance tests
- 15. Gherkin Syntax Source: Jeffrey Davidson
- 16. Scenarios Scenario: Standard Rate Given I am purchasing a ticket to DCBADD And I am not an IIBA member When I view my ticket price Then I see the full rate of $200 Scenario: IIBA Rate Given I am purchasing a ticket to DCBADD And I am an IIBA member When I view my ticket price Then I see the discounted rate of $150
- 17. Example Scenario Outline: Determine DCBADD ticket price Given I am purchasing a ticket to DCBADD And I am a â<membership type>â When I view my ticket price Then I see the discounted â<ticket price>â Examples: membership price nonmember $200 IIBA national $150 IIBA DC $125
- 18. Example Using tables as arguments as input to a Given or as expected output from a Then: Scenario: Validate Order Total Given I am a business analyst And I am purchasing multiple tickets with varying â<membership type>â to DCBADD: When I view my total Then I see my â<total>â ticket number & type price 2 nonmember $400 1 IIBA national $150
- 19. Guidelines âą Be precise âą Make sure itâs testable âą Focus on business functionality âą Avoid specific details âą Use active voice, not passive âą Have a single action trigger the expected behavior (WHEN condition) âą Use parameters for concise expression of examples (i.e. scenario outlines)
- 21. Automated Acceptance Tests (AATs) âą Code automates them âą They run constantly
- 22. Why Have AATs? (Pros)
- 23. Communication âą Helps specify behavior of the system in plain text âą Provides a medium for non-tech and devs to agree on Are we talking about the right system?
- 24. Seams, unit test mistakes
- 25. Automation âThereâs no place for human beings to be doing regression testing manually.â -Jez Humble
- 27. Save resources
- 28. More testing during development
- 29. Why NOT Have AATs? (Cons)
- 30. Why donât more people use them?
- 31. Why NOT have AATs? âą Maintenance âą Speed âą High false negatives, non-determinism
- 32. Impediments âą Poor adoption âą Bandwidth/Velocity âą Learning Curve/Experience âą Business users wonât write specifications âą Developers wonât automate them âą Brittle if recorded
- 33. Solutions
- 34. Acceptance Test Strategy âą Happy paths âą Major unhappy paths âą Legacy âą Regression
- 35. Minimize # of end-to-end tests âą AATs for journeys, not stories âą Is your new story entirely new? âą Balance high # of unit tests + selected end-to-end & acceptance
- 36. Gherkin Specs shouldnât have much setup code Given my friend âBobâ typed âIâm excitedâ into the text box And clicks the Post button on my timeline When I press the Like link on the post Then the screen should say âLikeâ And should include my name as liking it Given my friend âBobâ has posted âIâm excitedâ And I am on my timeline When I like on the post Then the post should be liked by me
- 37. General Tips âą Create different levels of suites depending on depth/level of feedback desired: âą Smoke, Current iteration/sprint, Regression âą Run AATs as close to the real environment as possible
- 38. When Acceptances Tests catches a bug âą See why bug got through unit/integration tests âą Add unit, integration tests âą Prune AATs?
- 39. UI tests âą Sometimes tests will fail if the page doesnât have enough time to load. Use implicit waits, and explicit when really needed âą Capture screen shots when tests fail âą Selenium IDE
- 40. AAT Workflow
- 41. AAT workflow âą Start with a scenario(s) Given my friend âBobâ has posted âIâm excitedâ And I am on my timeline When I like on the post Then the post should be liked by me
- 42. What can you write them in? Vim Sublime Text
- 43. Tracking AATs
- 44. Tracking AATs
- 45. Conclusion âą Worth the investment if done properly âą Very expensive and wasteful if not âą Requires collaboration between analysts, testers, developers âą Developers automate the gherkin âą Focus on journey and scenarios as opposed to stories
- 46. Resources: Books: âą Continuous Delivery, Jez Humble, David Farley âą Growing Object-Oriented Software, Guided By Tests, Steve Freeman, Nat Pryce âą Specification by Example, Gajko Adzic Articles: âą Automated Acceptance Tests, http://www.thoughtworks.com/insights/articles/automated- acceptance-tests âą Using SpecFlow with the Page Object, http://blogs.lessthandot.com/index.php/EnterpriseDev/application- lifecycle-management/using-specflow-to âą Maintaining Automated Acceptance Tests (ThoughtWorks), http://www.youtube.com/watch?v=uf0EVbH5hdA âą Creating Maintainable Automated Acceptance Test Suites, Jez Humble, âą http://www.youtube.com/watch?v=v-L_2y6g5DI
- 47. Thanks! Bharti Rupani @bhartir24 brupani@enterprise-knowledge.com https://www.linkedin.com/in/bhartir Wyn Van Devanter @wynv wyn.vandevanter@excella.com https://www.linkedin.com/in/wyntuition http://www.slideshare.net/wynvandevanter