Test control comprises all leadership, initiatory, and corrective measures that are performed in order to put into practice all test activities defined in the test plan and the test execution schedule. Controlling measures can directly affect testing activity or any other type of development activity. We differentiate between the following types of situations:
- The initiation of planned measures—for example, assigning planned test activities to a certain team member, and ensuring that the activity begins and delivers results.
- Short-term reaction to changes or difficulties that arise—for example, you may have to apply for and assign additional test resources (staff, workstations, tools) to rein in an obvious backlog.
- Check whether corrective measures you have initiated are having the desired effect (for example, whether a previously unfulfilled exit criterion is now fulfilled).
React to deviations from plan
Short-term reactions to unexpected issues or changes can mean you may have to improvise rather than wait until the next test cycle.
If critical issues arise, you may have to plan additional test cycles, which in turn may delay the product release and extend the planned time to market.
Clear communication of issues and changes
If issues occur that affect project activities external to the testing environment, or that cannot be solved within the team, the test manager must communicate the situation to the appropriate stakeholders. If following up on the test execution schedule leads to test cases being discarded, this usually implies increased risk. In turn, this means the situation must be documented and included in the next test summary report. The test manager is responsible for the clear communication to the project leader(s) of issues that increase risk.
Leave a Reply