Module - 3 - Testing Process
Module - 3 - Testing Process
Module - 3 - Testing Process
Testing process
Pre-requisites:
Logistics requirements:
Information sources:
Training time:
Working time:
page 2 of 3
Testing process
Testing is a process rather than a single activity. Testing must be planned and it requires discipline to act upon it. The
quality and effectiveness of software testing are primarily determined by the quality of the test processes used.
The activities of testing can be divided into the following basic steps:
1. planning and control
2. analysis and design
3. implementation and execution
4. evaluating exit criteria and reporting
5. test closure activities
Purpose:
- to determine the scope, the risks and to identify testing objectives
- to determine the required number of QA engineers or needed resources like test environments etc
- to schedule test analysis and design tasks, test implementation, execution and evaluation
Control, is the activity of comparing the actual progress against the plan, and reporting the status, including deviations
from the plan. It involves taking actions necessary to meet the mission and objectives of the project.
Test execution involves actually running the specified test on a computer system either manually or by using an automated
test tool. It is a fundamental test process in which actual work is done.
- to assess if more test are needed or if the exit criteria specified should be changed
- to write a test summary report for the stakeholders
In the same time, testing can be closed for other reasons like:
- when the project is cancelled
- when some target is achieved
- when a maintenance release or update is done