Testing in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time!

Transcription

1 Testing in an Agile Environment Understanding Testing role and techniques in an Agile development environment. Just enough, just in time!

2 Today s Topics How the Tester s Role Changes in Agile Testing in an Agile Framework Strategies to Apply to Testing

3 Origins of Agile Testing The Agile methods: Use most Testing Best practices Perform them differently Use different timing Add good practices to list

4 Scrum Overview Retrospective Pre-Sprint Prep Daily Stand-up Vision Roadmap Product Backlog Backlog Grooming Sprint Review Run Sprint Sprint Planning Sprint Demo 4

5 Progressive Test Planning Different levels of precision: Initiate Project Quality Objectives General Testing Strategies for Iterations & Releases Testing Roles/Responsibilities Plan Iteration Understand Acceptance Criteria for each User Story Iteration Testing Strategy Specific Activity Plan for Test Preparation & Testing Develop Product Increment Prepare Test Cases Ensure Product Quality

6 Iteration Test Planning Retrospective Acceptance Criteria Discuss Stories ATDD Criteria Pre-Sprint Prep Vision Roadmap Product Backlog Backlog Grooming Daily Stand-up Sprint Review BDD Scenarios Run Sprint Testing Strategy Adapt from the Team s General Testing Strategy Specific Activity Plans: Test Preparation, Testing, etc. Sprint Planning Sprint Demo

7 Agile Team Members The Agile Team Customer & End Users Product Owner Management The rest of the team Scrum Master Other Teams

8 Who is Responsible for Quality? Product Owner? Scrum Master? The rest of the team Developers? Testers? Others? The Agile Team The rest of the team Product Owner Scrum Master

9 Team-Based Testing Approach Story Story Testing Testing Feature Testing Non- Non- Functional Functional Testing Testing The Agile Team The rest of the team Product Owner Scrum Master Usability Testing End-to-End Testing Acceptance Testing Are we doing all of the Testing we should?

10 Product Owner Role in Testing The Agile Team Product Owner Scrum Master What is acceptable For each User Story? For each Feature? For the system? Who are the users? Their backgrounds? Their needs? Who should do the Acceptance Test? The rest of the team

11 Developers Role in Testing Understand requirements Discuss w/product Owner Ask questions Design, Automate and Perform tests Unit Tests TDD, ATDD Feature Tests Non-Functional tests Demonstrate product for Product Owner evaluation The Agile Team The rest of the team Product Owner Scrum Master

12 Agile Tester

13 Typical Agile Tester Role Support Product Owner and Developers Testing Clarify User Stories and Acceptance Criteria Assist with testing and interpreting test results Perform Additional Testing e.g. Exploratory Testing Negative Testing Special Scenarios The Agile Team Product Owner Scrum Master The rest of the team

14 Supporting the Team Agile Testing Quadrants Agile Testing Quadrants Business Facing Functional Tests Examples Story Tests Prototypes Simulations Unit Tests Component Tests Q2 Q3 Q1 Q4 Exploratory Testing Scenarios Usability Testing User Acceptance Testing Alpha/Beta Testing Performance & Load Test Security Testing ility Testing Critique the Product From More Agile Testing, Addison-Wesley, 2014 Technology Facing 1 Copyright 2015, Janet Gregory and Lisa Crispin

15 Just Enough Just in Time Low-Fidelity Models

16 Collaborative Test Design Use collaboration techniques e.g. Context Diagrams Mind Maps Brainstorming Others

17 Example: Context Diagram 17

18 Example: Testing Mind Map

19 Pairing with Developers Pair Programming is an Agile technique Pairing of Testers with Developers: The ultimate in collaboration Facilitates mutual learning Improves team efficiency Results in a higher-quality product

20 Test-Driven Development (TDD) AKA Test-First Development Focused on coding and unit testing Inspiration for other techniques: Acceptance Test-Driven Development (ATDD) Specification by Example Behavior-Driven Development (BDD)

21 Acceptance Test-Driven Dev (ATDD) Product Owner defines (prior to coding): Acceptance Criteria for each User Story Acceptance Tests (User Story, Feature, Product) Developers use Acceptance Tests: Ensure they develop what is needed Test for Doneness Testers collaborate with Product Owner and Developers

22 User Stories after User Story Estimation Winston Consulting, 2015

23 Behavior-Driven Development (BDD) Like ATDD, but focused on System Behavior in response to User Behavior User Story Acceptance Criteria: 1 or more Given/When/Then Given (a particular scenario) When (the user does something) Then (this should be the result)

24 BDD Example Banking Application User Story: Transfer Money Between Accounts As a Bank Customer I need to transfer money between my accounts So that I have money where I need it to be Scenario1 (Insufficient funds): Given Account A has $125 available And Account B has $375 available When I transfer $200 from A to B Then I should see an error message And A should have $125 available And B should have $375 available Scenario2 (Sufficient funds): Given Account A has $125 available And Account B has $375 available When I transfer $200 from B to A Then I should see confirmation message And A should have $325 available And B should have $175 available

25 Exploratory Testing "a style of software testing treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. Cem Kaner Use Exploratory Testing when: Requirements are incomplete Time is lacking Each Testing Session: Charter & Plan Test & Explore Analyze & Learn

26 Example

27 Lightweight Documentation Apply the Agile Values and Principles Remember: Plan is a verb! Plan just-in-time Talk about everything that is important Document to remember what was said Write only what will be needed later Lightweight: Scenarios, Lists, Diagrams

28 Storyboarding

29 Traveler confirms with no options Example: Check In Airline kiosk welcome screen with instructions to begin Traveler swipes an ID card Display of flight information for that traveler Traveler verifies flight Display of flight information for that traveler with options Display security messages while printing boarding pass System prints boarding pass Display Airline kiosk welcome screen with instructions to begin

30 Defect Tracking & Management Purposes: Ensure every defect is fixed or accepted Provide data for Metrics and analysis Options: Handle defects face-toface Write & manage Defect Stories Use a Defect or Issue Tracking System

31 Metrics Examples

32 Regression Tests Agile Values and Principles: We value responding to Change Welcome Change Every Agile Iteration = Change requires Regression Testing necessitates Test Automation

33 Time-Boxed Delivery Every Iteration results in a slice of product that is Production-Quality Done = Designed, Developed, Complete Fully Tested, Verified & Validated, Regression Tested Ready to ship, put in production & use

34 Release/End Game Decision to Release Functionality OK Quality Good Release Preparation Production Readiness Release Package Test Release Back-Out Test Release Release Activity Verification In-Production Final Check Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Release

35 User Acceptance Test (UAT) In addition to approval by the Product Owner End Users: Prior to Release User Acceptance Test the product-to-date Provide feedback to the Agile team

36 Cross-Team Testing When whole product involves more than the Agile Team s work, e.g. Multiple Agile Development Teams Non-Agile Software Teams Other Development Besides Software Agile Tester must: Coordinate & Collaborate Ensure whole product/solution testing

37 Review Retrospective Pre-Sprint Prep Daily Stand-up Vision Roadmap Product Backlog Backlog Grooming Sprint Review Run Sprint Sprint Planning Sprint Demo 37

38 38