Why Mocking resolvers in GraphQL? - Purpose & Use Cases

The Big Idea

What if you could build and test your app without waiting for the database to be ready?

The Scenario

Imagine you are building a new app that talks to a database, but the database isn't ready yet. You need to test your app's features, but without real data, it feels like trying to drive a car with no engine.

The Problem

Manually creating fake data for every test is slow and boring. It's easy to make mistakes or forget to update the fake data when your app changes. This leads to broken tests and wasted time.

The Solution

Mocking resolvers lets you quickly create pretend responses for your app's data requests. This means you can test your app's logic and UI without waiting for the real database, saving time and avoiding frustration.

Before vs After

✗ Before

const fakeUser = { id: '1', name: 'Alice' };
function getUser() { return fakeUser; }

✓ After

const mocks = { Query: { user: () => ({ id: '1', name: 'Alice' }) } };

What It Enables

It enables fast, reliable testing and development even before your real data is ready.

Real Life Example

A developer building a social media app can mock user profiles and posts to test the feed display without needing the backend database to be finished.

Key Takeaways

Manual fake data is slow and error-prone.

Mocking resolvers creates easy, reusable fake responses.

This speeds up development and testing before real data exists.