playwright-e2e-testing

Project rules for writing Playwright end-to-end tests, which control a real browser to check complete user flows. They cover test locations, selectors, mocked external services, and checks for chat, sessions, configuration, and user roles.

In plain words
What is it for?
Use them when adding or running tests for chat, session management, AppConfig, or role-based access control, including Admin, Editor, and Viewer behavior.
Why use it?
They make browser tests more reliable and focused, including verifying that each role can access only the actions it should.

Cursor rule for Cursor

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/consensys/ask-o11y-plugin/playwright-e2e-testing
Clone the repo
git clone --depth 1 https://github.com/Consensys/ask-o11y-plugin

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 273 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00273
Opus 5 $0.00000 $0.00137
Sonnet 5 $0.00000 $0.00055
Haiku 4.5 $0.00000 $0.00027

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

Security

Grade A, and why

playwright-e2e-testing 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/playwright-e2e-testing.mdc · 38 lines

What it actually says

Playwright E2E Testing

Reference: CLAUDE.md is the authoritative source.

Test Locations

  • E2E specs in tests/*.spec.ts

Focus

Test critical user flows: chat, session management, AppConfig, RBAC roles. Limit to 3–5 focused tests per file.

Best Practices

  1. Use data-testid selectors from src/components/testIds.ts — not CSS or XPath
  2. Mock external APIs with page.route() for deterministic tests
  3. Auto-waiting — use Playwright's built-in waiting, avoid explicit waitForTimeout
  4. Setup in beforeEach — page navigation and route mocking
  5. Test both success and error scenarios

RBAC Testing

Test RBAC with Admin, Editor, Viewer roles. Viewers must not access write tools.

Run Tests

# Requires running server: nvm use 22 && npm run server
nvm use 22 && npm run e2e
nvm use 22 && npm run e2e -- --grep "test name pattern"
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.

  1. 2d ago First seen · 38 lines · 0 tokens per session scan A 87506cbfdb83

Subscribe to this mod's changes

playwright-e2e-testing is a cursor rule published in the GitHub repository Consensys/ask-o11y-plugin (40 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 273 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-30.