fix-pulsar-flaky-tests

Identify flaky Pulsar tests via Develocity API and create fix PRs.

8|2|Updated Feb 2, 2021

Search Tags:#pull-request #git-blame #flaky-tests #test-fix #pulsar #develocity

Ready to run

npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill fix-pulsar-flaky-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix-pulsar-flaky-tests
Source: https://github.com/lhotari/pulsar-contributor-toolbox/tree/main/claude-code/skills/fix-pulsar-flaky-tests
Command: npx skills add https://github.com/lhotari/pulsar-contributor-toolbox --skill fix-pulsar-flaky-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end workflow to identify, analyze, and fix flaky Pulsar tests, enabling reliable test results by systematically discovering failures via Develocity, performing root-cause analysis with git blame and production code review, implementing robust, minimal fixes, and validating with repeated invocation before PR creation.

Core Features & Use Cases

Discover flaky tests using Develocity and group related failures for combined PRs.
Analyze failures by inspecting test code, tracing history with git blame, and reviewing production changes.
Apply robust, minimal fixes that preserve original test intent, verify with invocationCount, and create PRs following Pulsar templates.

Quick Start

Run the end-to-end workflow to identify flaky Pulsar tests, apply root-cause fixes, and open a PR.

Frequently Asked Questions about fix-pulsar-flaky-tests

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

FAQPage Schema

How do I find and fix flaky tests in Apache Pulsar?▼

To fix flaky Pulsar tests, this workflow discovers failures via the Develocity API and groups related failures. It then analyzes test and production code using git blame to find root causes and applies minimal fixes.

What is the best way to diagnose the root cause of a flaky Pulsar test?▼

Diagnosing a flaky Pulsar test involves reading the test code, tracing its history with git blame, and reviewing production code changes. This reveals the exact code modifications that introduced the test instability.

How do I verify that a flaky test fix is robust before opening a pull request?▼

You verify a flaky test fix by running the test repeatedly with invocationCount. Once the test passes consistently, you create a pull request following the standard Pulsar template to submit the fix.

Can I group multiple related flaky test failures into a single pull request?▼

Yes, you can group related flaky test failures into combined pull requests. The workflow identifies related failures discovered through the Develocity API and batches them together for a unified fix.

Does this workflow require access to the Develocity API to identify flaky tests?▼

Access to the Develocity API is required to identify flaky Pulsar tests. The workflow queries this API to systematically discover failing tests and gather the data needed for root cause analysis.

Why should I use git blame when analyzing flaky test failures?▼

Git blame helps analyze flaky test failures by tracing the history of test and production code. It identifies when and why specific changes were introduced, revealing the underlying cause of the test instability.