What it does
Covers the non-functional characteristics beyond performance/security/a11y: fixes the targeted ISO/IEC 25010 characteristic and its measurable sub-characteristics, derives test conditions and cases with acceptance criteria, implements the automatable ones, and reports results as numbers vs criteria. Routes perf/security/usability targets to their dedicated commands.
When to use it
When testing reliability, compatibility, portability, maintainability, or functional-suitability aspects of quality.
Prerequisites
qa.config.yml for paths, tooling, browser/device matrix, gates/SLAs, risk_areas; a target 25010 characteristic.
Output
ISO/IEC/IEEE 29119-3 Test Design + Test Case Specification -> docs_dir/NONFUNCTIONAL-<characteristic>.md, plus Test Procedures under tests_dir and Execution Log when run.
Mechanics
How it works
- Read config; route perf/security/usability targets to their owning command
- Resolve the characteristic from arguments (default to highest-risk area)
- Fix the 25010 sub-characteristics in scope, each with a measurable criterion from gates
- Derive test conditions and cases, tracing each to a sub-characteristic and criterion
- Implement the automatable cases with configured tooling
- Run against non-prod where feasible and report results vs criteria with pass/fail
Why it works
The theory behind it
Non-functional test design (CTFL v4.0 §2.2.2; CTAL-TTA) targeting ISO/IEC 25010 product-quality characteristics — each made measurable so it can be gated.
CTFL v4.0 §2.2.2 · CTAL-TTA (Specialist) · ISO/IEC 25010
Example
See it in use
> /qa:nonfunctional reliability✓ Correct when It maps to an ISO/IEC 25010 characteristic with measurable criteria.