agentleFS
joaoguimaraesprojoaoguimaraespro/personal-finance/.cursor/rules/common-testing.mdc

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

Test-first workflow, test structure and naming, what never to do to a failing test

  • Reads credentials

The file

We split this common-testing.mdc into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the failing test from the acceptance criteria (RED).

    line 10
  2. Distinctive:

    Write the minimal code to pass (GREEN).

    line 11
  3. Very specific:

    Run the project gate (VERIFY_CMD in .agent-loop.env, or the commands in AGENTS.md).

    line 13
  4. Distinctive:

    Every bug fix starts with a test that reproduces the bug.

    line 22
  5. Distinctive:

    Test data is synthetic. Never real personal data, client data or production identifiers in tests or fixtures.

    line 29
  6. Distinctive:

    Delete, skip or weaken a test to make the gate pass.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
common-testing.mdc
---
description: "Test-first workflow, test structure and naming, what never to do to a failing test"
globs: 
alwaysApply: true
---
<!-- Generated by armature from core/rules/common/testing.md. Edit the source rule, not this file. -->
# Testing (all languages)

## Test first
1. Write the failing test from the acceptance criteria (RED). Run it and see it fail for the right reason.
2. Write the minimal code to pass (GREEN).
3. Refactor with the tests green.
4. Run the project gate (`VERIFY_CMD` in `.agent-loop.env`, or the commands in `AGENTS.md`). The agent's claim that
   it works never counts; the gate does.

The `tdd-guide` agent implements one task this way.

## What to test
- Unit tests for domain logic and utilities; integration tests for endpoints, database access and external
  integrations; end-to-end tests for the critical user flows.
- Aim for 80% line coverage on new code as a floor, not a goal; test behaviour, not implementation details.
- Every bug fix starts with a test that reproduces the bug.

## Structure
- Arrange, Act, Assert. One behaviour per test.
- Names describe the behaviour: `returns_empty_list_when_no_match`, `rejects token with wrong audience`.
- Tests are isolated: no order dependence, no shared mutable state, no real network or clock unless the test is
  about them.
- Test data is synthetic. Never real personal data, client data or production identifiers in tests or fixtures.

## Never
- Delete, skip or weaken a test to make the gate pass. Fix the code; change a test only when the test is wrong,
  and say why in the commit. (The Armature test guard fails the attempt on removed or skipped tests.)

<!-- Adapted from affaan-m/ECC rules/common/testing.md (MIT) at d2ef268; merged with the owner's test-first and synthetic-data rules. -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.