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	$0.00024	$0.00842
Sonnet 5	$0.00010	$0.00337
Haiku 4.5	$0.00005	$0.00168

Measured 10d ago against content hash 76f4a79b7367, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

10d 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 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,684 once invoked, about $0.0002 per session on Opus 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

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

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

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog-foss · 112 tokens

pyats-dynamic-test

Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.

automateyournetwork/netclaw · 61 tokens

test-loop

Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).

HoangNguyen0403/agent-skills-standard · 25 tokens

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens

PlayWright-MCP-Repo: Skill for Claude Code