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/adonai-labs/agent-runwayWrote 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/adonai-labs/agent-runway/testing)<a href="https://agentmods.dev/rules/adonai-labs/agent-runway/testing"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/testing/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/adonai-labs/agent-runway/testing"><img src="https://agentmods.dev/badge/rules/adonai-labs/agent-runway/testing.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.00000 | $0.01599 |
| Opus 5.5 | $0.00000 | $0.00640 |
| Sonnet 5.5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
testing 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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategies and Quality Assurance
Directives for writing and reviewing tests. Use Australian English spelling throughout.
Testing Pyramid
- Structure the test suite as a pyramid: many unit tests at the base, fewer integration tests in the middle, few E2E tests at the top.
- Prefer fast, cheap, reliable tests at the bottom; accept slower, more brittle tests only where necessary at the top.
/\ E2E (few) — slow, expensive, brittle
/ \
/____\ Integration (some) — medium speed, more stable
/ \
/ \ Unit (many) — fast, cheap, reliable
/__________\
Unit Testing
- Test one behaviour per test; avoid testing multiple concerns in a single test.
- Use Arrange–Act–Assert: set up data, perform the action, assert the outcome.
- Mock external dependencies (APIs, databases, file system) to isolate the unit under test.
- Use descriptive test names that state the scenario and expected outcome (e.g.
should return null when user is not found). - Aim for 80–90% coverage of critical paths; avoid chasing 100% for its own sake.
- Keep tests fast; avoid real I/O, sleeps, or heavy setup.
Integration Testing
- Test interactions between components, services, or modules.
- Mock external services (third-party APIs, payment gateways) but use real or in-memory databases where appropriate.
- Test database connections, queries, and transactions; use test fixtures and clean up after each run.
- Verify API contracts, request/response shapes, and error handling.
- Prefer bottom-up or sandwich approaches over big-bang integration.
End-to-End Testing
- Test complete user flows (e.g. login → create item → checkout).
- Use
data-testidattributes for stable selectors; avoid CSS classes or XPath that change with styling. - Prefer Cypress or Playwright for web E2E; avoid brittle, implementation-coupled selectors.
- Keep E2E suites small and focused on critical paths; they are slow and costly to maintain.
- Run E2E against a dedicated test environment; avoid production data.
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.
- 16d ago Changed · +18 lines c18cb0507641
- 1mo ago First seen · 139 lines · 0 tokens per session scan A c8b935e691dd
testing is a cursor rule published in the GitHub repository adonai-labs/agent-runway (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,599 tokens. 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
boffin-post-change-audit
Pre-flight review and post-change kernel audit.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
safari-automation
Patterns and best practices for automating Safari browser interactions for web UI automation and testing.
rule-06
This is test rule number in the large package scalability test.