🕳️Non Functional Testing

Non-Functional Testing is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. It is designed to test the readiness of a system as per nonfunctional parameters which are never addressed by functional testing.

Type of Software Testing

In general, there are three testing types

• Functional

• Non – Functional

• Maintenance

Non-functional Testing

Examples

🧪 Non-Functional Testing

Non-functional testing is a type of testing that focuses on verifying the performance, reliability, usability, security, and other non-functional aspects of a software system.

Sample Test Cases of Non-Functional Testing

Test Case #	Test Case	Domain
1	Application load time should not be more than 5 secs up to 1000 users accessing it simultaneously	Performance Testing
2	Software should be installable on all versions of Windows and Mac	Compatibility Testing
3	All web images should have alt tags	Accessibility Testing
4	The system should be able to handle a large number of concurrent users without slowing down or crashing	Load Testing
5	The system should be able to handle a large amount of data without slowing down or crashing	Stress Testing
6	The system should be able to handle peak loads without slowing down or crashing	Peak Load Testing
7	The system should be able to recover from failures and errors quickly and gracefully	Recovery Testing
8	The system should be able to handle different types of network conditions, such as slow or unstable connections	Network Testing
9	The system should be able to handle different types of input, such as invalid or unexpected data	Input Validation Testing
10	The system should be able to handle different types of output, such as large or complex reports	Output Validation Testing
11	The system should be able to handle different types of security threats, such as hacking or malware attacks	Security Testing
12	The system should be able to handle different types of authentication and authorization scenarios, such as single sign-on or multi-factor authentication	Authentication and Authorization Testing
13	The system should be able to handle different types of user interfaces, such as desktop or mobile devices	User Interface Testing
14	The system should be able to handle different types of languages and locales, such as English or Spanish	Internationalization and Localization Testing
15	The system should be able to handle different types of environments, such as production or development	Environment Testing
16	The system should be able to handle different types of hardware, such as servers or mobile devices	Hardware Compatibility Testing
17	The system should be able to handle different types of software, such as operating systems or databases	Software Compatibility Testing
18	The system should be able to handle different types of performance metrics, such as response time or throughput	Performance Metrics Testing
19	The system should be able to handle different types of data formats, such as CSV or XML	Data Format Testing
20	The system should be able to handle different types of integrations, such as APIs or third-party systems	Integration Testing