mcpField
R
run-tests

run-tests

github.com/amplicodeTesting & quality134253 installsUpdated 8w ago
Repository

About run-tests

run-tests is a skill for running unit, integration, or full test suites in Gradle projects. It runs tests inside the IDE when the repository is available there, otherwise uses the console, and collects results in a Haiku subagent report.

Key features

  1. 01Runs unit, integration, or all tests
  2. 02Targets Gradle subprojects
  3. 03Runs tests in IDE when available
  4. 04Falls back to console Gradle
  5. 05Collects results in a Haiku report

Use cases

  1. 01Run unit tests for a module
  2. 02Run integration tests with project setup
  3. 03Run all tests when IDE is unavailable

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/amplicode/spring-skills --skill run-tests

After installing, type/run-testsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
gradle.md
ide.md
report.md
scripts/
run_tests_in_ide.kts

Details

From the project README

Run tests

Test types and modules

Test types (extend as a project needs):

TypeMeaningTypical Gradle tasks
unitfast tests, no Spring/Dockertest
integrationSpring + TestcontainerstestIntgr or integrationTest
alleverythingtest + testIntgr

A module is a Gradle subproject; prefix its path onto the task (:web:test). A module combines with a type on the fly — build that configuration when first asked and remember it.

Pick the path

Probe FIRST, here, before loading either reference — so you read only the one you need. Call steroid_list_projects (via ToolSearch if the tool schema isn't loaded):

  • It returns the repo you're in → IDE path: note that entry's project_name and follow references/ide.md (runs tests inside the IDE, each in its own Run tab). Its steps start already knowing the project_name — don't re-probe.
  • It fails, or the repo isn't listed → console Gradle path: follow references/gradle.md (runs Gradle in the console) and tell the user you used the console fallback because the IDE wasn't reachable.

Both paths end by collecting the result in a Haiku subagent that returns the references/report.md report and nothing else — keeping the long test/build output out of the main context. Act on that report in the main model.

Comments

Markdown supported