Integrating Testers on to the Agile Team

| by Mark Levison Follow 0 Followers on May 13, 2008. Estimated reading time: 2 minutes |

Integrating Testers into the team is an oft repeated Agile mantra, but we don't spend much time thinking about what it means or how to do it.

What is the role of testers on the team? To:

  • Help define and elicit the acceptance criteria (or requirements)
  • Provide information about quality not to find bugs via automated tests, exploratory tests, ...
  • Work with the customer to identify risks
  • Put more testing effort into the areas where the developers tests (unit and integration) are weakest. For instance if we know that the team has test the Data Layer well, but the GUI layer has been harder to Unit Test then the testers should focus more effort on the GUI layer.

Compiled from (Cem Kaner, Johanna Rothman (pdf), and Jonathan Kohl).

Testing as part of an Agile team is quite different experience than most are used to. As Jonathan Kohl, co-founder of Kohl Concepts, notes: "The difference is that on an agile project, we find the important bugs faster. We are more involved with testing throughout development. Now that the developers are doing rigorous work themselves with solid automated unit tests, the products I test are much more robust."

Antony Marcano, Independent agile testing consultant, talks about the lessons he's learned:

  • Writing acceptance tests requires collaboration: preferably Customer, Tester & Programmer.
  • Testers and Developers should nurture each other's skills.
  • Testing tasks should be part of sprint backlog and not a separate Test Plan
  • Use Exploratory Testing to generate feedback
  • Before fixing bugs write automated tests that reproduce them.

On Simon Baker's team, co-founder of Energized Work, the developers write most of the acceptance tests. This frees the testers to do Exploratory Testing, work with the Product Owner to connect with the customer and help the team understand the users (not just the stories). Developers work on vertical slices (small parts of stories) that satisfy specific acceptance criteria. When the slice is complete the developer works with the tester to explore the slice and understand the acceptance test. The team treats defects as a stop the line event. Either the developer fixes it in the next slice or if its no longer under development a defect task is created. The defect task becomes the highest priority task for the team. Testers find that although they use the same skills, they spend a lot more time collaborating with peers and less time filing bugs.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you