Do we need testers on agile teams?

EuroStar Test Huddle

November 2016

@janetgregoryca With input from Lisa Crispin

• It’s the same argument again and again.

• One side says “team members should all be able to do everything, and the programmers should do their testing and all testers should be writing code”.

• The other side says “No, that can’t possibly work – programmers don’t know how to test, they don’t have the right mindset”. And on and on it goes.

• an activity; not a phase • interactive and starts from the beginning • more than testing code

Potentially shippable product

“Whole Team” responsibility for testing

• Who actually does what?

• Can everyone do everything?

…. and do it well?

Matt Barcomb

Cross-functional knowledge

http://www.slideshare.net/ehendrickson

Analytical Relentlessly Curious Observant Skeptical Empiricist Critical Thinker Investigator

Analytical Detailed

Logical thinker Investigator Collaborator Clean Coder

…. ….

Breadth of Skills

See links for more by Rob Lambert and Adam P. Knight

• Testing provides feedback

• Developers think about testability

• Testers think about the big picture

• Multiple skill sets mean better solutions

The Agile Testing Quadrants (adapted from Brian Marick)

• Are a thinking tool

• Can be used to explain testing in a common language

• Emphasize whole-team responsibility

• Checking: Does the system do what it's supposed to do? - let’s automate this together

• Exploring: Are there any other risks or vulnerabilities that we haven't thought about yet?

• Testing = checking + exploring

**Elisabeth Hendrickson, The Two Sides of Software Testing, Agile Connection

Unit Tests

It’s not just about code !!! ◦ Test assumptions

◦ Explore ideas

The goal:

◦ Shared common understanding of the story

◦ Preventing defects in the code (eliminate waste)

Feature (with

examples) User Story

High-Level

Fix Defects

Code, test & automate story

Accept Story

Explore Examples

Guiding with examples

• Curiosity

• Ability to observe

• Ability to challenge

• To give valuable feedback

• Ability to adapt

• To recognize contexts

• Technical awareness

• Ability to THINK !

Instead of ◦ We’re here to find bugs … or ensure

requirements are met … or break the software …

Think ◦ What can I do to help deliver

the quality solutions?

Instead of We’re here to code and throw it over the wall and then fix bugs.

What can I do to help create testable code and deliver the software successfully?

Instead of We’re here to tell you what we want, and you just do it.

Think How can I work with the development team to deliver the software successfully?