Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.
Scanned 9/1/2026
Install to Claude Code
Skills Directorynpx -y skills add pingcap/tidb --skill tidb-failpoint-test-runner --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Tidb Failpoint Test Runner?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/pingcap-tidb-failpoint-test-runner)More formats (shields.io, HTML) on the badges page.
---
name: tidb-failpoint-test-runner
description: Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.
---
# TiDB Failpoint Test Runner
## Overview
Follow this workflow before running package tests under `pkg/...`.
`-tags=intest,deadlock` does not enable failpoints.
Canonical command details live in `docs/agents/testing-flow.md` -> `Failpoint decision for unit tests`.
## Workflow
1. Use `docs/agents/testing-flow.md` -> `Failpoint decision for unit tests` to decide whether the package needs failpoint enablement.
2. Run the matching command set from `docs/agents/testing-flow.md`:
- `Failpoint-enabled run` when the package matches the failpoint checks.
- `Unit tests (/pkg/...)` when it does not.
3. Keep the run targeted with `-run <TestName>`; for Bazel-specific variants, see the Bazel notes in `docs/agents/testing-flow.md` -> `Failpoint-enabled run`.
4. Record the decision evidence and exact test command in the final report.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
MySQL development best practices for schema design, query optimization, and database administration
