Stages of testing

Stages of testing

1. 1. Module testing

   • Module testing involves testing the individual sections ofthe software to make sure each section works as intended. They tend to be written from a programmers perspective and is an example of white box testing where the tester has access to the internal data structures and algorithms that form the basis of the system.

2. 2. Integration testing

   • When module testing is completed the modules are combined one at a time at each integration stage and debugged.

3. 3. Functional testing

   • This is intended to test the operation of the system and may pick up errors that were missed at the module stage. Developers write functional tests with users and then test the system with variations on those tests. This is an example of black box testing where the system is judged on whether a given input produces the correct output.

4. 4. Systems testing

   • Sytems testing tests the complete integrated solution in preparation for user testing. It checks that all the modules operate together properly and that a transaction is processed correctly throughout the system from beginning to end.

5. 5. User testing

   • User testing is where the users of the system put it through its paces and offers their comments. This is the final stage before the system goes into operation and should result in acceptance by the client before the system can be installed. Users may do things that the developer hasn't counted on meaning they can fix it before it gets installed.

6. 6. Operational testing

   • Operational testing is conducted in the actual environment in which the solution will be working or perhaps a simulated version of that environment. A simulated version will give the testers more control over conditions and solution experiences, the tests can also be repeated. However its only a partial substitute for seeing the system under real operational loads.