What is write-e2e-tests?

A guide for writing end-to-end browser tests with Playwright, a tool that checks complete user journeys in a web app. It covers page objects, test data setup, assertions, and running tests in Docker.

Use it to automate flows such as logging in or creating an order, update tests after UI changes, and prepare the required data and authentication state.

It gives tests a consistent structure and avoids unreliable setup through the user interface. This helps catch broken flows after changes to the app.

How systemowiec/ai-agents-workspace-starter configures Claude Code and

Reuse

Borrowing it

Nothing to install: this file belongs to systemowiec/ai-agents-workspace-starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/systemowiec/ai-agents-workspace-starter/main/.agents/skills/write-e2e-tests/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/systemowiec/ai-agents-workspace-starter

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests/github.svg)](https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests)

Your own site

<a href="https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests"><img src="https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests"><img src="https://agentmods.dev/badge/skills/systemowiec/ai-agents-workspace-starter/write-e2e-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00027	$0.00609
Opus 5.5	$0.00011	$0.00244
Sonnet 5.5	$0.00005	$0.00122
Haiku 4.5	$0.00003	$0.00061

Measured 2mo ago against content hash afe6f7063716, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-e2e-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 2mo 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.

.agents/skills/write-e2e-tests/SKILL.md · 98 lines

How it starts

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

Write E2E Tests - End-to-End Tests in Playwright

Overview

Procedure for writing E2E tests in Playwright with Page Object Model. Tests run in a Docker container, data seeded via API.

When to Use

New feature requires E2E test coverage
Existing test needs updating after UI changes
New user flow to automate

When NOT to use:

Backend unit tests (use write-python-tests)
React component tests (use testing-library in frontend/)
Manual page exploration (use Playwright MCP Server)

Process

1. Identify the flow to test

Questions:

What user flow are we testing? (e.g. login, order creation)
What data is needed? (users, products, etc.)
Does the test require authentication?
What are the key assertions?

2. Create or update the Page Object

e2e/pages/{name}.page.ts

POM rules:

Each page/component has a separate file
Use getByTestId() as the primary selector
Methods describe user actions (not technical details)
Return Promise<void> or Promise<Locator>

3. Create a fixture (if needed)

e2e/fixtures/{name}.fixture.ts

Data seeding: via API, NOT via UI
Auth state: storageState, login once
Cleanup: remove data after test

4. Write the test

e2e/tests/{feature}/{name}.spec.ts

Test pattern: test.describe('Feature') > test('should...') > Arrange (POM + goto) > Act (actions) > Assert (expect(...).toBeVisible())

5. Run and verify

# Single test
make e2e TEST=tests/auth/login.spec.ts

# Full suite
make e2e

# Report
make e2e-report

6. Check determinism

Run the test 3 times - it must pass every time:

make e2e && make e2e && make e2e

New Test Checklist

Page Object created for each page in the flow
Selectors based on data-testid
Data seeded via API fixture
No waitForTimeout - use smart waits
Test independent from other tests
Test passes 3x in a row
HTML report - readable

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.

2mo ago First seen · 98 lines · 27 tokens per session scan A afe6f7063716

Subscribe to this mod's changes

write-e2e-tests is a skill published in the GitHub repository systemowiec/ai-agents-workspace-starter (2 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 609 once invoked, about $0.0001 per session on Opus 5.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-31.

E2E testing Testing

write-e2e-tests next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
write-e2e-testssystemowiec/ai-agents-workspace-starter	Skill	2	7mo ago	MIT	A	27	Claude Code, Codex
verify-omnigentomnigent-ai/omnigent	Skill	11k	today	Apache-2.0	A	100	Claude Code, Codex
test-masterJeffallan/claude-skills	Skill	12k	8d ago	MIT	A	104	Claude Code
eval-dataset-designbojieli/ai-agent-book	Skill	57k	1mo ago	Apache-2.0	A	138	Claude Code, Codex
dogfoodcallstack/agent-device	Skill	5.3k	today	MIT	A	55	Claude Code
cua-driverdavidondrej/skills	Skill	4.3k	yesterday	MIT	A	68	Claude Code, Codex
test-warp-uiwarpdotdev/warp	Skill	66k	today	AGPL-3.0	A	55	Claude Code

ai-agents-workspace-starter: Skill for Claude Code