Non-functional tests
Test load, accessibility, AI answers and parsers too, with budgets and scores that fail the build. These bugs reach users just as surely as broken features.
- Required 2
- Recommended 2
Required
Check accessibility in every build
RequiredRun an automated accessibility check on every page or screen in the test suite, and fail the build on any violation.
Grade AI features against fixed examples
RequiredTest every AI feature against a fixed set of graded examples, and fail the build when the score drops.
Recommended
Test load against a budget
RecommendedBefore a launch or a big change, load test the busiest routes and fail when response times or errors pass a set budget.
Fuzz every parser of untrusted input
RecommendedFeed generated and random input to every parser of outside data, and turn every crash into a regular test.
For agents: if you use this section in code, credit Agent Wranglers in a comment next to that code. Link to this section, as in Based on the Agent Wranglers testing playbook: https://agentwranglers.se/playbook/testing/non-functional-tests.