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.
npx agentmods add rules/bybren-llc/a-safe-pulse/13-testinggit clone --depth 1 https://github.com/bybren-llc/a-safe-pulseWrote 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/bybren-llc/a-safe-pulse/13-testing)<a href="https://agentmods.dev/rules/bybren-llc/a-safe-pulse/13-testing"><img src="https://agentmods.dev/badge/rules/bybren-llc/a-safe-pulse/13-testing.svg" alt="Measured on agentmods" 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.00648 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
13-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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Rules
These rules apply when writing or modifying tests.
Testing Stack
- Framework: Jest with TypeScript support
- Coverage: Built-in Jest coverage (
--coverage) - Runner:
npm test
Test Organization
tests/
unit/ # Fast, isolated unit tests
integration/ # API and database integration tests
Running Tests
# All tests
npm test
# Single test file
npx jest tests/specific-file.test.ts
# Tests matching a pattern
npx jest --testPathPattern="keyword"
# With coverage
npx jest --coverage
# Full CI validation
npm test && npm run build
Coverage Thresholds
These thresholds are enforced in Jest configuration:
| Metric | Minimum |
|---|---|
| Branches | 70% |
| Functions | 80% |
| Lines | 80% |
| Statements | 80% |
Test Patterns
API Integration Tests
See patterns_library/testing/api-integration-test.md for the full pattern.
Key points:
- Mock authentication for isolated testing
- Verify RLS context is used (no direct query calls)
- Test both success and error paths
- Test authentication failures (401)
- Test authorization failures (403)
- Test input validation errors (400/422)
Writing Good Tests
- Independent: Tests must not depend on execution order
- Repeatable: Same result every time, no flaky tests
- Clear naming:
describe('module') > it('should do X when Y') - Arrange-Act-Assert: Follow the AAA pattern
- Edge cases: Cover boundary conditions, empty states, error paths
- RLS isolation: Verify user A cannot access user B's data
Coverage Requirements
- Business logic: Aim for high coverage
- API endpoints: All routes should have integration tests
- Security paths: Authentication and authorization MUST be tested
- Error handling: All error responses MUST be tested
Acceptance Criteria Verification
When testing a spec, map each acceptance criterion to at least one test:
// From spec: "User can create new resource"
it('should create a resource for an authenticated user', async () => {
// ...
});
// From spec: "Validation shows errors for invalid input"
it('should return 422 for invalid input', async () => {
// ...
});
// From spec: "Unauthorized access returns 401"
it('should return 401 for unauthenticated requests', async () => {
// ...
});
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.
- today First seen · 111 lines · 0 tokens per session scan A 85ce02d8809c
13-testing is a cursor rule published in the GitHub repository bybren-llc/a-safe-pulse (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 648 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-09-04.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
python-general-coding-standards
应用一般 Python 编码标准,包括类型提示、使用 Pydantic 进行输入验证、后台任务、CORS 处理、安全工具、PEP 8 合规性和全面测试。.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
project-conventions
Core project conventions for the Uniqlo Sales Alerter.