e2e-testing

e2e-testing is a skill for Claude Code from careerchain-ys/stdd. It costs 80 tokens per session (4,588 once invoked), scanned A, original, Apache-2.0.

A guide for creating and running Playwright end-to-end tests. Playwright is a tool that drives a browser to test what users see and do.

In plain words
What is it for?
Use it to organize tests by application, write login and page-flow checks, choose accessible locators, and run tests locally or in GitHub Actions.
Why use it?
It encourages stable element selection and checks rendered results, which helps reduce fragile tests and false failures.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is } from '../../fixtures/<apps[].id>/test-fixtures';.

Good fit Use it to organize tests by application, write login and page-flow checks, choose accessible locators, and run tests locally or in GitHub Actions.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/careerchain-ys/stdd
agentmods
npx agentmods add skills/careerchain-ys/stdd/e2e-testing

Made for: Claude Code.

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.

agentmods badge for e2e-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/careerchain-ys/stdd/e2e-testing/github.svg)](https://agentmods.dev/skills/careerchain-ys/stdd/e2e-testing)
Your own site
<a href="https://agentmods.dev/skills/careerchain-ys/stdd/e2e-testing"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/e2e-testing/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.

agentmods 80×15 button for e2e-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/careerchain-ys/stdd/e2e-testing"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/e2e-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,588 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.04588
Opus 5.5 $0.00032 $0.01835
Sonnet 5.5 $0.00016 $0.00918
Haiku 4.5 $0.00008 $0.00459

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

Security

Grade A, and why

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

plugins/playwright/skills/e2e-testing/SKILL.md · 430 lines

How it starts

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

E2Eテスト作成・実行スキル

対象プロジェクトにおけるPlaywright E2Eテストの作成・実行ガイド。

Quick Start

1. テストファイルの配置

.stdd.config.yml の各 apps[] ごとにサブディレクトリを分けて配置する(apps[].id をディレクトリ名に用いる)。

e2e/tests/
├── <apps[].id>/       # 各 apps[] の E2Eテスト(apps[] の数だけ繰り返す)
│   └── *.spec.ts
└── ...

2. 基本的なテスト構造

対象アプリのベースURLは .stdd.config.yml の apps[].port から組み立てる(http://localhost:<apps[].port>)。ハードコードしないこと。

import {
  test,
  expect,
  loginWithCredentials,
} from '../../fixtures/<apps[].id>/test-fixtures';

test.describe('機能名', () => {
  test('テストケース名', async ({ page, testUser }) => {
    // 認証が必要な場合はUIからログイン
    await loginWithCredentials(page, testUser.email, testUser.password);

    // テスト実行(ベースURLは apps[].port から組み立てる)
    await page.goto(`http://localhost:${process.env.PORT}/dashboard`);
    await expect(
      page.getByRole('heading', { name: 'ダッシュボード' }),
    ).toBeVisible();
  });
});

3. テスト実行(ローカル)

cd e2e
npx playwright test tests/<apps[].id>/login.spec.ts --headed

Locator選択の優先順位

重要原則: ユーザーが実際に見たり操作する「レンダリングされた出力」をテスト対象にすること。

優先度 Locator 用途 例
1 getByRole ボタン、リンク、見出し、フォーム要素 getByRole('button', { name: 'ログイン' })
2 getByLabel フォーム入力欄(label紐づき) getByLabel('メールアドレス')
3 getByPlaceholder プレースホルダーがある入力欄 getByPlaceholder('[email protected]')
4 getByText 静的テキストコンテンツ getByText('登録完了しました')
5 getByTestId 上記で特定できない場合の最終手段 getByTestId('submit-button')
❌ locator('selector') 避ける: CSSセレクタやXPath locator('input[type="email"]')

良い例と悪い例

// ✅ 良い例: アクセシビリティlocatorを使用
await page.getByRole('button', { name: 'ログイン' }).click();
await page.getByLabel('メールアドレス').fill('[email protected]');
await expect(
  page.getByRole('heading', { name: 'ダッシュボード' }),
).toBeVisible();

// ❌ 悪い例: CSSセレクタを使用
await page.locator('button[type="submit"]').click();
await page.locator('input[type="email"]').fill('[email protected]');
await expect(page.locator('h1')).toContainText('ダッシュボード');

Read the full file on GitHub · 430 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. 2mo ago First seen · 430 lines · 80 tokens per session scan A b54b0f982258

Subscribe to this mod's changes

e2e-testing is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 4,588 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens