A TestRail end-to-end testing workflow. TestRail is a tool for managing test cases and test runs, while end-to-end tests check a system through complete user-level workflows.

It runs regression tests for projects, suites, sections, cases, runs, tests, results, plans, milestones, and shared steps.

It checks that the project builds and that TestRail operations continue to work, including after changes.

How valvacchs/PlayWright-MCP-Repo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to valvacchs/PlayWright-MCP-Repo. 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/valvacchs/PlayWright-MCP-Repo/main/.claude/skills/e2e-test/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/valvacchs/PlayWright-MCP-Repo

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-test/github.svg)](https://agentmods.dev/skills/valvacchs/playwright-mcp-repo/e2e-test)

Your own site

<a href="https://agentmods.dev/skills/valvacchs/playwright-mcp-repo/e2e-test"><img src="https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-test/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/valvacchs/playwright-mcp-repo/e2e-test"><img src="https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,684 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 100% copy Near-identical to another mod 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.00049	$0.01684
Opus 5.5	$0.00020	$0.00674
Sonnet 5.5	$0.00010	$0.00337
Haiku 4.5	$0.00005	$0.00168

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

Security

Grade A, and why

e2e-test 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 1mo 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.

Origin

This is a copy

100% identical to e2e-test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/e2e-test/SKILL.md · 136 lines

How it starts

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

MCP TestRail E2E Test

Overview

Runs E2E regression tests against TestRail using mcp__testrail__* MCP tools directly. Always runs a baseline regression suite regardless of code changes.

Prerequisite: .mcp.json must be configured and MCP tools must be loaded. Run /e2e-setup first if needed.

Step 1: Build the project

npm run build

Ensure the build succeeds before proceeding.

Step 2: Detect changed tools (informational)

git diff main...HEAD --name-only -- src/server/api/ src/client/ src/shared/

Map changed files to categories (for reporting which are "targeted" vs "regression"):

File pattern	Tool category
`projects.ts`	Projects
`cases.ts`	Cases
`sections.ts`	Sections
`suites.ts`	Suites
`runs.ts`	Runs
`tests.ts`	Tests
`results.ts`	Results
`plans.ts`	Plans
`milestones.ts`	Milestones
`sharedSteps.ts`	SharedSteps

This is informational only. All categories are always tested.

Step 3: Run regression tests

Use the mcp__testrail__* tools directly. Each step captures IDs needed for subsequent steps. If a tool call returns an error, log it and continue. Do not abort the entire run.

3a. Projects (read-only)

mcp__testrail__getProjects -> capture a project_id from the response
mcp__testrail__getProject with that project_id

3b. Suites

mcp__testrail__getSuites with project_id -> capture a suite_id

3c. Sections

mcp__testrail__getSections with project_id and suite_id -> capture a section_id

3d. Cases (full CRUD lifecycle)

Create: mcp__testrail__addCase with section_id, title "[E2E] Auto-generated test case", type_id=1, priority_id=2 -> capture case_id
Read: mcp__testrail__getCase with case_id
Update: mcp__testrail__updateCase with case_id, title "[E2E] Updated test case"
Read again: mcp__testrail__getCase to verify update
(Keep case_id for Results tests, delete in cleanup)

Read the full file on GitHub · 136 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.

1mo ago First seen · 136 lines · 49 tokens per session scan A 76f4a79b7367

Subscribe to this mod's changes

e2e-test is a skill published in the GitHub repository valvacchs/PlayWright-MCP-Repo (0 stars, last pushed 3mo ago), licensed MIT. It adds 49 tokens to every session and 1,684 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to e2e-test, differing in 0 lines, and is treated as a copy.

E2E testing Testing

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

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

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

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens

PlayWright-MCP-Repo: Skill for Claude Code