Test Data Management
Creating and managing test data via fixtures, builders, factories, and minimal realistic datasets.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill test-data-managementgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/testing/skills/test-data-management ~/.claude/skills/test-data-managementPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Test Data Management Strategies for creating and maintaining test data. ## Context You are designing test data infrastructure. Good test data is realistic but lightweight. ## Domain Context - **Fixtures**: Pre-built test data sets; inflexible but fast - **Builders**: Fluent API to construct objects; flexible, readable - **Factories**: Methods that generate test data; reusable, minimal - **Realistic**: Use production-like data; but omit sensitive info - **Minimal**: Only data relevant to the test; avoid clutter ## Instructions 1. **Choose Strategy**: Fixtures (pre-built), Builders (flexible), Factories (reusable) 2. **Use Builders for Complex Objects**: Clear intent; easy to vary specific fields 3. **Create Factories for Common Patterns**: User factory, Order factory 4. **Avoid Shared State**: Each test gets fresh data; no pollution 5. **Seed Data Carefully**: Use realistic but non-sensitive data 6. **Document Defaults**: Default builder state should be valid for most tests 7. **Performance**: Consider test database resets vs. transactions for cleanup ## Anti-Patterns - Massive fixture files with hundreds of records; hard to understand which data matters - Global shared test data; tests interfere with each other - Over-realistic test data (full names, addresses); wastes resources - Complex object construction in tests; use builders instead - Test data stored in files separate from tests; couples tests to external state ## Further Reading
Details
- Skill name
test-data-management- Repository
- sethdford/claude-skills
- Path
engineer/testing/skills/test-data-management/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Test Data Management skill do?
Creating and managing test data via fixtures, builders, factories, and minimal realistic datasets.
How do I install the Test Data Management skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Test Data Management popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Test Data Strategy
48sethdford/claude-skills
Design test data management approaches. Use when planning data provisioning for testing.
Test Coverage Analysis
48sethdford/claude-skills
Measure and analyze test coverage gaps. Use when identifying untested code paths and assessing coverage sufficiency.
Test Doubles Strategy
48sethdford/claude-skills
Choosing between mocks, stubs, fakes, spies, and dummies based on testing needs.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.