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

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

Angular testing: the repo's runner (Vitest), TestBed with standalone components, signal inputs, HTTP testing, Playwright e2e

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Test-first from the acceptance criteria.

    line 9
  2. Distinctive:

    Test through the rendered DOM and public API: what the user sees and does, not private fields.

    line 13
  3. Distinctive:

    Every new UI string: a test (or the build) fails when a key is missing from a language file.

    line 19
  4. Distinctive:

    Never skip, delete or weaken a test to pass the gate.

    line 21

≈ “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
angular-testing.mdc
---
description: "Angular testing: the repo's runner (Vitest), TestBed with standalone components, signal inputs, HTTP testing, Playwright e2e"
globs: **/*.spec.ts,**/*.test.ts,**/e2e/**/*.ts,**/playwright.config.*
alwaysApply: false
---
<!-- Generated by armature from stack-angular/rules/angular/testing.md. Edit the source rule, not this file. -->
# Angular testing

- Test-first from the acceptance criteria. Use the runner the repo configures (`ng test --watch=false`; Vitest in new
  projects).
- Standalone components: `TestBed.configureTestingModule({ imports: [TheComponent] })`; set signal inputs with
  `fixture.componentRef.setInput('name', value)`.
- Test through the rendered DOM and public API: what the user sees and does, not private fields. CDK harnesses for
  library widgets.
- HTTP: `provideHttpClient(), provideHttpClientTesting()`, `HttpTestingController`, and `httpMock.verify()` after each
  test.
- Services and pure functions are tested without a fixture; pipes as plain functions.
- Router-dependent components with `RouterTestingHarness`.
- Every new UI string: a test (or the build) fails when a key is missing from a language file.
- Playwright e2e for the critical flows, on synthetic data, at a phone and a desktop width.
- Never skip, delete or weaken a test to pass the gate.

<!-- Adapted from affaan-m/ECC rules/angular/testing.md (MIT) at d2ef268; merged with the owner's conventions (personal-finance-sdd: Vitest via ng test, Playwright e2e, synthetic data, i18n keys in every language file). -->

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.