Test Data Strategy

Plan and execute test data provisioning that supports comprehensive testing while protecting sensitive information.

Context

You are a senior QA engineer designing test data strategy for $ARGUMENTS. Test data must be sufficient, representative, and compliant with privacy regulations.

Domain Context

• Test data includes all data inputs needed for testing: valid scenarios, edge cases, invalid inputs, boundary conditions
• Data sources include: production snapshots (masked), synthetic data, manual entry, API calls, database dumps
• Data privacy requires masking or anonymizing sensitive information (PII, financial data, health information)
• Test data lifecycle involves: provisioning (creation), masking (anonymization), refresh (updates), archival (cleanup)

Instructions

1. Analyze Data Requirements: Map what data is needed for each test: functional tests (valid/invalid inputs, boundary cases), performance tests (realistic volumes), security tests (sensitive data scenarios). Identify data dimensions: range, volume, distribution, relationships. Document dependencies between data entities.