HomeGitHub
Docs/Quality/Testing

Testing

Add unit tests deliberately and use the right evidence for logic, UI, and integration work.

Qualityguidetestingunit-tests

Testing is opt-in

Blueprint cannot know the correct runner for every stack, so it does not install one by default. Run /tests when the project is ready to make unit tests part of the workflow.

The project switch

A test command in the AGENTS.md Commands section turns tests into a gate. Logic-bearing implementation steps must add focused coverage and keep the suite green.

Match proof to the work

Work Best evidence
Parser, validator, formatter, or action Focused unit test with edge cases
Responsive UI or visual component Production build and browser screenshot
Form, navigation, or download flow Real browser interaction and console check
API endpoint Representative request, response, and error path

Avoid false confidence

An empty suite should not report success. A build does not prove a click flow. A screenshot does not prove a validator handles malformed input. Use the smallest evidence that directly tests the claim.

Documentation

Search AI Blueprint

Start typing to search the documentation.