test-gradle

Run Gradle tests headlessly and return only failing test output.

135|25|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jvm-skills/jvm-skills --skill test-gradle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-gradle
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/test-gradle
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill test-gradle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs Gradle tests headlessly and returns only failing test output.

Core Features & Use Cases

  • Headless Gradle test execution for fast feedback
  • Return-only-failures reporting to streamline triage
  • Works with multi-module Gradle projects and common DSLs (Kotlin/Groovy)

Quick Start

Invoke the /test-gradle command to run all tests and return only the failing results.

Frequently Asked Questions about test-gradle

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

FAQPage Schema
How do I run Gradle tests headlessly and only show failures?

You can run Gradle tests headlessly and filter for failures by invoking a wrapper script that forwards test patterns to Gradle and writes results to build/gradle-test-out.txt, emitting a concise failure report.

Can I use this headless test runner with multi-module Kotlin DSL Gradle projects?

Yes, this headless test runner works with multi-module Gradle projects and supports common DSLs including Kotlin and Groovy for executing tests across your modules.

Does this Gradle test execution approach work for CI pipelines and local development workflows?

Yes, this Gradle test execution approach is applicable to both CI pipelines and local development workflows, providing fast feedback through headless execution and concise failure reporting.

What is the best way to streamline triage for failing Gradle tests in a multi-module setup?

The best way to streamline triage is to run Gradle tests headlessly and return only the failing test output, which helps you quickly identify issues across multi-module setups without scrolling through successful test logs.

Why does my Gradle test output include successful tests when I only need to see failures?

Standard Gradle test output includes all tests by default. This Skill solves that by running tests headlessly and returning only the failing test output, filtering out successful results to reduce noise.