Trusted answers to developer questions
Trusted Answers to Developer Questions

Related Tags


What are the types of non-functional testing?

Theodore Kelechukwu Onyejiaku

What is non-functional testing?

Non-functional testing is the type of testing done to verify the non-functional aspects of a product such as performance, security, compatibility, etc.

Types of non-functional testing

The several types of non-functional testing are described below.

1. Performance testing

Performance testing verifies whether the system meets the non-functional requirements identified in the SRSSystem Requirements Specification document or not.

It verifies how the system behaves and how well the system works based on response time, throughput, etc.

2. Load testing

Load testing checks how the system responds when the load is increased. When the load is at its peak, it verifies if the application works as expected.

One way to constantly perform this testing is to increase the number of users using the same application until the time load reaches its maximum.

3. Stress testing

Stress testing requires increasing the system’s capacity to check the point at which it fails. An example is by feeding a system with illegal or invalid inputs to stress the capabilities of a product.

4. Volume testing

In volume testing, the amount of data is increased and fed to the software. With this, the efficiency and response time of the software is checked for any data loss.

5. Security testing

This type of testing is known as one of the most important types. Security testing ensures that an application is secured. Security deals with authentication, authorization, sessions, etc.

6. Usability testing

Usability testing is focused on how usable a system is. The main focus is the experience of using the application. The application should be user-friendly.

7. Compatibility testing

Compatibility testing tests if the application or software is compatible with other hardware or software platforms where it will be used.

8. Installation testing

Installation testing is carried out to ensure that the user doesn’t face difficulty when installing the software. This is because installation is the first interaction a user has with the application.

9. Uninstallation testing

In uninstallation testing, the software is tested to verify that errors are not caused after uninstalling it and that all the components of this application are cleared.

10. Recovery testing

Recovery testing is the test carried out to confirm that data is recovered when there is any failure such as power failure, crashing of the application, etc.

11. Documentation testing

Documentation testing is carried out to confirm that all documents related to the technical use and maintenance of the application exists and are consistent.

12. User Interface testing

User Interface testing is done regarding the application designs. It helps ascertain that all the elements that make up the interface work as they should.




Theodore Kelechukwu Onyejiaku

View all Courses

Keep Exploring