An end-to-end test skill for checking TestRail MCP tools. End-to-end tests build the project and then test complete user-facing operations across TestRail, a system for managing software test cases and results.

For testing TestRail projects, suites, sections, cases, runs, tests, results, plans, milestones, and shared steps. It always runs a baseline regression suite and reports which areas relate to changed files.

It checks whether the project still builds and whether the TestRail tools work together, instead of testing only isolated parts. It also records tool errors while continuing the regression run.

e2e-test — Skill for Claude Code and Codex by bun913: An end-to-end test skill for checking TestRail MCP tools.

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 skills/bun913/mcp-testrail/e2e-test

Any agent

npx skills add bun913/mcp-testrail --skill e2e-test

Clone the repo

git clone --depth 1 https://github.com/bun913/mcp-testrail

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/bun913/mcp-testrail/e2e-test.svg)](https://agentmods.dev/skills/bun913/mcp-testrail/e2e-test)

Your own site

<a href="https://agentmods.dev/skills/bun913/mcp-testrail/e2e-test"><img src="https://agentmods.dev/badge/skills/bun913/mcp-testrail/e2e-test.svg" alt="Measured on agentmods" 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. 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.

Model	Per session	Once invoked
Fable 5	$0.00049	$0.01684
Opus 5	$0.00024	$0.00842
Sonnet 5	$0.00010	$0.00337
Haiku 4.5	$0.00005	$0.00168

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

Copies of this mod

1 near-identical copy found in the catalogue:

e2e-test — 100% identical, 0 lines differ

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

5d 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 bun913/mcp-testrail (44 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

E2E testing Testing mcp testrail

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

run-integration-tests

Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.

dotnet/maui · 35 tokens

cli-e2e-testcase-writer

Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.

larksuite/cli · 78 tokens

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

every-app/open-seo · 35 tokens

__SKILL_ID__

This fixture verifies that skill content can be written into the target sandbox and queried back immediately.

NVIDIA/NemoClaw · 10 tokens

harness-test-writer

Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…

maximhq/bifrost · 133 tokens