What is 7-testing-standards?

A set of rules for writing and organising tests by feature and behaviour. It distinguishes unit, integration, and end-to-end tests, which check different parts of an application and its connections.

Use it to name tests, structure Given-When-Then steps, prepare test data, choose test doubles, and cover success, failure, and edge cases.

It keeps tests focused, repeatable, readable, and appropriate to the layer of the application being checked.

7-testing-standards — Cursor rule for Cursor by cmnemoi/cursor-rules

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/cmnemoi/cursor-rules

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/cmnemoi/cursor-rules/7-testing-standards/github.svg)](https://agentmods.dev/rules/cmnemoi/cursor-rules/7-testing-standards)

Your own site

<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/7-testing-standards"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/7-testing-standards/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/cmnemoi/cursor-rules/7-testing-standards"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/7-testing-standards.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 271 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.00271
Opus 5.5	$0.00000	$0.00108
Sonnet 5.5	$0.00000	$0.00054
Haiku 4.5	$0.00000	$0.00027

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

Security

Grade A, and why

7-testing-standards 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.

general-rules/.cursor/rules/07-quality-assurance/7-testing-standards.mdc · 39 lines

What it actually says

Organization:

Organize tests by domain/feature in appropriate directory structure
Group related tests by behavior using descriptive test methods

Naming:

Name test methods with should prefix describing behavior
Use descriptive names for test helper methods
Follow Given-When-Then pattern in method names

Test Structure:

Extract test steps into descriptive methods
Use givenXxx() for test setup
Use whenXxx() for executing behavior
Use thenXxx() for assertions
Keep assertions focused and minimal

Test Data:

Use in-memory repositories and gateways over mocks
Create test data in setup methods
Use factories for test entities

Test Quality:

Test behaviors not implementation details
Test both success and failure paths
Keep tests independent and deterministic
Test edge cases and error conditions

Testing strategy:

Unit tests should use test doubles and focus on business logic
Integration tests should use real dependencies and test the adapter without business logic
End to End tests should test that business code and infrastructure code is wired properly and focus on happy path, with all real dependencies

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 · 39 lines · 271 tokens per session scan A e347253b2417

Subscribe to this mod's changes

7-testing-standards is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 271 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.

E2E testing Testing Unit testing

7-testing-standards

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other cursor rules, from other repositories

300-testing

hatch3r-testing

testing

30-testing

tester

go-test