The system test cycle includes the following procedures:
Because you can select which tasks to add to the system testing project, they are insulated from ongoing changes. Selecting tasks gives you the ability to build, fix, and test the software apart from ongoing changes until it meets an agreed-upon quality standard.
The system test area is more stable and easier to build because most of the integration problems were resolved before the software moved to the system test level.
The system test cycle usually is used in preparation for a milestone, such as a release. The frequency of the system test cycle and the level of testing depend on several situations, such as:
Also, because software development is still underway, the goal is to find defects and develop new tests, not to create a stable installation or release.
The following overview gives you an idea of what the system test build cycle includes: