Using feedback
Test plans are not static documents carved in stone to stand for all time. They should be dynamic, living texts that evolve as you learn more about your features and products. Recall the testing spiral from Chapter 1, Making the Most of Exploratory Testing. Even after the detailed test plan is complete, you need further testing, specification, and discussion cycles to refine and improve your checks.
Those refinements can take several forms. Most benignly, you may need to add details you are happy with to the specification. Perhaps a particular input case or UI element had been missed from the document. If you find it during testing and it works as intended, all you need to do is write it up.
In my experience, such lucky coincidences are rare. If an element was missed from the specification, it’s unlikely a developer will implement it exactly as the product owner intended. Most feedback is, unfortunately, negative—either bugs where the feature doesn...
