There is no one universal software test process, but there are common sets of test activities without which testing will be less likely to achieve its established objectives. These sets of test activities are a test process. The proper, specific software test process in any given situation depends on many factors. Which test activities are involved in this test process, how these activities are implemented, and when these activities occur may be discussed in an organization’s test strategy
Contextual factors that influence the test process for an organization, include, but are not limited to:
- Software development lifecycle model and project methodologies being used
- Test levels and test types being considered
- Product and project risks
- Business domainOperational constraints, including but not limited to:
- Budgets and resources
- Timescales
- Complexity
- Contractual and regulatory requirements
- Organizational policies and practices
- Required internal and external standards
The following sections describe general aspects of organizational test processes in terms of the following: Test activities and tasks Test work products Traceability between the test basis and test work products It is very useful if the test basis (for any level or type of testing that is being considered) has measurable coverage criteria defined. The coverage criteria can act effectively as key performance indicators (KPIs) to drive the activities that demonstrate achievement of software test objectives