System Testing: Objectives, Defects & Examples
- Objectives – here the system as a whole is tested, from end to end. This will include testing the functional and non-functional behaviours of the system.
- Typical defects and failures – a defect found at system testing level would usually not be in the source code since testers here would typically not have access to it. It would usually be found in a requirement or user story document. These would then be observed as failures in the system, found when testing a scenario.
- Continuing our example, the drop-down box may not be displayed, and is now observed in normal operations, such as when trying to add more than 1 item to a shopping cart.
- Specific approaches and responsibilities - this is often the start point for testing carried out by dedicated test professionals. When conducting non-functional testing, such as usability testing, the test environment should attempt to mirror the live environment as much as possible. In addition, it may be necessary to use simulations or models of parts of the system, such as simulating poor network connectivity when testing online systems.