eclipse-test
Run JUnit tests in Eclipse projects — all tests, by package, by class, or individual test methods. Also build Maven projects.
pinned to #170d9bcupdated last week
Ask your AI client: “install skills/eclipse-test”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/eclipse-testmetahub onboarded this repo on the author's behalf.
If you own github.com/gradusnikov/eclipse-chatgpt-plugin on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
158
Last commit
last week
Latest release
published
- #eclipse
- #eclipse-plugin
- #mcp
- #mcp-client
- #mcp-server
- #plugin
About this skill
Pulled from SKILL.md at publish time.
Execute JUnit tests and Maven builds using Eclipse's built-in infrastructure.
Allowed tools
- mcp__eclipse-ide__runAllTests
- mcp__eclipse-ide__runPackageTests
- mcp__eclipse-ide__runClassTests
- mcp__eclipse-ide__runTestMethod
- mcp__eclipse-ide__findTestClasses
- mcp__eclipse-ide__runMavenBuild
- mcp__eclipse-ide__getConsoleOutput
- mcp__eclipse-ide__getEffectivePom
- mcp__eclipse-ide__listMavenProjects
- mcp__eclipse-ide__getProjectDependencies
- mcp__eclipse-ide__getCompilationErrors
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.170d9bc· last week
Kind-specific
31Skill: SKILL.md present
found at .claude/skills/eclipse-test/SKILL.md · frontmatter source: SKILL.md
Skill: body content present
236 words · 1,810 chars · 4 sections
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
11 declared: mcp__eclipse-ide__runAllTests, mcp__eclipse-ide__runPackageTests, mcp__eclipse-ide__runClassTests, mcp__eclipse-ide__runTestMethod, mcp__eclipse-ide__findTestClasses (+6)
Release history
1- releasecurrent170d9bcwarnlast week
Contents
Run Tests & Build in Eclipse
Execute JUnit tests and Maven builds using Eclipse's built-in infrastructure.
Test Tools
- runAllTests — Run all tests in a project. Provide
projectNameand optionaltimeout(default: 60s). - runPackageTests — Run tests in a specific package. Provide
projectNameandpackageName. - runClassTests — Run all tests in a specific test class. Provide
projectNameandclassName(fully qualified). - runTestMethod — Run a single test method. Provide
projectName,className, andmethodName. - findTestClasses — Find all test classes in a project.
Build Tools
- runMavenBuild — Run Maven with specified goals. Provide
projectName,goals(e.g.,clean install), optionalprofiles, andtimeout. - getEffectivePom — Get the effective POM for a Maven project.
- listMavenProjects — List all Maven projects in the workspace.
- getProjectDependencies — Get Maven dependencies for a project.
Typical Workflow
-
Find test classes:
findTestClasses(projectName="myapp") -
Run specific test after code change:
runClassTests(projectName="myapp", className="com.example.MyServiceTest", timeout="60") -
Run all tests before committing:
runAllTests(projectName="myapp", timeout="120") -
Build with Maven:
runMavenBuild(projectName="myapp", goals="clean verify", timeout="300") -
Check build output:
getConsoleOutput()
Notes
- Tests run using JUnit 5 by default
- Test results include pass/fail status, execution time, and failure traces
- Use
getCompilationErrorsfirst to ensure code compiles before running tests - Maven build output goes to the Eclipse console — use
getConsoleOutputto retrieve it
Reviews
No reviews yet. Be the first.
Related
Gpt Researcher
An autonomous agent that conducts deep research on any data using any LLM providers
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
mh install skills/eclipse-test