---
title: "Non-functional tests · Agent Wranglers"
url: https://agentwranglers.se/playbook/testing/non-functional-tests
updated: 2026-10-20
licence: "All rights reserved"
---

# Non-functional tests

By Erik Bergstedt, Agent Wranglers. Updated 2026-10-20.

> 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.

**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`.

## Required

- [Check accessibility in every build](https://agentwranglers.se/playbook/testing/non-functional-tests/accessibility-in-ci): Run 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](https://agentwranglers.se/playbook/testing/non-functional-tests/llm-evals): Test every AI feature against a fixed set of graded examples, and fail the build when the score drops.

## Recommended

- [Test load against a budget](https://agentwranglers.se/playbook/testing/non-functional-tests/load-tests): Before 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](https://agentwranglers.se/playbook/testing/non-functional-tests/fuzz-parsers): Feed generated and random input to every parser of outside data, and turn every crash into a regular test.

- Previous: [Test quality](https://agentwranglers.se/playbook/testing/test-quality)
- [All chapters](https://agentwranglers.se/playbook/testing)