Content ITV PRO
This is Itvedant Content department
Non Functional Testing
Performance · Security · Usability
· Compatibility · Quality
What is NON Functional Testing?
Verifies HOW WELL a system performs — not WHAT it does. Evaluates performance, reliability, usability, and security.
⚡ Performance
How fast the system responds under load
🔒 Security
Protection from unauthorized access
🎯 Usability
How easy & satisfying the system is to use
✅ Reliability
Consistent functioning without failure
Types of Non-Functional Testing
1.
📊 Performance / Load Testing
Measures response time under normal and peak load.
Identifies bottlenecks before they hit production.
2.
🔐 Security Testing
Detects vulnerabilities, prevents unauthorized access,
and protects sensitive user data.
3.
🖥️ Usability Testing
Evaluates UI design, navigation flow, and accessibility
to ensure a smooth user experience.
4.
🌐 Compatibility Testing
Ensures the application works correctly across
browsers, devices, and operating systems.
Functional vs Non-Functional Testing
| Functional Testing |
Non-Functional Testing |
|
|---|---|---|
| Focus |
What the system does |
How well the system performs |
| Source |
User requirements |
Quality benchmarks & SLAs |
| Tools |
Selenium, JUnit, TestNG |
JMeter, LoadRunner, Lighthouse |
| Failure Impact |
Incorrect or missing functionality |
Poor performance, security risk, bad UX |
| When |
Throughout development cycle |
After functional testing is stable |
Testing Levels: System & UAT
System Testing — Tests complete end-to-end workflow
3.
Functional
[Ride-Sharing App] Verify: booking → driver allocation → invoice generation flow
Non-Functional
[Video Streaming Platform] Load test with 10,000 concurrent users; measure stability
User Acceptance Testing (UAT) — Final validation by real users
4.
Functional
[HR System] Verify leave request submission and manager approval process
Non-Functional
[Online Learning Platform] Check usability and streaming performance on low-speed internet
Real-World Testing Scenarios
| Functional Testing |
Non-Functional Testing |
|
|---|---|---|
| Web Login | Validates credentials, access rights, account lock after failed attempts |
Response < 2 sec, browser compatibility, brute-force protection |
| Mobile Banking | Displays balance, processes transactions, generates receipt |
Biometric login, encryption, offline capability |
| Streaming App | Plays videos, manages playlists, tracks watch history |
Minimal buffering, adaptive streaming, HD quality support |
7 Principles of Software Testing (1–4)
Testing Shows Presence of Defects
Testing can find bugs — it cannot prove the software is completely bug-free.
Exhaustive Testing is Impossible
You cannot test everything. Prioritize based on risk and business impact.
Early Testing Saves Cost
Start testing early in the SDLC to catch issues before they become expensive.
Defects Cluster Together
Most defects are concentrated in a small number of high-risk modules.
7 Principles of Software Testing (5–7)
Pesticide Paradox
Running the same tests repeatedly finds fewer new bugs. Regularly update and diversify your test cases.
Exhaustive Testing is Impossible
The approach differs for banking apps, medical software, gaming apps, and e-commerce. No one-size-fits-all.
Absence-of-Errors Fallacy
Bug-free software is still useless if it doesn't meet user needs. Testing must align with business goals.
NON Funtional TESTING
By Content ITV
