skills.rest
studenkov
studenkovCOMMUNITY
Explore all skills by this author →
GitHub

run-tests

Run Gradle project tests by type or module via IDE or console and report results.

Updated May 4, 2026
Search Tags:#testing#integration tests#java#gradle#ide#junit#test runner
One-click install
npx skills add https://github.com/studenkov/FinanceTracker --skill run-tests-studenkov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-tests
Source: https://github.com/studenkov/FinanceTracker/tree/main/.agents/skills/run-tests
Command: npx skills add https://github.com/studenkov/FinanceTracker --skill run-tests-studenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running a Gradle project's tests often means digging through build files to find the right task, launching long noisy builds, and wading through console output to find failures. This Skill maps test types (unit, integration, all) and modules to the correct Gradle tasks or IDE Run Configurations, executes them, and returns a compact pass/fail report. ## Core Features & Use Cases - Dual execution paths: Runs tests inside the IDE via Run Configurations when the IDE is reachable, or falls back to console Gradle commands when it is not. - Type and module mapping: Maps unit, integration, and all test types to actual Gradle tasks (e.g. test, testIntgr) and subproject modules, asking the user when multiple candidates exist and remembering the mapping for future runs. - Context-safe reporting: Executes the run in a Haiku subagent that parses JUnit XML results and returns only a concise report with verbatim failure messages and stacktraces, keeping long build logs out of the main context. - Use Case: Ask "run the integration tests for the vet module" and the Skill resolves the right task or Run Configuration, executes it, and reports which tests failed with their actual error messages. ## Quick Start Ask the assistant to run the unit tests for this project and report whether they passed.

Frequently Asked Questions about run-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run only the integration tests in a Gradle project?▼

The Skill maps the integration test type to the project's actual Gradle task, such as testIntgr or integrationTest, by inspecting task descriptions. If multiple tasks fit, it asks which one to use, then runs it and reports the results.

How do I run tests for a single Gradle module or subproject?▼

Prefix the module path onto the task, for example :web:test or :vet:testIntgr. The Skill combines a module with a test type on the fly and remembers that mapping for future runs in the same project.

Can I run Gradle tests inside the IDE instead of the console?▼

Yes. When the IDE is reachable via the steroid MCP tools, the Skill reuses or creates an IDE Run Configuration and launches it in its own Run tab. If the IDE is not reachable, it falls back to running Gradle directly in the console.

Why do my Gradle tests show as up-to-date and not actually run?▼

Gradle skips tasks it considers up-to-date, so the IDE tab shows no test events. The Skill adds --rerun-tasks by default so tests actually execute, at the cost of losing the incremental build cache for that run.

How do I run only tests matching a specific package or class?▼

Narrow the run with a test filter glob, which maps to Gradle's --tests option, for example ru.openide.petclinic.vet.*. The Skill passes this filter to the Gradle task or IDE configuration before launching.

Why does the test report ignore red console warnings?▼

Console noise such as Mockito self-attach warnings or invalid Java installation notes appears in red but does not affect results. The report judges pass or fail only by actual test failures parsed from the JUnit XML output.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

sdet

Generate Kotlin test code from structured test plans for Gradle builds.

Community
Advanced
v1-iov1-io
6

fix-tests

Diagnose failing test outputs and apply minimal fixes across the codebase.

Official
Advanced
agentmattersagentmatters
3

laravel-verification

Run environment checks, linting, static analysis, tests, and security scans for Laravel projects.

Official
Advanced
jvm-skillsjvm-skills
135

test-gradle

Run Gradle tests headlessly and return only failing test output.

Official
Intermediate