Resolver unit tests in GraphQL - Time & Space Complexity

Time Complexity: Resolver unit tests

O(n)

Understanding Time Complexity

When testing GraphQL resolvers, it's important to know how the time to run tests grows as the number of resolvers or test cases increases.

We want to understand how the testing effort scales with more resolvers or more data.

Scenario Under Consideration

Analyze the time complexity of the following resolver unit test code snippet.

query GetUsers {
  users {
    id
    name
  }
}

# Resolver test calls the users resolver and checks the result
# This test runs once per resolver function

This code tests a single resolver by calling it and verifying the output.

Identify Repeating Operations

Look for repeated actions in the testing process.

• Primary operation: Calling each resolver function once per test case.
• How many times: Once for each resolver tested, and once per test case for that resolver.

How Execution Grows With Input

As the number of resolvers or test cases grows, the total test time grows proportionally.

Input Size (number of resolvers)	Approx. Operations (test calls)
10	10 test calls
100	100 test calls
1000	1000 test calls

Pattern observation: The total test calls increase directly with the number of resolvers tested.

Final Time Complexity

Time Complexity: O(n)

This means the testing time grows in a straight line as you add more resolvers or test cases.

Common Mistake

[X] Wrong: "Adding more resolvers won't affect test time much because tests run fast."

[OK] Correct: Even if each test is quick, many tests add up, so total time grows with the number of resolvers.

Interview Connect

Understanding how test time grows helps you plan and write efficient tests, a skill valued in real projects and interviews.

Self-Check

"What if we batch multiple resolver tests together in one call? How would the time complexity change?"

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