What is testing-approach?

A set of project rules for testing a web application. It covers small code tests, component tests, and end-to-end tests that check complete user journeys in a browser.

Use it when adding or changing tests, running the project's test commands, checking code coverage, or validating a feature before release.

It gives the agent consistent instructions for choosing, organizing, and running tests, including separate checks for previews, staging, and production.

testing-approach — Cursor rule by thematters

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.

agentmods

npx agentmods add rules/thematters/matters-web/testing-approach

Clone the repo

git clone --depth 1 https://github.com/thematters/matters-web

Made for: Cursor.

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 463 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00007	$0.00463
Opus 5	$0.00003	$0.00231
Sonnet 5	$0.00001	$0.00093
Haiku 4.5	$0.00001	$0.00046

Measured 2d ago against content hash a37a4c24d9fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing-approach 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 2d 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.

.cursor/rules/testing-approach.mdc · 56 lines

What it actually says

Testing Approach

Matters Web uses a combination of unit, component, and end-to-end (E2E) tests.

Testing Framework

Vitest and Testing Library for unit and component tests
Playwright for end-to-end (E2E) tests

Test Structure

Unit and component tests are typically located in a ComponentName.test.tsx file within each component
End-to-end tests are in the tests/ directory

Running Tests

npm run test: Run all tests
npm run test:unit: Run unit and component tests
npm run test:e2e: Run end-to-end tests
npm run test:unit:coverage: Generate coverage report

Release Evaluation Boundary

Use the shared release evaluation standard when testing feature launches:

Preview and PR checks should use the Vercel preview URL through PLAYWRIGHT_TEST_BASE_URL.
matters.icu is the staging acceptance target and may use disposable test data.
matters.town production checks are read-only by default; production mutations, admin actions, payment actions, moderation changes, or outbound delivery require explicit human approval.
Keep CI status, staging acceptance, production deployment, and production smoke-test results separate.

See docs/e2e-release-evaluation.md for the repo-local guide.

Testing Utilities

Mock data and fixtures for testing
Utility functions for common test operations
Custom test renderers for components with specific requirements

Key Test Files

vitest.config.ts: Vitest configuration
vitest.setup.ts: Vitest setup file
playwright.config.ts: Playwright configuration

Testing Best Practices

Make sure to create corresponding unit tests when adding a new component.
Tests should be independent and not rely on the state of other tests
Use testing-library queries that align with how users interact with the application
Mock API responses for component tests

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.

2d ago First seen · 56 lines · 7 tokens per session scan A a37a4c24d9fe

Subscribe to this mod's changes

testing-approach is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 463 once invoked, about $0.0000 per session on Opus 5. 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-30.

Frontend Git and workflow Testing apollo apollo-client matters platform

tutorial-system-guide

This guide documents the complete tutorial infrastructure in Windmill's frontend, enabling developers to create new interactive tutorials without re-exploring the codebase.

windmill-labs/windmill · 3,888 tokens

windmill-overview

Windmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.

windmill-labs/windmill · 0 tokens

testing-approach