A set of rules for writing and organizing software tests. It covers test names and structure, mocking outside services, code coverage, edge cases, and test speed.

Use it when creating or changing tests, especially when deciding where test files belong, how to name them, what to mock, and which success and error cases to cover.

It gives AI-assisted development consistent expectations for tests and reduces duplicated, slow, or incomplete test coverage.

testing — Cursor rule for Cursor by davidl71

Install

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.

Clone the repo

git clone --depth 1 https://github.com/davidl71/project-management-automation

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/davidl71/project-management-automation/testing/github.svg)](https://agentmods.dev/rules/davidl71/project-management-automation/testing)

Your own site

<a href="https://agentmods.dev/rules/davidl71/project-management-automation/testing"><img src="https://agentmods.dev/badge/rules/davidl71/project-management-automation/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/davidl71/project-management-automation/testing"><img src="https://agentmods.dev/badge/rules/davidl71/project-management-automation/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00380
Opus 5.5	$0.00000	$0.00152
Sonnet 5.5	$0.00000	$0.00076
Haiku 4.5	$0.00000	$0.00038

Measured 1mo ago against content hash 52537a907737, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.cursor/rules/testing.mdc · 52 lines

What it actually says

Testing Rules

Test Organization

File Structure

One test file per tool/module: project_management_automation/tools/automation_opportunities.py → tests/test_automation_opportunities.py
Dedicated files for shared utilities: Shared network utilities → tests/test_utils_network.py
Avoid duplicate tests: Never duplicate the same test in multiple files

Naming Conventions

Use descriptive test names: test_find_automation_opportunities_success (not test_success)
Include context in names to prevent duplicates across files
Group related tests into test classes: TestAutomationOpportunitiesTool

See: Test Organization Guidelines

Test Structure

Use descriptive test names
Follow Arrange-Act-Assert pattern
One assertion per test when possible
Group related tests into test classes

Mocking

Mock external dependencies
Use dependency injection for testability
Reset mocks between tests

Coverage

Aim for >80% code coverage
Cover edge cases and error paths
Test both happy and unhappy paths

Performance

Keep tests fast (<1s each)
Use fixtures for expensive setup
Run tests in isolation

Running Tests

Always use uv run pytest to run tests
Never use pip install or manual virtual environments
Example: uv run pytest tests/ -v

Checking for Duplicates

Run uv run python scripts/check_duplicate_test_names.py before committing
Ensure no duplicate test names across different files

Changes

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 · 52 lines · 0 tokens per session scan A 52537a907737

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 380 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.

Testing

testing