What problem does it solve?
Recording expected outputs for TiDB integration tests under tests/integrationtest is error-prone: using the wrong flags or recording too broadly produces noisy result diffs in tests/integrationtest/r that obscure real behavior changes. This Skill provides the correct recording workflow and guardrails for that suite.
Core Features & Use Cases
- Correct Recording Workflow: Points to the canonical recording command in docs/agents/testing-flow.md and explicitly forbids using the -record flag for this suite.
- Test Name Derivation: Shows how to derive the TestName from a path under tests/integrationtest/t/ by stripping the .test suffix (e.g., planner/core/binary_plan).
- Minimal Diff Guardrails: Instructs targeted recording of only the affected suite and review of changed files under tests/integrationtest/r to avoid unrelated result churn.
- Use Case: After modifying SQL planner behavior, a developer records only the affected integration test suite, then verifies the regenerated result files contain minimal, correct diffs before committing.
Quick Start
Ask the assistant to record the TiDB integration test for the suite you changed, for example by saying: record the integration test for planner/core/binary_plan and keep the result diff minimal.
