When it comes to the complex validation of the implemented system functionality, it’s necessary to release testing cycles that consist of the stages described below.
The performance of functional testing as a service is conducted exactly after the configuration of the appropriate functionality and ends when each part of the configuration operates in accordance with documented requirements.
First Integration Testing
On the given testing stage, designed prototype of the system is firstly validated in its fullness. The highest priority has those works where all defects and bugs are fixed: one defects can block passing script and identify other errors. At the end of the first integration testing, testers evaluate the feasibility of the transition into the productive exploitation of project results.
Second Integration Testing
Second integration testing is performed after elimination of all previously identified problems and errors. At the end of the given phase, it’s necessary to check if acceptance testing was run by the end-users. At the same time, it makes sense to delay the acceptance testing, if there is a reason to believe that the quality of the system is not initially established with requirements.
In practice: the discovery of a larger number of errors during testing cycles significantly reduces the likelihood of the adoption of the system by the customer.
First User Acceptance Testing
This stage of the testing cycle is preceded by the removal of previously detected errors, providing user access to a test environment, explanation to the testers all procedures. To ensure a rapid problem solving and continuous monitoring of the testing process is better to organize testing in one place. Depending on the testing cycle results, it’s necessary:
Final System Configuration
Based on the information obtained from the first acceptance testing, as well as the registered requests for change, and the final system configuration and approved changes. Correct processing of this stage greatly simplifies the process of acceptance, because changes that were made to the system ensure greater compliance and existing practice.
Second User Acceptance Testing
This stage is a final one because all test scenarios should be completed and approved. On successful completion of this cycle, the transition to a productive operation must be approved.