The Business and Test Analysts Guide to Acceptance Test-Driven Development. Dale Emery

Transcription

1 The Business and Test Analysts Guide to Acceptance Test-Driven Development Dale Emery Web: dhemery.com 1 A Caveat When I talk about Business Analysts and Testers and Developers I do not mean job titles I mean anyone who is using these particular skills at a particular time 2

2 Defining Agile by Results Agile means that the team continuously delivers business value at a sustainable pace while adapting to the changing needs of the business 3 Characteristics of Agile Teams Business-Focused Characteristics Focus on Business Value Done means Done Alignment Frequent Delivery Team-Focused Characteristics Collaboration Coordination Visibility Feedback 4

3 Defining Acceptance Test Driven Development (ATDD) Acceptance Test Driven Development is a practice in which the whole team collaborates to discuss acceptance criteria with examples and then distills them into a concrete set of acceptance tests before development begins 5 The ATDD Cycle As Bart Bookworm I want to be told when new releases are vailable at a discount. Discuss Distill Who What When Why Me Fish 9am Eat Given... When... Then... You Rose noon Grow Us Toys 3pm Play Demonstrate Develop TDD 6

4 Discuss: What Happens story 7 Discuss: Who does What Business Analysts! Describe the feature! Answer questions! Decide acceptance criteria Testers and developers! Ask questions to test understanding, probe ambiguities, and define boundaries " What if...? " Do you mean...? Everybody! Offer and request examples to test and express understanding 8

5 Example: Entaggle 9 Discuss: Entaggle.com Story On a userʼs profile page, show the tags that the user has given to other users Discussion Display the tags in a Has Tagged... tab on the profile Donʼt show tags until they are accepted If the user hasnʼt tagged anyone, say... has not tagged anyone yet 10

6 Distill: What Happens story story with Examples 11 Distill: Who does What Everybody! The same as Discuss, plus! Write acceptance criteria in the form of precise, concise, expressive examples...!... possibly in a format that can be directly automated...!... possibly directly in a test tool 12

7 Distill: Entaggle.com Background: Given users: username first_name last_name arthur Arthur Pendragon black_knight Black Knight And the tag "A Knight of Agile" Scenario: Display tags others have accepted from the user When "black_knight" tags "arthur" as "A Knight of Agile" And "arthur" accepts the tag "A Knight of Agile" Then the "Has Tagged..." tab for "black_knight" displays: recipient tag name Arthur Pendragon A Knight of Agile 13 Distill: Entaggle.com Scenario: Indicate when the user has not yet tagged anyone Given that "black_knight" has not tagged anyone Then the "Has Tagged..." tab for "black_knight" displays: """ Black has not tagged anyone yet. """ Scenario: Display only accepted tags When "black_knight" tags "arthur" as "A Knight of Agile" But "arthur" has not accepted the tag "A Knight of Agile" Then the "Has Tagged..." tab for "black_knight" displays: """ Black has not tagged anyone yet. """ 14

8 Develop: What Happens partially implemented story story story 15 This slide Copyright 2011 Elisabeth Hendrickson, Quality Tree Software, Inc. CC licensed. Develop: What Happens The Test System The System Under Test Driver GUI Tests Fixture code System functionality 16

9 Develop: Who does What Developers! Implement the feature! Work with testers to automate tests! Run acceptance tests Testers! Work with developers to automate tests! Conduct exploratory testing! Run acceptance tests Business Analyst! Answer questions as they arise 17 Demo: Who Does What Developers! Help prepare the demo! Answer questions Testers! Help prepare the demo! Perhaps arrange to execute the acceptance tests! Answer questions about test activities and results Business Analyst / Product Owner! Decide whether to accept the feature 18

10 Demo: Entaggle.com 19 Testers: Same and Different Same Still use all of your testing skill and expertise Different Apply testing skills early and throughout the project Define tests at the start, not at the end Your value is not only in finding problems, but also in helping to prevent them Test each feature as soon as it is available Much more emphasis on automation You (might) help automate tests All one team 20

11 Business Analysts: Same and Different Same Still use all of your analysis skill and expertise Different Deliver features to the team in smaller batches, perhaps one at a time Collaborate with other team members to create shared understanding Express acceptance criteria as potentially automatable tests Remain available to the team to provide guidance throughout development Review progress and done more frequently 21 Resources Agile Testing. Lisa Crispin and Janet Gregory. Agile Product Management with Scrum. Roman Pichler. Bridging the Communcation Gap. Gojko Adzik. Specification by Example. Gojko Adzik. User Stories Applied. Mike Cohn. Driving Development with Tests: ATDD and TDD. Elisabeth Hendrickson. wp-content/uploads/2011/04/atddexample.pdf 22

12 For Further Information Dale Emery Web: dhemery.com 23