The system test cycle includes the following:
The system test cycle enables you to do more in-depth testing on a specific set of tasks, insulated from ongoing changes by developers. The goal is to produce an installation area or to produce release media that meets a quality standard.
Because you can select which tasks to add to the system testing project, they are insulated from ongoing changes. This 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 will be resolved before the software is at 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 will depend on several situations, such as:
Also, since 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 should give you an idea of what the system test build cycle includes: