Resolver unit tests in GraphQL

Introduction

Resolver unit tests check if small parts of your GraphQL server work correctly. They help find mistakes early and keep your code reliable.

When you add a new resolver to fetch or change data.

When you fix a bug in a resolver and want to make sure it stays fixed.

When you want to make sure your resolver returns the right data for different inputs.

When you update your data source and want to check if resolvers still work.

When you want to prevent future changes from breaking your resolver logic.

Syntax

GraphQL

describe('resolverName', () => {
  it('should do something expected', () => {
    // Arrange: set up data or mocks
    // Act: call the resolver function
    // Assert: check the result matches expected
  });
});

describe groups related tests.

it defines a single test case.

Examples

This test checks if the getUser resolver returns the correct user name when given ID '1'.

GraphQL

describe('getUser', () => {
  it('returns user data for valid ID', () => {
    const result = getUser(null, { id: '1' }, context);
    expect(result.name).toBe('Alice');
  });
});

This test verifies that createPost returns the post with the right title after creation.

GraphQL

describe('createPost', () => {
  it('creates a post and returns it', () => {
    const input = { title: 'Hello', content: 'World' };
    const result = createPost(null, { input }, context);
    expect(result.title).toBe('Hello');
  });
});

Sample Program

This example shows two tests for the getUser resolver: one for a valid user ID and one for an invalid ID.

GraphQL

const { describe, it, expect } = require('@jest/globals');

// Sample resolver function
function getUser(parent, args, context) {
  const users = { '1': { id: '1', name: 'Alice' }, '2': { id: '2', name: 'Bob' } };
  return users[args.id] || null;
}

describe('getUser resolver', () => {
  it('returns user data for valid ID', () => {
    const result = getUser(null, { id: '1' }, null);
    expect(result).toEqual({ id: '1', name: 'Alice' });
  });

  it('returns null for invalid ID', () => {
    const result = getUser(null, { id: '3' }, null);
    expect(result).toBeNull();
  });
});

Important Notes

Use mocks to simulate data sources when testing resolvers.

Keep tests small and focused on one behavior.

Run tests often to catch errors early.

Summary

Resolver unit tests check small parts of your GraphQL server.

They help make sure your resolvers return correct data.

Write simple tests using describe and it blocks.

Practice

1. What is the main purpose of a resolver unit test in GraphQL?

easy

A. To verify the database connection settings

B. To test the entire GraphQL schema at once

C. To check if a resolver returns the correct data

D. To style the GraphQL playground interface

Solution

1. Step 1: Understand resolver role

   Resolvers are functions that fetch and return data for GraphQL queries.

2. Step 2: Purpose of unit tests

   Unit tests check small parts of code, here specifically if resolvers return correct data.

3. Final Answer:

   To check if a resolver returns the correct data -> Option C

4. Quick Check:

   Resolver unit tests = check resolver output [OK]

Hint: Resolvers return data; tests check if data is correct [OK]

Common Mistakes:

• Confusing unit tests with integration tests
• Thinking tests check UI or styling
• Assuming tests check database setup

2. Which syntax correctly defines a simple resolver unit test using Jest?

easy

A. describe('Test', () => { it('checks resolver', () => { expect(resolver()).toBe(data); }); });

B. test('Test', () => { describe('checks resolver', () => { expect(resolver()).toBe(data); }); });

C. it('Test', () => { expect(resolver()).toBe(data); }); describe('checks resolver', () => {});

D. expect('Test', () => { it('checks resolver', () => { resolver(); }); });

Solution

1. Step 1: Identify Jest test structure

   Jest uses describe to group tests and it or test for individual tests.

2. Step 2: Check correct nesting and syntax

   describe('Test', () => { it('checks resolver', () => { expect(resolver()).toBe(data); }); }); correctly nests it inside describe and uses expect properly.

3. Final Answer:

   describe('Test', () => { it('checks resolver', () => { expect(resolver()).toBe(data); }); }); -> Option A

4. Quick Check:

   describe + it + expect = correct test syntax [OK]

Hint: Use describe for groups, it for tests, expect for checks [OK]

Common Mistakes:

• Swapping describe and it blocks
• Missing expect or incorrect nesting
• Using expect without a matcher

3. Given this resolver and test code, what will the test output be?

const resolver = () => ({ id: 1, name: 'Alice' });

describe('User resolver', () => {
  it('returns correct user', () => {
    expect(resolver()).toEqual({ id: 1, name: 'Alice' });
  });
});

medium

A. Test throws runtime error

B. Test fails due to wrong object

C. Syntax error in test code

D. Test passes successfully

Solution

1. Step 1: Analyze resolver output

   The resolver returns an object { id: 1, name: 'Alice' } exactly.

2. Step 2: Check test expectation

   The test expects the same object using toEqual, which compares object values deeply.

3. Final Answer:

   Test passes successfully -> Option D

4. Quick Check:

   Exact object match = test passes [OK]

Hint: toEqual checks deep equality; objects must match exactly [OK]

Common Mistakes:

• Confusing toBe with toEqual for objects
• Expecting test to fail with correct data
• Misreading object properties

4. Identify the error in this resolver unit test code:

describe('Test resolver', () => {
  it('returns data', () => {
    expect(resolver).toBe(data);
  });
});

medium

A. No error; code is correct

B. Missing parentheses to call resolver function

C. Wrong matcher; should use toEqual instead of toBe

D. Incorrect use of describe block

Solution

1. Step 1: Check resolver usage

   The test uses resolver without parentheses, so it tests the function itself, not its return value.

2. Step 2: Correct function call

   To test the returned data, the resolver must be called as resolver().

3. Final Answer:

   Missing parentheses to call resolver function -> Option B

4. Quick Check:

   Call resolver() to get data, not resolver [OK]

Hint: Call functions with () to test their output [OK]

Common Mistakes:

• Forgetting to call the resolver function
• Confusing toBe and toEqual for objects
• Misplacing describe and it blocks

5. You want to test a resolver that fetches a user by ID from a mock database. Which approach best ensures your unit test is isolated and reliable?

hard

A. Mock the database call inside the resolver test to return fixed data

B. Connect to the real database and fetch actual user data

C. Skip testing the resolver and test only the database separately

D. Write tests that depend on network availability

Solution

1. Step 1: Understand unit test isolation

   Unit tests should test one part only, without relying on external systems like databases.

2. Step 2: Use mocking for database calls

   Mocking replaces real database calls with fixed data, making tests fast and reliable.

3. Final Answer:

   Mock the database call inside the resolver test to return fixed data -> Option A

4. Quick Check:

   Mock external calls for isolated unit tests [OK]

Hint: Mock external dependencies to isolate resolver tests [OK]

Common Mistakes:

• Using real database in unit tests
• Skipping resolver tests entirely
• Writing flaky tests depending on network