Claire Lohr has been an active professional in the computer field for thirty years, with the past twenty years emphasizing software process improvement and testing. She currently provides training (design, authoring, and instruction) and consulting services for a wide variety of both government and commercial clients. Claire was the chair of the Working Group for the revision of the IEEE Std 829-2008 Software and System Test Documentation.
Quality assurance testers may feel overwhelmed by all they have to do and the short time they have to do it. Implementing proven process improvement techniques can help streamline or replace existing models, making testers’ workloads manageable and letting them accomplish more—without sacrificing quality.
Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements.
Testable requirements, or acceptance criteria, are the communication of an expectation between its originator and potential stakeholders. Many testers struggle with this starting point. But once you succeed, you know the processes that can build and test a system implementing “good” requirements.