// Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.
| 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. |
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.
docs/agents/testing-flow.md -> Failpoint decision for unit tests to decide whether the package needs failpoint enablement.docs/agents/testing-flow.md:
Failpoint-enabled run when the package matches the failpoint checks.Unit tests (/pkg/...) when it does not.-run <TestName>; for Bazel-specific variants, see the Bazel notes in docs/agents/testing-flow.md -> Failpoint-enabled run.Use when deciding whether make bazel_prepare is required before build or test commands based on local file changes in TiDB.
Use when creating or editing TiDB GitHub issues so issue templates, labels, issue titles, and issue descriptions stay consistent with repository workflow. Trigger on tasks involving issue creation, bug reports, enhancement tracking issues, label selection, or searching for existing issues and PRs before filing a new one.
Use when creating or editing TiDB pull requests so PR title scope, PR template fields, hidden HTML comments, and bot-parsed checklist sections stay intact. Trigger on tasks involving PR creation, PR body updates, issue linking from a PR, test checklist updates, or investigating labels like do-not-merge/needs-tests-checked.
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.
Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.
Use when running tests under tests/realtikvtest that require a local TiUP playground lifecycle with strict startup, readiness checks, and cleanup.