# Tidb Integrationtest Recorder

> Use when recording TiDB integration tests under tests/integrationtest and verifying regenerated result files stay minimal and correct.

- Skill: `pingcap/tidb-integrationtest-recorder` (Agent Skill)
- Install (CLI): `npx skillmds@latest add pingcap/tidb-integrationtest-recorder`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pingcap/tidb-integrationtest-recorder/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: pingcap (https://skillmd.com/u/pingcap)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pingcap/tidb-integrationtest-recorder

---


# TiDB Integration Test Recorder

## Overview

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)`.

## Workflow

1. Use `docs/agents/testing-flow.md` -> `Integration tests (/tests/integrationtest)` for the recording command.
2. Derive `TestName` from the path under `tests/integrationtest/t/` without the `.test` suffix (example: `planner/core/binary_plan`).
3. Review changed files in `tests/integrationtest/r/**` and keep result diffs minimal.

## Guardrails

- Prefer targeted recording of the affected suite only.
- Avoid unrelated result churn.
- If result files need manual edits, keep them minimal and verify with another run.