Menu
Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | tidb-integrationtest-recorder |
| description | Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct. |
Use this workflow for changes under tests/integrationtest/t/** or when SQL behavior needs integration coverage.
Do not use -record for this suite.
Canonical command details live in docs/agents/testing-flow.md -> Integration tests (/tests/integrationtest).
docs/agents/testing-flow.md -> Integration tests (/tests/integrationtest) for the recording command.TestName from the path under tests/integrationtest/t/ without the .test suffix (example: planner/core/binary_plan).tests/integrationtest/r/** and keep result diffs minimal.Use when implementing a user- or reviewer-prescribed code change (including review comments with suggested fixes or options), especially when the requested edit may be risky, incomplete, ambiguous, or misaligned with TiDB correctness and compatibility constraints.
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.
Use when running TiDB package tests and deciding whether failpoint enable/disable is required before and after the test command.
Use when running tests under tests/realtikvtest that require a local TiUP playground lifecycle with strict startup, readiness checks, and cleanup.