Overview
The Quality Attributes
Non-functional testing (NFT) focuses on the 'ilities' of a system: reliability, usability, scalability, and maintainability.
For QA Managers, NFT is where Product Perception is born. A feature that works correctly but takes 10 seconds to respond is functionally sound but operationally a failure.
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Include NFT in your 'Definition of Done' for high-traffic features.
- •Use automated tools for Performance and Security scanning (Dast/Sast).
- •Benchmark your results against previous releases to detect 'Performance Regression'.
Common Pitfalls
- •Don't wait until the end of the project to start NFT; it's the most expensive time to fix architectural flaws.
- •Don't ignore Accessibility (a11y) as part of your NFT suite.
The Details
The 6 Pillars of Non-Functional Quality
To manage NFT effectively, QAs should categorize checks into six pillars: Performance, Security, Reliability, Usability, Efficiency, and Portability. In an Agile squad, these are often treated as 'Non-functional Requirements' (NFRs). A common failure in QA strategy is neglecting the 'Portability' pillar—ensuring the app works across different browser engines or mobile OS versions—which can lead to a fragmented user experience.