Test multiple stories together to uncover different perspectives
Posted by Matt Archer on April 12, 2013
|This post is part of the tips for manual testers working in an agile environment series. A series of posts inspired by the topics covered in the Techniques for Agile Manual Testers course that is currently available to take in London (via the Ministry of Testing) and in Copenhagen (via PrettyGoodTesting).
Efficient agile teams are often compared to a well-managed production line, with new stories flowing quickly from a concept, through development and testing, before being rapidly released so that users can immediately benefit from their introduction.
This type of efficiency gives the team and their clients a competitive advantage over slower agile teams and teams following traditional process models, but it also introduces some potential testing pitfalls.
When we test in a fast paced team, it is easy to become too focused on the individual units of work that progress through our production line (the features / stories), without considering the bigger picture.
To help mitigate this risk, I recommend thinking about each new story from a variety of different perspectives, including how it relates to stories already released. By combining multiple stories together you will typically unearth a more complicated assortment of inputs and interactions that can be the basis for wider-ranging tests.
That said, be careful not to lose focus entirely. It is important to supplement (not replace) our focused tests with tests that are based on a broader viewpoint. I say this because it is typically a variety of tests from many different perspectives that help us minimise effects like inattentional blindness and find the greatest number of bugs.
If you have a comment or question about this particular tip, please do not hesitate to Leave a Reply. A complete list of tips is listed below.