test-data-management

The test-data-management skill provides a robust framework for handling, generating, and protecting data within automated software testing environments. It is designed for quality engineers and developers who need to bridge the gap between volatile production data and secure, reliable testing datasets. By automating the creation of synthetic records using faker libraries and enforcing strict database isolation via transactional rollbacks, the skill prevents data-related test flakiness and ensures compliance with global regulations such as GDPR and CCPA.

This skill is highly effective when teams struggle with production PII (Personally Identifiable Information) in non-production environments. It provides mechanisms for secure anonymization, masking, and hashing, ensuring that sensitive information is never exposed during test execution. Furthermore, it supports high-volume performance testing by enabling the batch generation of over 10,000 records per second, maintaining referential integrity across complex schemas.

• Automated generation of realistic synthetic datasets with configurable constraints and schemas.

• Secure anonymization, masking, and hashing techniques to handle PII and sensitive user information.

• Database transaction isolation strategies to ensure clean, predictable test states and auto-cleanup.

• High-speed data generation capabilities designed for volume-based performance testing.

• Native support for integration with QE agents like qe-test-data-architect and qe-security-scanner.

• Compliance-first workflows designed to meet strict GDPR, CCPA, and enterprise security standards.

• Always utilize synthetic or anonymized production snapshots; never use raw production PII.

• Align data complexity with the test type: use minimal data for unit tests, realistic sets for integration, and high-volume batches for performance testing.

• Leverage the qe-test-data-architect agent for complex, constraint-based data orchestration.

• Ensure schema-aware generation by maintaining a consistent memory namespace for generators, fixtures, and anonymization rules.

• Input requirements include schema definitions, volume counts, and privacy constraint flags; expected outputs include secure, compliant test datasets tailored to specific test scope.