agentleFS
Sign inStart free
ajavadinezhadajavadinezhad/zyrln/.cursor/rules/testing.mdc

zyrln / rules

Cursor rule759 starsChanged 4 months agoMITView on GitHub

Tests document behavior; never bend product logic to make tests pass

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

5 rules. About 0 are common, 5 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When a test fails:

    line 10
  2. Distinctive:

    If the test is wrong or outdated, fix or delete the test — do not add shims, lists, or branches in production code solely to satisfy …

    line 13
  3. Distinctive:

    Do not add “exclude” lists that undo “include” lists, or duplicate configuration, just to reconcile contradictory tests.

    line 14
  4. Distinctive:

    Prefer fixing tests in the same change as a behavior fix.

    line 15
  5. Distinctive:

    If requirements are unclear, ask or read project docs before changing production code.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 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
testing.mdc
---
description: Tests document behavior; never bend product logic to make tests pass
alwaysApply: true
---

# Testing discipline

**Never change runtime behavior, APIs, or user-visible functionality because a test expects something different.**

When a test fails:

1. Decide whether the **code** or the **test** is wrong against the real requirement (docs, issues, invariants).
2. If the test is wrong or outdated, **fix or delete the test** — do not add shims, lists, or branches in production code solely to satisfy assertions.
3. Do not add “exclude” lists that undo “include” lists, or duplicate configuration, just to reconcile contradictory tests.
4. Prefer fixing tests in the same change as a behavior fix; document intentional behavior in a short comment only when non-obvious.

If requirements are unclear, ask or read project docs before changing production code.

Download now (ZIP)

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.

Check your setup, free