New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Edt MCP E2E Testing

by DitriXNew in DitriXNew/EDT-MCP

How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage…

AGPL-3.0Auto-check passedTesting & QA

Install Edt MCP E2E Testing

skills CLI
$ npx skills add DitriXNew/EDT-MCP --skill edt-mcp-e2e-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install DitriXNew/EDT-MCP edt-mcp-e2e-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/DitriXNew/EDT-MCP.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/edt-mcp-e2e-testing .claude/skills/edt-mcp-e2e-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
edt-mcp-e2e-testing
GitHub stars
295
Token cost
~1.3k tokens
SKILL.md length
557 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
AGPL-3.0

At a glance

How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage…

  • Works in 5 steps: One file per tool,… → git-fixture isolation: TestConfiguration… → Verify the effect the RIGHT way per kind= → …
  • Adding/editing a test in tests/e2e/
  • SKILL.md covers What this is, Run it, The rules in brief (details in… and Don't, plus 1 more section
  • Calls git, python and npx

What it does

Edt MCP E2E Testing is an agent skill from DitriXNew/EDT-MCP. How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage, and an anti-cheat bar. Use when adding/editing a test in tests/e2e/, adding a new tool (the coverage ratchet requires a test), or running the suite. (For the older MANUAL per-tool reference checklists see edt-mcp-testing; for Java unit/build see edt-mcp-build-test.)

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing and MCP servers. It works with Model Context Protocol, Git and Java. The licence is AGPL-3.0.

When your agent uses it

  • Adding/editing a test in tests/e2e/
  • Adding a new tool (the coverage ratchet requires a test)
  • Running the suite

Example prompts

  • “/edt-mcp-e2e-testing”

Requirements

  • Python 3
  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. One file per tool, tests/e2e/tools/test_.py, importing ONLY from harness. Adding a new MCP tool? add its test file — the coverage ratchet…
  2. git-fixture isolation: TestConfiguration is a committed fixture. The orchestrator resets it before every test (git reset + git checkout…
  3. Verify the effect the RIGHT way per kind=
  4. Negative coverage is MANDATORY (not just happy): invalid path/object, every XOR/conditional/enum, missing-required, boundaries. Assert…
  5. Anti-cheat (mutation thinking): "would this test FAIL if the tool were broken?" If not, it's a CHEAT. No trivial asserts, no…

What it can do on your machine

Read from SKILL.md and the folder at commit 6d18531. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • python
    • npx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Edt MCP E2E Testing loads about 1.3k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 557 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~121
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from DitriXNew/EDT-MCP at commit 6d18531, republished under its AGPL-3.0 licence (© DitriXNew). 557 words, ~1,279 tokens.

Download SKILL.mdSave it as .claude/skills/edt-mcp-e2e-testing/SKILL.md (or your agent's skills folder).
name
edt-mcp-e2e-testing
description
How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage, and an anti-cheat bar. Use when adding/editing a test in tests/e2e/, adding a new tool (the coverage ratchet requires a test), or running the suite. (For the older MANUAL per-tool reference checklists see edt-mcp-testing; for Java unit/build see edt-mcp-build-test.)

EDT-MCP — automated black-box e2e suite (tests/e2e/)

The full, authoritative, always-current guide is tests/e2e/SKILL.md in the repo. READ IT before writing or running a test — it has the harness API, the worked examples, and the anti-cheat anti-pattern list. This skill is the entrypoint + the rules in brief; the repo file wins on any disagreement (it lives with the harness).

What this is

A Python (stdlib-only) black-box suite: a real MCP client hits the live server on :8765 and asserts the real effect. One file per tool: tests/e2e/tools/test_<tool>.py. Shared base: harness.py. Runner: run_all.py (serial, --junit-xml, per-test timeout). Every registered tool covered (62 today; the coverage ratchet test_coverage_ratchet.py fails the suite if a tools/list tool has no test). Different layer from Java/JUnit (which is headless and can't touch a real project).

Run it

python tests/e2e/run_all.py --project TestConfiguration --junit-xml tests/e2e/e2e-results.xml

Needs a LIVE server on :8765 + TestConfiguration loaded (the dev EDT copy — see the project memory / edt-redeploy loop). Execution is serial (one fixture, one git tree); authoring can be parallel (one agent per tool file). --filter <substr> runs a subset.

The rules in brief (details in tests/e2e/SKILL.md)

  1. One file per tool, tests/e2e/tools/test_<tool>.py, importing ONLY from harness. Adding a new MCP tool? add its test file — the coverage ratchet fails the suite otherwise.
  2. git-fixture isolation: TestConfiguration is a committed fixture. The orchestrator resets it before every test (git reset + git checkout HEAD -- + git clean -fd). Read tools must leave it clean (assert_no_diff()).
  3. Verify the effect the RIGHT way per kind=:
    • read → assert_no_diff() + content.
    • write (file-write, write_module_source) → assert_diff_contains() (on disk).
    • write-metadata (create/add/delete/rename) → MODEL READ-BACK + on-disk structure. Call a read tool and assert the change in the model, AND assert it landed on disk via poll_diff_contains of the structural element (<name>X</name>, <catalogs>Type.X</catalogs> — not the bare name). Metadata writes now persist to disk via forceExport (~1-2s lag → poll). The orchestrator runs reset_fixture+reset_model after these.
    • action → usually assert_no_diff() + status; never run a destructive happy mutation that corrupts the fixture.
    • env-dependent (form-render JVM flag, LanguageTool, debug no-session) → env-robust branch: real result OR a clear actionable sentinel.
  4. Negative coverage is MANDATORY (not just happy): invalid path/object, every XOR/conditional/enum, missing-required, boundaries. Assert error QUALITY (assert_error_quality): names the bad value + actionable next step. A vague/non-actionable tool error → # AUDIT: note + a fix-card; do NOT weaken the test to a bad error.
  5. Anti-cheat (mutation thinking): "would this test FAIL if the tool were broken?" If not, it's a CHEAT. No trivial asserts, no assert_no_diff()-only, no swallowed exceptions, no tolerant matching. A separate anti-cheat reviewer rules REAL/CHEAT.
Show full SKILL.md (147 more words)Show less

Don't

  • Don't add pip dependencies (stdlib only; the client is kept spec-conformant by hand on purpose).
  • Don't assert a metadata-write effect with the BARE name in the diff (it false-matches the parent's collection reference) — assert the structural element via poll_diff_contains, paired with a model read-back. (Metadata writes DO persist now, with a ~1-2s lag.)
  • Don't parallelize the RUN (serial only). Don't call reset_fixture/reset_model in a test (the orchestrator owns them).

Protocol conformance (a separate gate)

This suite tests tool business logic. The MCP protocol itself (initialize handshake, capabilities/version negotiation, Mcp-Session-Id, Accept/Content-Type, isError, ping, SSE) is a different layer, checked by the official modelcontextprotocol/conformance suite — see tests/conformance/ (tests/conformance/README.md). Run: npx @modelcontextprotocol/conformance@latest server --url http://127.0.0.1:8765/mcp --spec-version 2025-11-25 --expected-failures tests/conformance/baseline.yml → green when only the pinned (intentional) gaps fail. Don't mix the two gates.

Related: edt-mcp-tool-conventions (param/error/output canon), edt-mcp-bilingual (ru/en), edt-mcp-build-test (Java unit/build), edt-mcp-testing (manual per-tool checklists), edt-mcp-ready-to-deploy (final pre-merge checklist).

© DitriXNew, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/edt-mcp-e2e-testing of DitriXNew/EDT-MCP.

Open the folder on GitHubat commit 6d18531

Compare with similar skills

Edt MCP E2E Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Edt MCP E2E Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Edt MCP E2E Testing this skillDitriXNew/EDT-MCP295—~1.3kAutomated safety check: PassAGPL-3.0
Qwen Code E2E TestingQwenLM/qwen-code28k—~2.1kAutomated safety check: PassApache-2.0
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0
Glance TestDebugBase/glance156—~827Automated safety check: PassMIT
Tauri Dev MCP Bridgejerrywu001/cc-sessions-viewer394—~1.4kAutomated safety check: WarnMIT
Exploring The WizardPostHog/wizard197—~2.2kAutomated safety check: PassMIT

Similar skills

  • Qwen Code E2E Testing

    QwenLM/qwen-code

    Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.

    28k GitHub stars~2.1k tokensUpdated today
    Testing & QAAuto-check passed

  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Glance Test

    DebugBase/glance

    Run E2E browser tests on any web application using Glance MCP.

    156 GitHub stars~827 tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Tauri Dev MCP Bridge

    jerrywu001/cc-sessions-viewer

    Launches a Tauri app's dev build with the MCP bridge compiled in, so an agent can take screenshots, read the live DOM, click real buttons and call real backend commands.

    394 GitHub stars~1.4k tokensUpdated yesterday
    Testing & QAAuto-check: warnings

  • Exploring The Wizard

    PostHog/wizard

    Official

    Drive the PostHog wizard headlessly against a throwaway app through wizard-ci MCP tools, inspect decisions, and capture the real TUI.

    197 GitHub stars~2.2k tokensUpdated today
    Testing & QAAuto-check passed

  • Playwright Healing Agent

    Tahanima/playwright-java-test-automation-architecture

    Expert in diagnosing Playwright failures. Uses the @playwright MCP to verify live DOM state.

    113 GitHub stars~210 tokensUpdated 7 mo ago
    Testing & QAAuto-check passed

More from DitriXNew/EDT-MCP

All 24 skills in this repo

  • Edt MCP Autopilot

    DitriXNew/EDT-MCP

    Autonomous, spec-driven, multi-agent pipeline that takes an EDT-MCP task or issue end-to-end — research → critics → architect → parallel development → review loop → tests → live-stand check →…

    295 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Edt MCP Build Test

    DitriXNew/EDT-MCP

    How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo.

    295 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Edt MCP Tool Descriptions

    DitriXNew/EDT-MCP

    How to size, write and A/B-test the text of a tool — its description and its inputSchema parameter prose — so that cutting it does not cost call quality, and so that a tool that IS getting called…

    295 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Edt MCP Yaxunit

    DitriXNew/EDT-MCP

    How to write and run YAXUnit unit tests for a 1C configuration through 1C:EDT + the EDT-MCP runyaxunittests / debugyaxunittests tools.

    295 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Edt MCP Testing

    DitriXNew/EDT-MCP

    How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration.

    295 GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Edt MCP Architecture

    DitriXNew/EDT-MCP

    Map of the EDT-MCP plugin's target architecture — where the shared helpers live, the layering rules, and the canonical way to do project/metadata/code resolution.

    295 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Edt MCP E2E Testing

What does Edt MCP E2E Testing do?

How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage…. Edt MCP E2E Testing is an agent skill from DitriXNew/EDT-MCP. How to write/run the AUTOMATED black-box e2e suite (tests/e2e/) that covers every EDT-MCP tool (62 today) against a live server with git-fixture isolation, happy + negative + error-quality coverage, and an anti-cheat bar.

When should I use Edt MCP E2E Testing?

Edt MCP E2E Testing fits situations like: adding/editing a test in tests/e2e/; adding a new tool (the coverage ratchet requires a test); running the suite.

How do I install Edt MCP E2E Testing in Claude Code?

Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-e2e-testing -a claude-code`. Or copy the skill folder (.claude/skills/edt-mcp-e2e-testing in DitriXNew/EDT-MCP) into .claude/skills/edt-mcp-e2e-testing in your project. Claude Code loads it when a task matches its description.

How do I install Edt MCP E2E Testing in Codex?

Run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-e2e-testing -a codex`. Or copy the skill folder (.claude/skills/edt-mcp-e2e-testing in DitriXNew/EDT-MCP) into .agents/skills/edt-mcp-e2e-testing in your project. Codex loads it when a task matches its description.

Can I use Edt MCP E2E Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add DitriXNew/EDT-MCP --skill edt-mcp-e2e-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/edt-mcp-e2e-testing, .gemini/skills/edt-mcp-e2e-testing, .github/skills/edt-mcp-e2e-testing and .opencode/skills/edt-mcp-e2e-testing in your project.

What does Edt MCP E2E Testing need to run?

Going by SKILL.md and its folder, Edt MCP E2E Testing needs the command-line tools its instructions call (git, python and npx). Our summary lists: Python 3; Node.js.

Does Edt MCP E2E Testing access the network?

SKILL.md contains no URLs. Its commands use git and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Edt MCP E2E Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Edt MCP E2E Testing use?

Edt MCP E2E Testing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Edt MCP E2E Testing use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Edt MCP E2E Testing?

Skills that share tags, products or a category with Edt MCP E2E Testing: Qwen Code E2E Testing (QwenLM/qwen-code, 28k stars), Diff-Driven Smoke Tests (Skyvern-AI/skyvern, 23k stars), Glance Test (DebugBase/glance, 156 stars) and Tauri Dev MCP Bridge (jerrywu001/cc-sessions-viewer, 394 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Edt MCP E2E Testing?

DitriXNew (a GitHub user) maintains it in DitriXNew/EDT-MCP, which has 295 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.

Source: DitriXNew/EDT-MCP on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.