Writing tests in my app is slow because every test has to hand-build its own data. I want a fixture system that makes realistic test data trivial to create. First, look at my database schema or models and list the core entities (users, posts, orders, subscriptions, whatever my app has). Then build a fixtures module that: 1. Provides a factory function for each entity that returns a valid, realistic record with sensible defaults. 2. Lets a test override any field (for example, create a user with an expired trial, or an order in a refunded state). 3. Handles relationships between entities, so I can ask for "a user with two orders" and get consistent data. 4. Generates unique values where uniqueness matters (emails, usernames, slugs) so parallel or repeated test runs don't collide. Avoid random data for anything the tests assert against. Randomness in fixtures causes flaky tests. Use deterministic defaults with explicit overrides. Refactor one or two of my existing tests to use the fixtures so I can see the pattern, then show me how to create data for a new test from scratch. Don't touch production code. Fixtures are test infrastructure only, and they must never run against a production database. Add a guard or a clear naming convention if my test and production configs could plausibly get crossed.