Test Data and Fixtures Strategy
Create realistic, safe, repeatable test data.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Design realistic, safe, and repeatable test data for my project. System and database: [SYSTEM_AND_DATABASE]. Types of tests that need data: [TEST_TYPES]. Sensitive data in production: [SENSITIVE_DATA]. Tools: [TOOLS]. Create the strategy as a checklist, with decisions and code where useful: [ ] Never copy raw production personal data into test environments; choose generated, masked, or subsetted data and say why [ ] Define data sets: minimal (unit tests), standard (integration), large (performance), and edge-case (unicode names, long strings, boundary dates, zero and negative amounts, empty lists, time zone boundaries) [ ] Use factories or builders that create only what a test needs, with sensible defaults and overrides [ ] Seed data deterministic with a fixed random seed and documented [ ] Each test creates and cleans its own data, or runs in a transaction rolled back after, to avoid test interference [ ] Fixed or fake clocks for time-dependent tests [ ] Fake external services with contract tests to keep fakes honest [ ] Referential integrity preserved in masked data [ ] Data reset command for local, CI, and shared environments [ ] Data refresh schedule and ownership [ ] Documentation of the main personas and scenarios in the data Deliver example factories and a seed script for my entities, a masking approach with a table of fields to mask and how, and a review of test data risks.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.