While functional tests determine if the system does what it’s supposed to, non-functional tests determine how well the system performs the tasks it was designed to do. These tests validate the readiness of a system, or subsystems based on predefined criteria that are not generally covered in functional tests. Non-functional tests look deeper into the system to make sure both the hardware and software can handle heavy loads, can withstand hacking attempts, or even make sure all of the user documentation is thorough and useful to the end user. It helps to answer questions such as:
- How fast does it respond?
- How many people can login at once?
- How quickly can a new user learn the application?
- Is it suitable from the perspective of the typical end user?
Comparison testing can include many areas of evaluation including: functionality, quality, performance, features, usability, help manuals, and security.
This type of testing determines the immediate or long term effects of configuration changes on the system’s behavior and performance.
This kind of testing makes sure that your global product can be translated effectively into any language you want, thereby cementing your standing in the global market.
Regardless of the focus, compatibility testing ensures that all of your end users will have the same positive experience.
Also known as soak testing, endurance testing helps to determine if a system can sustain a continuous high load.
The goal of installation testing is to make sure the software is installed and working as expected after installation. Sometimes called implementation testing.
Ensure that services are performant and understand the behaviour of how scalable the system is.
Identifying bottlenecks in infrastructure.
Allows understanding of compatible integrations.
Find gaps in security.