run-test

Automates single Pinot JUnit/TestNG test execution via Maven module detection.

6.1k|1.5k|Updated May 19, 2014
One-click install
npx skills add https://github.com/apache/pinot --skill run-test-apache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-test
Source: https://github.com/apache/pinot/tree/main/.claude/skills/run-test
Command: npx skills add https://github.com/apache/pinot --skill run-test-apache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running a single Pinot test by name across the multi-module repo usually requires manually identifying the owning Maven module and building the correct mvnw command with the right test filters. This Skill automates that workflow, returning a focused test execution with minimal user effort.

Core Features & Use Cases

  • Auto-detects the owning Maven module for a given test class and runs only that test.
  • Constructs the precise Maven invocation (including -pl, -am, -Dtest, and -Dsurefire.failIfNoSpecifiedTests=false) to guarantee upstream modules are built correctly.
  • Supports integration tests by recognizing typical integration-test naming patterns and taking the appropriate flags, with warnings about potentially long runtimes.

Quick Start

Run the command '/run-test RangeIndexTest' to execute a specific Pinot test by name.

Frequently Asked Questions about run-test

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

FAQPage Schema
How do I run a single JUnit or TestNG test by name in a multi-module Maven project?

To run a single JUnit or TestNG test by name, you can use this Skill to auto-detect the owning Maven module and construct the precise ./mvnw command with the correct -Dtest filters, executing only that specific test class.

What's the best way to execute a specific Pinot integration test without running the entire suite?

The best way to execute a specific Pinot integration test is to use this Skill, which recognizes integration-test naming patterns and applies the appropriate Maven flags, while warning about potentially long runtimes.

Why does my focused Maven test execution fail when running a test in an upstream module?

Focused Maven test execution can fail if upstream modules are not built correctly; this Skill prevents this by ensuring the -Dsurefire.failIfNoSpecifiedTests=false flag is included in the composed command.

Do I need the Maven wrapper to run focused tests across Pinot modules?

Yes, you need the Maven wrapper to use this automation, as it requires the ./mvnw command to build the invocation and run the specified test class across the Pinot repository.

How does auto-detection work for finding the owning module of a test class?

Auto-detection works by scanning the repo's module structure to identify which Maven module owns the given test class name, then composing a command with -pl and -am to build only the necessary dependencies.

Can I use this to run tests if I don't know the module structure of the repository?

Yes, you can run tests without knowing the module structure, because this Skill automates the identification of the owning Maven module and constructs the correct execution command based solely on the test class name.