Mock Data

What is Mock Data?

Mock Data is simplified fake data used primarily for unit testing, component testing, and rapid development. Unlike synthetic data which aims for statistical accuracy and production-likeness, mock data prioritizes simplicity, readability, and test clarity. Mock data is often hardcoded in test files, kept minimal to reduce test complexity, and designed to make test intentions obvious. Examples include placeholder names like "Test User", predictable IDs like 1, 2, 3, and simple values like "[email protected]".

Mock data characteristics include: Simplicity (easy to understand and maintain), Minimalism (only essential fields populated), Predictability (deterministic values aid debugging), Readability (obvious test data like "ACTIVE_STATUS"), Speed (no complex generation logic), and Self-Documenting (mock values clarify test intent). Mock data trades realism for test clarity - when debugging a unit test, "Test User 1" is more helpful than a realistic "Jennifer Martinez".

Mock data is appropriate for: Unit Tests (testing individual functions in isolation), Component Tests (testing UI components with minimal data), Development (rapid prototyping without database dependencies), API Mocking (simulating external service responses), and Documentation (examples in API documentation). Mock data is NOT appropriate for integration testing, performance testing, or security testing where production-like realism matters.

Mock data vs Synthetic Data trade-offs: Mock data is faster to create and easier to maintain, but doesn't catch production issues. Synthetic data is slower to generate but catches more bugs. Best practices use mock data for fast unit tests and synthetic data for comprehensive integration tests. Modern testing pyramids use lots of mock data at the unit test level, and production-like synthetic data at integration and E2E test levels.