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

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

TypeScript testing: Vitest, Testing Library by user-visible behaviour, Playwright for flows, test-first

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Very specific:

    Never: delete, skip (.skip, .only, xit) or weaken a test to make the gate pass.

    line 18
  2. Distinctive:

    Test data is synthetic: no real names, emails, accounts or customer data in fixtures.

    line 19

≈ “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
typescript-testing.mdc
---
description: "TypeScript testing: Vitest, Testing Library by user-visible behaviour, Playwright for flows, test-first"
globs: **/*.test.ts,**/*.test.tsx,**/*.spec.ts,**/*.spec.tsx,**/__tests__/**,**/e2e/**,**/vitest.config.*,**/playwright.config.*
alwaysApply: false
---
<!-- Generated by armature from stack-typescript/rules/typescript/testing.md. Edit the source rule, not this file. -->
# TypeScript testing

- **Test-first.** A behaviour change starts with a failing test taken from the acceptance criteria.
- **Runner:** Vitest for unit and component tests (Jest only where the repo already uses it). One runner per repo.
- **Components:** Testing Library, tested by what the user sees and does. Query by role and accessible name first,
  then label, then text; `data-testid` only as a last resort. `userEvent` (awaited) instead of `fireEvent`.
- **Async:** `findBy*` or `waitFor`, never a `setTimeout` followed by an assertion.
- **Network:** mock at the network boundary (MSW or a fake server), not by mocking the fetch wrapper.
- **No snapshot tests of rendered components**; they get rubber-stamped. Use real assertions, and screenshots in
  Playwright for visual regressions.
- **End to end:** Playwright for the critical user flows, against a running app with synthetic data.
- **Never** delete, skip (`.skip`, `.only`, `xit`) or weaken a test to make the gate pass.
- Test data is synthetic: no real names, emails, accounts or customer data in fixtures.

<!-- Adapted from affaan-m/ECC rules/typescript/testing.md and rules/react/testing.md (MIT) at d2ef268; merged with the owner's conventions (ordo-frontend AGENTS.md: Vitest + Testing Library by behaviour, Playwright for flows; personal-finance-sdd: test-first, synthetic data). -->

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.