Resolver unit tests in GraphQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a resolver in GraphQL?

A resolver is a function that fetches the data for a specific field in a GraphQL query. It tells the server how to get the data requested by the client.

beginner

Why do we write unit tests for resolvers?

Unit tests for resolvers check that each resolver returns the correct data and handles errors properly. This helps catch bugs early and ensures the API works as expected.

intermediate

What is a common tool used to mock data sources in resolver unit tests?

A common tool is Jest with mocking functions. It lets you simulate database calls or API responses so you can test resolvers without real data sources.

intermediate

How do you test error handling in a resolver?

You simulate an error in the data source or input and check if the resolver returns the correct error message or throws an error as expected.

advanced

What is the difference between unit testing a resolver and integration testing a GraphQL API?

Unit testing a resolver focuses on one resolver function in isolation, often mocking data sources. Integration testing checks how multiple parts work together, including the full GraphQL query execution.

What does a resolver function do in GraphQL?

A Validates client queries

B Defines the GraphQL schema

C Runs the GraphQL server

D Fetches data for a specific field

Resolvers fetch the data for each field requested in a GraphQL query.

Which tool is commonly used to mock data in resolver unit tests?

A Jest

B React

C Express

D MongoDB

Jest is a popular testing framework that supports mocking functions for unit tests.

What should you test in a resolver unit test?

A Network latency

B User interface layout

C Correct data return and error handling

D Database schema design

Unit tests check if the resolver returns correct data and handles errors properly.

How do you isolate a resolver for unit testing?

A Mock external data sources

B Run the full server

C Use real database connections

D Test the entire API

Mocking data sources isolates the resolver so you test only its logic.

What is the main difference between unit and integration tests for GraphQL?

A Unit tests check UI; integration tests check backend

B Unit tests check one resolver; integration tests check multiple parts working together

C Unit tests run slower than integration tests

D Unit tests require a database; integration tests do not

Unit tests focus on single resolvers; integration tests cover the full query execution flow.

Explain how you would write a unit test for a GraphQL resolver that fetches user data.

Think about isolating the resolver and simulating data.

Describe the benefits of unit testing resolvers in a GraphQL API.

Consider how testing helps in development and maintenance.

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