review-testing

Verify test coverage and quality for Pinot diffs and integration-test readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach for code reviewers to verify test coverage and quality in Pinot diffs, ensuring regression coverage, appropriate use of mocks, and integration-test readiness across versions.

Core Features & Use Cases

  • Guides systematic evaluation of changes to src/test/**, covering positive and negative cases, real dictionaries vs mocks, and mixed-version testing patterns.
  • Recommends integration-test base classes (prefer CustomDataQueryClusterIntegrationTest) and flags for standalone cluster tests when required.
  • Defines a severity framework (CRITICAL, MAJOR, MINOR) and concrete test-signature recommendations to reproduce regressions.

Quick Start

Review the PR’s test changes and apply this guide to assess coverage, mocks usage, and integration-test readiness

Frequently Asked Questions about review-testing

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

FAQPage Schema
How do I review test coverage for Pinot diffs and ensure regression tests are sufficient?

To review test coverage for Pinot diffs, systematically evaluate changes in src/test/**, verify positive and negative cases, and ensure regression tests exist for modified code paths. This structured approach confirms alignment with documented review principles and flags missing tests.

What is the recommended base class for Pinot integration tests?

The recommended base class for Pinot integration tests is CustomDataQueryClusterIntegrationTest. Reviewers should flag standalone cluster tests when they are required, ensuring integration-test readiness and proper mixed-version testing patterns across the codebase.

When should I use real dictionaries instead of mocks in Pinot tests?

Use real dictionaries instead of mocks when evaluating src/test/** changes to ensure accurate test coverage. Reviewers must verify appropriate mock usage and flag inappropriate test patterns that might hide regressions in null-handling logic or type-dispatch changes.

How do I classify test severity issues during a code review?

Classify test severity issues during code review using a framework of CRITICAL, MAJOR, and MINOR levels. This structure helps prioritize missing tests, inappropriate test patterns, and inadequate regression coverage found in Pinot diffs.

Does this code review guide apply to new wire-format and type-dispatch changes?

Yes, this code review guide applies to PRs modifying new wire-format or integration-test scenarios, type-dispatch changes, and code paths with null-handling logic. It ensures concrete test-signature recommendations reproduce regressions effectively.