Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/dobryakov/cursor-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/dobryakov/cursor-rules/testing-rules)<a href="https://agentmods.dev/rules/dobryakov/cursor-rules/testing-rules"><img src="https://agentmods.dev/badge/rules/dobryakov/cursor-rules/testing-rules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/dobryakov/cursor-rules/testing-rules"><img src="https://agentmods.dev/badge/rules/dobryakov/cursor-rules/testing-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00287 | $0.00287 |
| Opus 5.5 | $0.00115 | $0.00115 |
| Sonnet 5.5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
testing-rules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Testing Strategy
- Do not run tests on the host! Run tests inside docker containers.
- After completing each task, run the relevant automated tests, including browser and performance tests whenever possible.
- Choose the environment according to the type of tests: put unit tests inside the service container, put API and e2e tests in separate test containers. Make sure to add the tests dir to the image.
- Connect test containers to the main
docker-compose.yml. - Before starting tests, check if the test container needs to be rebuilt and migrations applied.
- If the project includes an SDK or software clients, they must be covered by separate tests.
- If using Playwright, make sure you have browsers installed to the test container.
- If using Playwright, consider to use proper "FROM" image (for example, debian-based node.js image) in the Dockerfile before building test container.
- When calling
docker compose logswithtail, use proper syntax:docker compose logs --tail 10 <container name>. - It is recommended to include tests dir to the container as
volumesin docker-compose.yml to re-run the tests without re-building the image. - Always try first to debug the errors/warnings by running the corresponding tests. Add the tests if its needed.
- After fixing every bug, write tests to cover it, and run them.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 19 lines · 287 tokens per session scan A 2613318e5415
testing-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 4mo ago), licensed MIT. It adds 287 tokens to every session, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.