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.
npx agentmods add rules/m3au/playwright-bdd-cursor-template/writing-testsgit clone --depth 1 https://github.com/m3au/playwright-bdd-cursor-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/m3au/playwright-bdd-cursor-template/writing-tests)<a href="https://agentmods.dev/rules/m3au/playwright-bdd-cursor-template/writing-tests"><img src="https://agentmods.dev/badge/rules/m3au/playwright-bdd-cursor-template/writing-tests.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.00731 |
| Opus 5 | $0.00000 | $0.00365 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
writing-tests 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Tests
Test Organization
Tests are organized by challenge in tests/e2e/challenges/:
tests/e2e/challenges/uitestingplayground/- UI testing challenges (23 scenarios)tests/e2e/challenges/automationexercise/- E-commerce challenges (15 scenarios)tests/e2e/challenges/jsonplaceholder/- API testing challenges (34 scenarios)
Each challenge contains:
features/- Gherkin feature files (.feature)poms/- Page Object Models with BDD decoratorspages/- Page-level POMscomponents/- Reusable component POMs (UITestingPlayground only)
services/- API Object Models (JSONPlaceholder only)
Unit tests are in tests/unit/ and achieve 100% coverage for utilities and scripts.
Test Writing Patterns
BDD with Gherkin
Tests use Gherkin feature files with BDD decorators directly on POM methods. No separate step-definition files needed.
See tests/e2e/challenges/uitestingplayground/features/element-identification.feature and tests/e2e/challenges/automationexercise/features/product-browsing.feature for feature file examples.
See tests/e2e/challenges/uitestingplayground/poms/pages/verify-text-page.ts and tests/e2e/challenges/automationexercise/poms/pages/product-details-page.ts for POM implementation examples.
Testing Conventions
- A: use
@Fixturedecorator on POM classes (seepom.mdcfor details) - A: use Playwright's semantic locators (see
playwright.mdcfor locator guidance) - A: use
expect()assertions (seeplaywright.mdcfor assertion patterns) - A: use environment variables via
environment('BASE_URL_*')fromtests/e2e/world.ts - A: write independent tests - each test should be isolated
- A: use data-driven tests with
Scenario Outline:andExamples:in Gherkin when appropriate
Before Writing a Test
- If fixing a bug, write the test first and ensure it fails (as expected) before the fix
- Always attempt to find related tests in existing files before creating new test files
- When expected behavior is ambiguous, defer to Playwright best practices and accessibility standards
- For regression tests, place in appropriate challenge directory with descriptive scenario name
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.
- 3d ago First seen · 67 lines · 0 tokens per session scan A 858d79f5e035
writing-tests is a cursor rule published in the GitHub repository m3au/playwright-bdd-cursor-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 731 tokens. 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-31.
Other cursor rules, from other repositories
testing
Testing strategy for AI developers.
issues-tests
Backend test conventions — QuarkusTest, REST Assured, Given, ArchUnit.
do-runner
Use the following runners.
typescript-tests
TypeScript and Vitest testing standards for this repo.
testing
Use when writing or reviewing tests. Covers test structure (AAA pattern), unit/integration/e2e placement, database cleanup, and test data setup.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.