| |
Testing functionality as defined by the Software Requirements Specification (SRS), or similar document |
| Testing related functions and interfaces as bugs are closed |
|
| |
Testing of distribution, setup, migration, un-install, update, and ongoing state/configuration management of the software |
|
| |
Ensuring that the software provides fault-free service under specific hardware and software environments over long durations |
Test the behavior of the software under stress, e.g. failure modes, resource constraints, and peak load conditions |
Test to ensure that software deals with such threats as identity spoofing, data tampering, illegal access, and denial of service attacks |
Spot typical security holes such as buffer overruns, and ensures that mitigation techniques work as expected |
|
| |
Testing applications and hardware for logo compliance and platform certification |
|
| |
Application and hardware compatibility testing for new versions of platform and system software |
Platform and hardware compatibility testing for new versions of client-server, web-based, and desktop applications |
Application and platform compatibility testing for new versions of devices and peripherals |
|
| |
Ensuring that various components of the system work well together in selected scenarios |
| Testing software interoperability with other standards-based solutions |
Testing cross-server scenarios in client-server and web service applications |
| Testing end-to-end scenarios with multiple applications and solutions |
|
| |
Testing to ensure that the software is developed as a world-ready product, enabling efficient and cost-effective localization efforts |
Testing to ensure that localized versions of the software work as per the requirements |
Testing to ensure that the software meets accessibility and usability requirements |
|
