The test process typically contains the following phases:

- Test planning
- Designing test cases
- Test execution
- Recording test output
- Check whether IUT passes the tests

For large, complex systems a systematic testing process is essential. Companies may have a test policy which can help throughout the test process. The test policy is a statement that describes the philosophy / motivation behind the testing being done. Test strategies state how systems are tested and how the risks are mapped to test techniques.

Test planning should start early in the development process. This ensures that the overall requirements of the system are considered in testing. Early test planning can also identify problems with requirements. If requirements are too vague they will not be easily tested for. This means that they can be refined and updated early on in the development process.

Black-box and White-box Testing

Black-box testing techniques involve developing the tests based on the specification of the program / system only i.e. what it should do. White-box testing involves tests being developed on the basis of the code.

Black-box test techniques are normally applied in testing of the overall system. Black-box testing techniques are not very good at finding some faults. They can miss special cases which are more likely to result in test failures. White-box test techniques are typically used in unit testing.

Black-box and white-box techniques both have advantages and disadvantages so it is beneficial to employ both. "Grey-box" techniques are a combination of white-box and black-box testing and use information about the system specification as well as the implemented code.

See Alpha, Beta, Regression and Stress Testing for more examples of testing techniques.

Search for "Testing Process and Techniques" on: Google | Kelkoo | Amazon | eBay (UK) | eBay (US)

Search for "Testing Process and Techniques" on the rest of Computing Students: Testing Process and Techniques