agentic-playwright test-standards.instructions.md

A set of rules for writing and organizing Playwright tests, which automate checks in web browsers. It defines which test fixtures, tags, assertions, cleanup steps, and file locations to use.

In plain words
What is it for?
Use it when adding or reviewing Playwright tests. It helps classify tests, choose their location and type, apply one required tag, and add cleanup for tests that change state.
Why use it?
It prevents inconsistent test structure and common testing mistakes, such as using fixed delays or leaving changed data behind. It also makes each test’s purpose easier to identify.

Instructions file for GitHub Copilot

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 instructions/idavidov13/agentic-playwright/test-standards
Clone the repo
git clone --depth 1 https://github.com/idavidov13/agentic-playwright

Made for: GitHub Copilot.

Per session 3,234 This file is loaded in full into every session.
When invoked 3,234 The same file — it is already loaded in full.
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.03234 $0.03234
Opus 5 $0.01617 $0.01617
Sonnet 5 $0.00647 $0.00647
Haiku 4.5 $0.00323 $0.00323

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

Security

Grade A, and why

agentic-playwright test-standards.instructions.md 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.

.github/instructions/test-standards.instructions.md · 278 lines

How it starts

The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Standards

Critical

  • Imports: Import test and expect from fixtures/pom/test-options.ts. NEVER from @playwright/test in spec files.
  • Single-tag rule: Each test has exactly one tag chosen from @smoke | @sanity | @regression | @e2e | @api | @destructive. NEVER combine tags. NEVER use @functional. NEVER put tags on test.describe() blocks.
  • @destructive is the heaviest tag and always wins — but only for shared/global state. A test that mutates state other tests or users depend on (locale, permissions, roles, guest access, feature flags, global settings) is tagged only @destructive. A test that creates and deletes only its own data is isolated, not destructive — tag it by importance (@smoke / @sanity / @regression / @e2e / @api).
  • Every state-mutating test must have test.afterEach() or test.afterAll() cleanup that reverts the change — both @destructive shared-state tests and isolated tests that write their own data.
  • Web-first assertions only (await expect(locator).toBeVisible(), .toHaveText(), .toBeEnabled(), .toHaveCount(...), etc.). NEVER page.waitForTimeout(...).
  • Use test.step() for Given/When/Then structure when a test has more than one distinct phase (setup, action, assertion).
  • Tests must be independent. No ordering dependencies, no shared mutable state across tests.
  • NEVER commit explore-only or debug test files (.spec.ts containing console.log(await page.content()), temporary probes, etc.).
  • Static test data is imported from .ts modules (test-data/static/**/*.ts) via named as const exports. NEVER .json.
  • Dynamic happy-path data comes from Faker factories (test-data/factories/{area}/); universal type-mismatch arrays from test-data/static/util/invalid-values.ts; domain-specific curated sets from test-data/static/{area}/*.ts. See the data-strategy skill.
  • Page objects are consumed via the fixture (async ({ appPage }) => ...). NEVER new PageObject(page) inside a test.
  • After adding or modifying a test file, run the affected tests and confirm zero failures before finishing the task.

Read the full file on GitHub · 278 lines

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 · 278 lines · 3,234 tokens per session scan A 1a513cb87dc5

Subscribe to this mod's changes

agentic-playwright test-standards.instructions.md is an instructions file published in the GitHub repository idavidov13/agentic-playwright (139 stars, last pushed 5d ago), licensed MIT. It adds 3,234 tokens to every session, about $0.0162 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.