run-tests

Yes, you can filter Gradle test execution by module, class, or test name. This allows you to target specific JVM-based unit tests and run only the relevant subsets, speeding up your feedback loop during development.

Yes, when running integration tests in a multi-module Gradle project, you must start a local backend first. This Skill automates test execution and provides diagnostic options for failures, but requires the backend to be running for integration test validation.

To debug failing JVM tests in a multi-module Gradle setup, this Skill provides diagnostic options and clear failure reports. It executes your targeted test classes across modules and isolates the failures so you can quickly identify and resolve code changes.

Executing tests across modules requires Gradle and properly configured test tasks within your project. The Skill automates running and debugging JVM-based unit and integration tests, but relies entirely on your existing Gradle configuration to function correctly.