Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

edt-mcp-build-test

Estrelas218

Forks48

Atualizado8 de junho de 2026 às 13:49

How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

DitriXNew

DitriXNew/EDT-MCP

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	edt-mcp-build-test
description	How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.

EDT-MCP — build and tests

Layout

Maven/Tycho reactor: mcp/ (bom, bundles, features, repositories, targets, tests).
Unit tests: mcp/tests/com.ditrix.edt.mcp.server.tests/src (JUnit4, a plug-in fragment).
E2E: tests/e2e/run_all.py + tools/test_<tool>.py (Python; runs the MCP server against TestConfiguration/).

Build

A Tycho build from mcp/ (Maven, JDK 17). The artifact is a p2 update-site in repositories/com.ditrix.edt.mcp.server.repository/target.

A local build is available — use it to validate Java edits (don't claim "verified by review/grep only"). The canonical script is source/compile.sh (it reproduces the CI flow mvn clean verify -T 1C from .github/workflows/build.yml):

# from the repo root: compile + unit tests
bash source/compile.sh
# compile only (no Surefire) — faster
bash source/compile.sh --skip-tests

The toolchain (JDK 17 + Maven 3.9+) is often not on PATH — pass it explicitly: --java-home <JDK17 home> --maven-home <maven home> (or env JAVA_HOME/MAVEN_HOME). The exact paths are machine-specific — discover them on the spot, don't hardcode into committed files. Exact options are in README "Building from source".
The first build is slow: Tycho pulls the EDT p2 repository (edt.1c.ru) + the Eclipse SDK (hundreds of MB). Once the caches are warm (~/.m2/repository/p2, .cache/tycho) it runs in ~1 minute. If the caches are absent and there's no network, the build legitimately can't run — say so, don't fake "green".
Unit tests need the target platform too (Mockito/JUnit come from the p2 target, not plain Maven Central) — a green compile.sh is the real proof for Java edits; grep only catches anchor/text problems.

Unit tests — conventions

One XxxToolTest per tool (tools/impl/), JUnit4.
Base pattern: tool.execute(params) + a sentinel-message check (e.g. "Project not found") for argument validation. Reference: WriteModuleSourceToolTest.
Bilingual invariant: for tools that resolve metadata/code, a case with a Russian identifier/synonym (reference WriteModuleSourceToolTest.testResolveRussianObjectName). See skill edt-mcp-bilingual.

Coverage gate

BuiltInToolTestCoverageTest (unit) fails the build if a registered tool has no XxxToolTest; the e2e coverage ratchet (tools/test_coverage_ratchet.py) fails the suite if a tools/list tool has no test_<tool>.py. Adding a tool without a test fails the build.

E2E

tests/e2e/run_all.py (+ tools/test_<tool>.py, one per tool) runs scenarios against the live server and TestConfiguration/ with git-fixture isolation. The round-trip of Cyrillic synonyms and the synonym-keyed-by-language-code check live in test_create_metadata.py / test_get_metadata_details.py. A new tool — add tools/test_<tool>.py. Full guide: edt-mcp-e2e-testing (and tests/e2e/SKILL.md).

Protocol conformance

A separate gate from the e2e business-logic suite: the official modelcontextprotocol/conformance suite validates the SERVER against the MCP wire spec (handshake, capabilities, session-id, isError, ping, SSE). Lives in tests/conformance/ (baseline.yml pins the intentional gaps; README.md explains the layer split). 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.

Before committing

Build passes
Unit tests green; a new/changed tool has a test
If metadata/code resolution is touched — a bilingual case exists
(if applicable) the e2e scenario is updated
For a finished piece of work, run the full edt-mcp-ready-to-deploy checklist (build → README → live redeploy → golden → full e2e → conformance → clean tree)

Mais deste repositório

mesmo repositório

edt-mcp-e2e-testing

DitriXNew/EDT-MCP

How to write and run black-box end-to-end (e2e) tests for the EDT-MCP server. Covers the architecture (shared harness + one file per tool + orchestrator), the git-fixture isolation protocol, happy-path AND negative coverage, error-quality assertions, and the anti-cheat rules. An agent that has never seen this project should be able to write a correct, non-cheating test after reading this.

2026-07-15221

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 → Russian issue comment + PR. Use when asked to take a whole task/issue to completion autonomously (not for a single quick edit or a pure question).

2026-07-03221

edt-mcp-testing

DitriXNew/EDT-MCP

How to manually e2e-test each EDT-MCP server tool against a live EDT workbench + TestConfiguration. One reference per tool under references/<family>/, each with the exact MCP call, the real expected result, and gotchas. Use when validating an MCP tool end-to-end by actually calling it (for build/unit tests see edt-mcp-build-test).

2026-06-23221

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. Use when starting work in this plugin, deciding where new code belongs, or before adding/refactoring an MCP tool.

2026-06-15221

edt-mcp-bilingual

DitriXNew/EDT-MCP

Correctness checklist for 1C's bilingual (Russian/English) model in EDT-MCP — synonym language-code vs name, object resolution by Name vs synonym vs TYPE token, dialect-aware vs literal code search. Use when reading, writing, resolving, formatting or searching metadata objects, synonyms, BSL identifiers or query keywords.

2026-06-08221

edt-mcp-e2e-testing

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

2026-06-08221

name	edt-mcp-build-test
description	How to build the EDT-MCP Eclipse plugin (Tycho/Maven) and run its unit and e2e tests, plus the test conventions for this repo. Use when building the plugin, running or writing tests, or verifying a change before committing.

EDT-MCP — build and tests

Layout

Maven/Tycho reactor: mcp/ (bom, bundles, features, repositories, targets, tests).
Unit tests: mcp/tests/com.ditrix.edt.mcp.server.tests/src (JUnit4, a plug-in fragment).
E2E: tests/e2e/run_all.py + tools/test_<tool>.py (Python; runs the MCP server against TestConfiguration/).

Build

A Tycho build from mcp/ (Maven, JDK 17). The artifact is a p2 update-site in repositories/com.ditrix.edt.mcp.server.repository/target.

# from the repo root: compile + unit tests
bash source/compile.sh
# compile only (no Surefire) — faster
bash source/compile.sh --skip-tests

The toolchain (JDK 17 + Maven 3.9+) is often not on PATH — pass it explicitly: --java-home <JDK17 home> --maven-home <maven home> (or env JAVA_HOME/MAVEN_HOME). The exact paths are machine-specific — discover them on the spot, don't hardcode into committed files. Exact options are in README "Building from source".
The first build is slow: Tycho pulls the EDT p2 repository (edt.1c.ru) + the Eclipse SDK (hundreds of MB). Once the caches are warm (~/.m2/repository/p2, .cache/tycho) it runs in ~1 minute. If the caches are absent and there's no network, the build legitimately can't run — say so, don't fake "green".
Unit tests need the target platform too (Mockito/JUnit come from the p2 target, not plain Maven Central) — a green compile.sh is the real proof for Java edits; grep only catches anchor/text problems.

Unit tests — conventions

One XxxToolTest per tool (tools/impl/), JUnit4.
Base pattern: tool.execute(params) + a sentinel-message check (e.g. "Project not found") for argument validation. Reference: WriteModuleSourceToolTest.
Bilingual invariant: for tools that resolve metadata/code, a case with a Russian identifier/synonym (reference WriteModuleSourceToolTest.testResolveRussianObjectName). See skill edt-mcp-bilingual.

Coverage gate

E2E

Protocol conformance

Before committing

Build passes
Unit tests green; a new/changed tool has a test
If metadata/code resolution is touched — a bilingual case exists
(if applicable) the e2e scenario is updated
For a finished piece of work, run the full edt-mcp-ready-to-deploy checklist (build → README → live redeploy → golden → full e2e → conformance → clean tree)