Testing

Agile Testing is “collaborative testing practices that occur continuously, from inception to delivery and beyond, supporting frequent delivery of value for our customers. Testing activities focus on building quality into the product, using fast feedback loops to validate our understanding. The practices strengthen and support the idea of whole-team responsibility for quality.” - Lisa Crispin and Janet Gregory in Agile Testing Condensed.

Role

No separate role - rather a need that a self organizing team needs to fulfill. Requires true collaboration.

• Participate in backlog refinement and sprint planning to understand user stories, acceptance criteria.
• Collaborate on creating acceptance criteria with other team members.
• Continuous Testing - start testing before development starts on PBI/User Stories.
• Help automate tests of Acceptance Criteria (i.e. Example Mapping).
• Provide Product Owner feedback during Sprint itself and also in Sprint Review.
• Help the Product Owner and whole Scrum Team understand where the product quality is, especially with respect to the Definition of Done.
• Mentor and coach other team members to raise quality, especially through cross-skilling.
• Ask questions about usability, accessibility and security. Highlight risks found in these areas.
• Ask questions about the business domain.
• Exploratory testing - in addition to automating acceptance tests, exploratory work takes perspectives that haven’t already considered.
• Testing isn’t checking to see if the product works.
• Work in the language of the customer.

Key Ingredients for Success

• Whole Team Approach
• Agile Testing Mindset
• Automate Regression Tests
• Automated Acceptance Tests as Living Documentation
• Continuous Feedback
• Collaborate with Customers
• See the Big Picture