_edited.png)
Test phases are the different stages involved in the software testing process, which are typically organized according to the software development lifecycle. Each test phase has a specific goal and set of activities, and the results of each phase are used to guide the subsequent phases.
​
There are six different phases used during a full software quality assurance test cycle. The first is the Static Testing Phase which verifies that the requirements and specifications are thorough, complete, and make sense for the goal of the product. This is done before any coding starts and seeks to eliminate defects before they’re even in the system.
The module/Unit Testing Phase begins once developers have completed individual modules. Each module or unit is tested independently of the other to help find potential defects and speed up development. By testing the units in isolation, finding the cause of an issue is expedited, saving both time and energy.
​
After each unit has been tested, the third phase begins Integration Testing. This phase ensures that the individually tested units work well together in assemblies. Generally, units are added together one by one and fully tested after each unit is added. This manner of testing validates that the modules play well together and by adding units sequentially, determining the cause of a possible defect between the units is much easier.
Static Testing Phase
Module & Unit Testing Phase
Module & Components Integration Testing Phase
System & System Integration Testing Phase
User Acceptance Testing Phase
Production Verification & Acceptance Testing Phase