Examples of Test Cases for following Non-functional requirements are mentioned below;
- Efficiency
- Capacity
- Availability
- Scalability
- Maintainability
- Compatibility
- Robustness
- Response Time
- Portability
- Interoperability
- Usability
- Security
- Throughput
- Logging
- Performance
- Reliability
Efficiency:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Evaluate response time of search feature |
checking results on University Website by entering rollno |
1. Perform a search operation |
System must responds within 2 seconds |
System respond after 5 seconds rather than 2 seconds |
System is not efficient as desired |
Capacity:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Assess maximum user capacity |
Maximum user data |
Simulate concurrent logins with the maximum allowed users |
The system should allow the specified number of concurrent users |
Our requirement was to handle at least 500 users at the same time and system can handle more than 500 users |
Pass |
| TC#02 |
Evaluate database capacity of 1 GB |
Images, videos, text etc |
Input data until the database reaches its size limit |
The system should handle the maximum database size without performance issues or data corruption |
Database can store data of 1 GB |
Pass |
| TC#03 |
Test concurrent transactions |
Withdraw money,
Check balance, Transfer money |
Simulate simultaneous transactions from multiple users |
The system should handle the specified number of concurrent transactions without data inconsistencies |
There is no issue observed when multiple account holders try to Withdraw money,
Check balance or Transfer money. |
Pass |
Availability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Check system accessibility during regular hours |
Multiple users |
Access the system during peak usage hours |
The system should be accessible without downtime during regular hours |
system was not accessible and system is hanged during regular hours |
Fail |
| TC#02 |
Test system availability during scheduled maintenance |
Updating system, updating plugins |
Schedule system maintenance |
Users should be notified, and the system should display a maintenance message during the scheduled maintenance window |
User is properly notified about maintenance |
Pass |
Scalability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test scalability by increasing user load incrementally |
Multiple users |
Gradually increase the number of concurrent users |
System must handles increased load without significant performance impact |
System was unable to handles increased load without significant performance impact |
Fail |
Maintainability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Check ease of software updates |
N/A |
Install the latest software update |
System must updates without causing issues |
System is updated without causing issues |
Pass |
| TC#02 |
Assess code maintainability |
N/A |
Review code structure and documentation |
Code must be well-documented and easily understandable |
Code is not well-documented and lack of comments to understand the structure of code |
Fail |
Compatibility:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test Website compatibility with trending browsers like Google chrome and Firefox |
Website surfing on Google chrome and Firefox |
Access the Website using different browsers |
Website must displays and functions correctly on each browser |
Website images are not loading correctly on web browser XYZ |
Fail |
| TC#02 |
Evaluate compatibility of Software with different operating systems like win 10, win7, win 11 |
Software execution on win 7, win 10, and win 11 |
Access the Software on various operating systems like win 10, win7, win 11. |
Software should works well on win 7, win 10, and win 11 |
Software is working well on win 7, win 10, and win 11 |
Pass |
Robustness:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test the website login module with invalid input of email address |
Email address |
Enter invalid data in email fields |
System must handles invalid input and provides appropriate feedback |
System successively handles invalid input and provides appropriate feedback |
Pass |
Response Time:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Evaluate response time for checking the account balance on ATM machine |
Account Balance |
Insert the card and after login try to check account balance |
System must responds within the specified time frame |
System is not responding within the specified time frame and user need to wait for more than 1 minute for checking balance. |
Fail |
Portability:
| Test Case ID |
Test Case Description |
Test Data |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test system portability across different devices |
N/A |
Access the system on various devices (e.g., desktop, tablet, mobile) |
System must adapts to different devices without loss of functionality |
System is able to adapts to different devices without loss of functionality |
Pass |
| TC#02 |
Assess database portability |
Database |
Migrate the database to a different platform |
Database operations must remain consistent after migration |
Database operations are consistent after migration |
Pass |
Interoperability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Verify interoperability with third-party API |
API credentials |
Integrate the system with a third-party API |
Data exchange between the system and API must be successful |
Data exchange between the system and API is successful |
Pass |
| TC#02 |
Test data interchangeability with another system |
External system data |
Import data from a different system |
The system must processes and utilizes the imported data correctly |
The system is not processing and utilizing the imported data correctly |
Fail |
Usability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Assess interface component (make purchase) of a shopping mall |
User data and Cart data |
Complete a common user task (e.g., make a purchase) |
Users can successfully complete tasks with minimal steps and effort |
Users is unable to complete tasks with minimal steps and effort |
Fail |
Security:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test user authentication |
Invalid email and password |
Attempt to log in with invalid credentials |
Unauthorized access must be denied, and an error message must be displayed |
Unauthorized access is not denied and the user is able to login into someone else account. |
Fail |
Throughput:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Assess data processing speed |
Large dataset |
Input a large dataset into the system |
The system must processes the data within an acceptable timeframe |
The system processes the data within an acceptable timeframe |
Pass |
Logging:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Validate the creation of log entries |
Various actions |
Perform various actions in the system |
The system must generates log entries for each action with timestamps |
The system is generating log entries for each action with timestamps |
Pass |
Performance:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Test system behavior under heavy load |
Varying user data |
Simulate a high number of concurrent users |
The system maintains acceptable performance under heavy load |
[Observed Results] |
Test Case Result |
Reliability:
| Test Case ID |
Test Case Description |
Test Data |
Test Steps |
Expected Results |
Observed Results |
Test Case Result |
| TC#01 |
Verify system stability over an extended period |
N/A |
Keep the system running continuously for 72 hours |
The system must remain stable without crashes or errors |
The system is crashed after a continuous working of 48 Hours |
Fail |