Non-functional testing evidence
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
define what evidence proves each non-functional requirement (NFR) is met.
Planned topics
- Every NFR needs a measurable target and a test that produces evidence: performance, security, resilience, recoverability.
- Performance: load test at peak volume with realistic data, reporting response times against the target.
- Security: penetration test, dependency and configuration scans, and results of fixes.
- Resilience: fail a dependency (ERP down, payment provider slow) and show the system degrades as designed; recovery tested against the RTO/RPO.
- Evidence must be reproducible and tied to a requirement ID, not a verbal "it was fine".
Draft outline details
Demonstration
an evidence table for Larkspur: requirement (checkout p95 under agreed limit at peak), test (load test with Black Friday volume), evidence (report), owner, status.
Check your understanding
What makes NFR evidence acceptable?
Show answer
It is measured against a stated target, reproducible, and traceable to a requirement.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.