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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/testing)<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/testing"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/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/boparaiamrit/skills-by-amrit/testing"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/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.00390 |
| Opus 5.5 | $0.00000 | $0.00156 |
| Sonnet 5.5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
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 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 Rules
Test Structure
- Use descriptive test names:
should return empty array when no items match filter - One assertion per test (or closely related assertions)
- Follow Arrange-Act-Assert (AAA) pattern
- Group related tests with
describeblocks by feature/behavior
Test Coverage
- Every new feature needs tests for:
- Happy path — Normal expected behavior
- Error paths — What happens when things go wrong
- Edge cases — Null/undefined, empty arrays, max values, concurrent access
- Boundary conditions — Min/max values, exactly at limits
Test Independence
- Tests must run in any order
- Tests must not share mutable state
- Each test sets up its own data (use setUp/beforeEach)
- Clean up after tests (use tearDown/afterEach)
Mocking
- Mock external dependencies (APIs, databases, file system)
- Don't mock internal implementation details
- Prefer dependency injection over monkey-patching
- Verify mock interactions when behavior matters
Anti-Patterns (AVOID)
- Testing implementation instead of behavior
- Brittle tests that break on refactoring
- Tests that depend on execution order
- Over-mocking (mocking the thing you're testing)
- Snapshot tests for dynamic content
- Ignoring test failures ("it's flaky")
Test Quality
- Tests ARE documentation — they show how code is intended to be used
- If a test is hard to write, the code may need refactoring
- Test coverage should never decrease with new changes
- Run the full test suite before committing
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 · 47 lines · 0 tokens per session scan A 45a3a8c489a6
testing is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 390 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
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.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.