non-Functional
Testing
Ensuring software is optimized for real-world conditions!
Swipe
01
non-Functional Testing
Non-Functional Testing (NFT) focuses on how a system
performs, rather than what it does. Unlike functional
testing, which verifies that the software meets business
requirements,
Non-Functional Testing evaluates performance, security,
usability, and other quality attributes to ensure the
system is reliable, efficient, and user-friendly.
Measures system speed, stability, security, and usability
and identifies bottlenecks, vulnerabilities, and
weaknesses in the system.
Fatimah Hamzah
Swipe
Quality Assurance Engineer
02
Scope
Evaluates software beyond just functional correctness
Includes system behavior, user experience,
infrastructure stability, and operational readiness
Covers performance, security, usability, reliability, and
compatibility testing.
Fatimah Hamzah
Swipe
Quality Assurance Engineer
03
Purpose
Ensure System Performance: Validate speed,
responsiveness, and scalability under different loads
Identify Security Vulnerabilities: Detect potential
threats, breaches, and data protection flaws
Improve User Experience: Ensure intuitive navigation,
accessibility, and usability
Test System Reliability: Verify uptime, failover
handling, and disaster recovery measures
Ensure Compatibility: Check the software’s cross-
device, cross-browser, and cross-platform support.
Fatimah Hamzah Swipe
Quality Assurance Engineer
04
Techniques Used
Load Testing (Performance Validation): Simulates
normal and peak user loads to measure system
response
Stress Testing (System Breakpoint Analysis): Pushes
the system beyond its limits to check when it fails or
crashes
Penetration Testing (Security Weakness
Assessment):Identifies vulnerabilities that could be
exploited by hackers
Configuration Testing (Cross-Platform Compatibility):
Validates how the application runs on different
devices, browsers, and networks.
Fatimah Hamzah Swipe
Quality Assurance Engineer
05
types
Performance Testing (Speed & Stability Validation
Measures response time, system scalability, and
reliability under different workloads.
2. Security Testing (Threat & Risk Assessment
Identifies vulnerabilities related to data protection,
authentication, and compliance.
3. Usability Testing (User-Friendliness & Accessibility
Evaluates ease of navigation, design efficiency, and
accessibility standards.
Fatimah Hamzah Swipe
Quality Assurance Engineer
06
Types
4. Compatibility Testing (Cross-Environment Validation
Ensures software functions correctly across different
devices, OS, and browsers.
5. Reliability Testing (System Stability Over Time
Measures uptime, failure recovery, and crash handling.
6. Compliance Testing (Industry Standard Adherence
Ensures legal, regulatory, and security compliance.
Fatimah Hamzah Swipe
Quality Assurance Engineer
Lastly
A software system isn’t just about what it does—it’s also
about how well it performs, how secure it is, and how
easily users can interact with it.
Non-Functional Testing ensures software is optimized for
real-world conditions, covering speed, security, usability,
compatibility, and stability.
Functional testing might confirm that an app works, but
non-functional testing ensures it works well—both are
essential for a successful product!
Fatimah Hamzah
Swipe
Quality Assurance Engineer
THANK YOU FOR
WATCHING
Fatimah Hamzah
Quality Assurance Engineer