Engineering
test-data-management avatar

test-data-management

Strategic test data generation, management, and privacy compliance for scalable, secure, and realistic quality engineering workflows.

Introduction

The test-data-management skill provides a specialized framework for handling data lifecycles within quality engineering environments. Designed for engineers and QA teams, it enables the secure generation, anonymization, and isolation of datasets required for comprehensive testing. By leveraging the qe-test-data-architect agent, users can automate the creation of synthetic datasets that maintain referential integrity while strictly adhering to data privacy standards such as GDPR and CCPA. This skill is critical for teams performing integration, performance, or edge-case testing where production data access is restricted or insufficient.

  • Automated synthetic data generation using faker-based libraries for various schemas and constraints.

  • Production data anonymization, including advanced masking, hashing, and PII field redaction.

  • High-speed batch data generation capable of producing over 10k records per second for performance testing scenarios.

  • Built-in database transaction management for automated test isolation, ensuring clean test environments via rollback mechanisms.

  • Compliance-first architecture that prevents the leakage of production PII into non-production environments.

  • Support for complex relationship mapping and referential integrity maintenance across generated datasets.

  • Utilize the qe-test-data-architect for generating volume data (10k+) for performance load testing.

  • Employ transaction isolation strategies in your tests to avoid cluttering test databases with leftover state.

  • Always replace sensitive user information (email, phone, SSN) with generated synthetic values when working with production snapshots.

  • Integrate with other QE skills like performance-testing or security-testing for a holistic QA pipeline.

  • Input requirements include schema definitions, desired record counts, and constraints; outputs are clean, ready-to-use fixtures for your test suite.

  • Adhere to the core rule: Never store or use production PII directly in automated testing loops.

Repository Stats

Stars
329
Forks
65
Open Issues
4
Language
TypeScript
Default Branch
main
Sync Status
Idle
Last Synced
Apr 29, 2026, 05:35 AM
View on GitHub