test-data-strategy
/test-data-strategy
Define how tests get their data: synthetic generation, anonymised production extracts, fixtures per test, seeded reference data, data reset between runs, GDPR constraints on personal data, and ownership. Use when tests fail because of data, when someone wants to copy production into test, or when building a new test environment.
- Author
- RobinBeraud ↗
- Repository
- claude-qa-skills ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Define how tests get their data: synthetic generation, anonymised production extracts, fixtures per test, seeded reference data, data reset between runs, GDPR constraints on personal data, and ownership. Use when tests fail because of data, when someone wants to copy production into test, or when building a new test environment.
Original author description
Define how tests get their data: synthetic generation, anonymised production extracts, fixtures per test, seeded reference data, data reset between runs, GDPR constraints on personal data, and ownership. Use when tests fail because of data, when someone wants to copy production into test, or when building a new test environment.
How it works
- Principles
- Steps
- Output
SKILL.md preview
--- name: test-data-strategy description: "Define how tests get their data: synthetic generation, anonymised production extracts, fixtures per test, seeded reference data, data reset between runs, GDPR constraints on personal data, and ownership. Use when tests fail because of data, when someone wants to copy production into test, or when building a new test environment." --- # Test data strategy ## Principles - **Each automated test creates the data it needs** (via API or fixtures) and does not depend on data left by others. - **Reference data** (countries, VAT rates, charts of accounts) is seeded and versioned with the code. - **Production data** never lands in test environments raw: anonymise (irreversibly), minimise, and document the legal basis (GDPR). Prefer synthetic data. - **Volume data** for performance tests is generated, with realistic distributions. ## Steps 1. List data needs per test level and environment. 2. Choose the source per need: synthetic (`test-data-fr`), fixtures, anonymised extract, generated volume. 3. Define reset: transaction rollback, per-test tenant, database snapshot restore, nightly refresh. 4. Assign owners and write the anonymisation rules (which fields, which technique: masking, shuffling, fake values, keeping formats and checksums valid). 5. Check: no real names, e-mails, IBANs or national ids in test environments (scan regularly). ## Output Data matrix (need -> source -> reset -> owner), anonymisation rules, and the compliance checklist.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · RobinBeraud/claude-qa-skills | 90 | MIT |
| rpraharaj/forward-deployed-engineer | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7e1a03f7e195 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100test-data-generator
Creates test fixtures, mock data, and test scenarios for unit and integration tests. Use when setting up test data, creating mocks, or generating test fixtures. - 100test-data-management
Create and manage test data with factory patterns, fixture strategies, data anonymization, and synthetic data generation. Covers Fishery (TypeScript), FactoryBot (Ruby), Factory Boy (Python), database seeding, cleanup strategies, and GDPR-compliant data handling. Use when: "test… - 100writing-tests
Use when authoring, editing, or reviewing an automated test — any change to a test file or its fixtures. - 100test-data-management
When the user wants to design or audit how test data is generated, managed, masked, and reset between tests. Use when the user mentions "test data," "test data management," "TDM," "fixtures," "factories," "FactoryBot," "factory_bot," "Bogus," "faker," "synthetic data," "data… - 85wicked-garden-qe-test-data-manager
Fixtures, factories, anonymized production snapshots. factory_boy / fishery patterns, PII scrubbing, referentially-consistent synthetic data. Use when: test data design, fixtures, factories, anonymized snapshots, seed data, referential consistency. - 100decoy
Makes synthetic, fake, mock, seed or test data safe and reproducible. Every generated value that looks like personal data comes from a published reserved range (RFC 2606 email domains, NANP 555-0100 to 0199 phones, processor test card numbers, SSNs the SSA never issues, RFC 5737…