Managing Test Data Dependencies
You'll learn how to create reliable, isolated test data instead of depending on shared or unpredictable data sources.
Why Test Data Dependencies Matter
When your E2E tests rely on shared databases, production copies, or pre-existing data that other tests modify, they become unpredictable. A test might pass today but fail tomorrow simply because someone else changed the underlying data. It's like trying to cook in a kitchen where ingredients randomly disappear or get replaced—your recipe won't work consistently.
The Solution: Create Your Own Test Data
Instead of hoping the right data exists, create exactly what you need for each test:
Data Seeding
Before running tests, populate your test database with a known starting state. Reset it between test runs to ensure consistency.
Factories
Use factory functions or patterns to generate test objects on demand. Need a user account? Call your user factory to create one with specific attributes tailored to your test scenario.
API Calls
Use your application's own APIs to set up test data programmatically. If your app has a "create user" endpoint, call it during test setup. This ensures you're using the same code paths real users would, making your tests more realistic.
The Predictability Principle
The key is predictability: you control exactly what data exists, what state it's in, and when it's created or cleaned up. Each test becomes self-contained, creating its own universe of data rather than sharing a chaotic common world.
This approach directly supports isolating tests from each other (your previous lesson)—when each test creates and manages its own data, tests can't interfere with one another's expectations.
Key Takeaway: Always create your test data explicitly through seeding, factories, or API calls rather than depending on shared or external data sources, ensuring every test runs in a predictable, controlled environment.