test-data-management

Design deterministic, isolated test data with factories, fixtures, and seed scripts.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill test-data-management-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-data-management
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/test-data-management
Command: npx skills add https://github.com/rabbicse/go-projects --skill test-data-management-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams create reliable test data that stays deterministic, isolated, realistic, and safe, avoiding flaky tests, shared mutable state, and accidental use of real PII.

Core Features & Use Cases

  • Factory Patterns: Build fresh users, orders, and related records with sensible defaults and per-test overrides.
  • Fixture Strategies: Use static, dynamic, or composed fixtures for API mocks, golden files, and per-test setup and teardown.
  • Data Anonymization and Seeding: Mask production data, generate synthetic edge cases, and write idempotent seed scripts that preserve referential integrity.
  • Use Case: A QA team can seed a test database, run parallel browser tests, and clean everything up afterward without leaking sensitive customer data.

Quick Start

Ask for a test data strategy for your repository and specify the app language, test framework, and whether you need factories, fixtures, seeding, or anonymization.

Frequently Asked Questions about test-data-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create deterministic test data for integration and end-to-end test suites?

Deterministic test data is created using factory patterns and static fixtures with seeded random generation to ensure reproducible results across integration and end-to-end tests.

What's the best way to anonymize production data for GDPR-safe software testing?

To anonymize production data for GDPR-safe testing, apply data masking techniques to generate synthetic records and edge cases while preserving referential integrity.

How do I write idempotent seed scripts for a test database?

Idempotent seed scripts are written using upserts to safely populate a test database, ensuring referential integrity is preserved and preventing flaky tests from shared mutable state.

Why are my tests flaky when using shared mutable test fixtures?

Tests become flaky due to shared mutable state, which isolated test fixtures and per-test cleanup resolve by building fresh records with sensible defaults and executing per-test setup and teardown.

Can I run parallel browser tests using factory patterns without data collisions?

Yes, isolated test data strategies using factory patterns prevent collisions in parallel browser tests by applying per-test overrides and per-test cleanup to maintain referential integrity.