|
The testing plan will be done at the following different levels:
1. Unit test, which is under the development team’s responsibility, aims to assure that all functions and features of a single unit transaction are performed as specified in the design document. It could cover a group of closely related unit transactions as a single object. Unit testing is performed in isolation by the team member responsible for programming.
2. Integration test, which is under the technical team’s responsibility, aims to ensure that all interacting subsystems in a system interface correctly with one another to produce the desired results. Furthermore, in trying to reach this goal, integration tests will ensure that the introduction of one or more subsystems into the system does not have an adverse effect on existing functionalities.
3. Performance test, which is under the technical team’s responsibility, is planned and executed on all components for which performance requirements and targets have been agreed with the client.
4. Capacity test, which is under the technical team’s responsibility, assesses the application behaviour running with the conditions of a deployed solution (notably the volume of data and the simultaneous connexions of users). The capacity test may reveal insufficient material resources for instance or network bottlenecks.
5. Solution test, which is under the functional team’s responsibility, aims to ensure that the application performs as per the functional specifications, approved by the client. Solution Testing is performed, once the Integration testing has been completed. Depending on the project, any regression tests deemed necessary. This phase is necessary to ensure the coherence of figures, business rules and calculations. It consists of sanity checks.
6. User acceptance tests (UAT) are under key users’ responsibility. Test cases will be provided as support of the application testing and user validation.  |
