In the field of software testing, the term test control may be seen as an open-ended exercise performed throughout the testing phase to compare the actual progress of the phase with the pre-specified & developed plans and accordingly directing the testing process.
Thus, the main intent, behind the test control activity is to meet the specified objectives, and implementing the corrective actions, to control and mentor the testing phase in order to achieve the goals, in accordance with pre-decided strategy and time duration.
The probability of, what a human being thinks of, and what actually happens, is close to "zero", unless and until, all goes well, from beginning to end.
Similarly, in the field of software engineering, a project is planned, to be completed within the stipulated time period, but most of the time, the progress of the project lacks behind its specified deadline. This situation, has become the common scenario in most of the projects and may arise due to various factors such as
Basically, the activities of test control are based on the results of the test monitoring. So first, let's have a small overview of "Test Monitoring".
The terminology "Test monitoring", itself describes its job. Test monitoring is a time management activity, used to evaluate and observe the status of the current process. What is observed in the test monitoring, is being used in the test control process to implement the corrective actions.
Now coming back to the test control. For test control, a tester may opt for the negative approach. Its basic working consists of following steps in a sequential manner:
Based on the status report of the test monitoring process, following activities may be implemented as the corrective measures:
Thus, it may be concluded that test control is a management activity, which constantly execute throughout the testing phase to bring the derailed ongoing process back on the track in order to achieve the set-up goals.