Integration tests with test server in GraphQL - Time & Space Complexity

Time Complexity: Integration tests with test server

O(n * m)

Understanding Time Complexity

When running integration tests with a test server, we want to know how the time to complete tests changes as we add more test cases or data.

We ask: How does the test execution time grow when the test inputs get bigger?

Scenario Under Consideration

Analyze the time complexity of the following GraphQL integration test snippet.

query GetUsers {
  users {
    id
    name
    posts {
      id
      title
    }
  }
}
    

This query fetches all users and their posts from the test server during integration testing.

Identify Repeating Operations

Look for repeated actions in the query execution.

• Primary operation: Fetching each user and then fetching each post for that user.
• How many times: For each user (n users), the server fetches their posts (m posts per user).

How Execution Grows With Input

As the number of users and posts grows, the total work grows too.

Input Size (users n, posts m)	Approx. Operations
10 users, 5 posts each	10 + (10 * 5) = 60
100 users, 5 posts each	100 + (100 * 5) = 600
1000 users, 5 posts each	1000 + (1000 * 5) = 6000

Pattern observation: The operations grow roughly in proportion to the number of users times their posts.

Final Time Complexity

Time Complexity: O(n * m)

This means the time grows with the number of users multiplied by the number of posts per user.

Common Mistake

[X] Wrong: "The query time grows only with the number of users, not posts."

[OK] Correct: Each user's posts are also fetched, so posts add extra work that grows with their count.

Interview Connect

Understanding how test queries scale helps you write efficient tests and spot slow points in real systems.

Self-Check

What if the query only fetched users without their posts? How would the time complexity change?

Practice

1. What is the main purpose of using a test server in GraphQL integration tests?

easy

A. To speed up the production server

B. To run queries and mutations safely without affecting real data

C. To replace the database permanently

D. To generate random data automatically

Solution

1. Step 1: Understand the role of a test server

   A test server is a safe environment that mimics the real server but does not affect actual data.

2. Step 2: Identify the purpose in integration tests

   Integration tests use the test server to check if queries and mutations work together correctly without risk.

3. Final Answer:

   To run queries and mutations safely without affecting real data -> Option B

4. Quick Check:

   Test server = safe testing environment [OK]

Hint: Test server isolates tests from real data changes [OK]

Common Mistakes:

• Thinking test server speeds up production
• Confusing test server with permanent database replacement
• Assuming test server auto-generates data

2. Which of the following is the correct way to start a test server for GraphQL integration tests using Apollo Server?

easy

A. const server = ApolloServer(); server.startServer();

B. const server = ApolloServer(typeDefs, resolvers); server.run();

C. const server = new ApolloServer({ typeDefs, resolvers }); await server.listen();

D. const server = new ApolloServer({ typeDefs, resolvers }); await server.start();

Solution

1. Step 1: Recall Apollo Server setup

   Apollo Server requires creating an instance with typeDefs and resolvers, then calling start() before listen().

2. Step 2: Identify correct method to start server

   The correct method to start the server is await server.start(); before running listen().

3. Final Answer:

   const server = new ApolloServer({ typeDefs, resolvers }); await server.start(); -> Option D

4. Quick Check:

   Use server.start() before listen() [OK]

Hint: Remember to call await server.start() before listen() [OK]

Common Mistakes:

• Calling listen() without starting server
• Using incorrect constructor syntax
• Assuming server.run() or startServer() exist

3. Given this test code snippet for a GraphQL query on a test server:

const result = await server.executeOperation({ query: `query { user(id: 1) { name } }` }); console.log(result.data.user.name);

What will be printed if the user with id 1 has the name "Alice"?

medium

A. undefined

B. null

C. "Alice"

D. Error: user not found

Solution

1. Step 1: Understand executeOperation result

   executeOperation returns an object with data containing the query result if successful.

2. Step 2: Check the query and expected data

   The query requests user with id 1 and its name. If user exists with name "Alice", result.data.user.name will be "Alice".

3. Final Answer:

   "Alice" -> Option C

4. Quick Check:

   Query result matches user name "Alice" [OK]

Hint: executeOperation returns data object with query results [OK]

Common Mistakes:

• Expecting undefined if user exists
• Confusing null with undefined
• Assuming error thrown instead of null result

4. You wrote this test code but it throws an error:

const result = await server.executeOperation({ query: `mutation { addUser(name: "Bob") { id } }` });

What is the most likely cause?

medium

A. The mutation name is incorrect or not defined in schema

B. The query should be a GET request, not mutation

C. executeOperation cannot run mutations

D. Missing await keyword before server.executeOperation

Solution

1. Step 1: Check mutation usage in test

   executeOperation supports mutations, so that is not the issue.

2. Step 2: Verify mutation name and schema

   If mutation name addUser is not defined in the schema, the server throws an error.

3. Final Answer:

   The mutation name is incorrect or not defined in schema -> Option A

4. Quick Check:

   Mutation must exist in schema to run [OK]

Hint: Check mutation name matches schema exactly [OK]

Common Mistakes:

• Thinking executeOperation can't run mutations
• Forgetting to await executeOperation
• Confusing query and mutation types

5. You want to write an integration test that checks if a mutation correctly adds a user and then a query fetches that user. Which sequence correctly tests this on a GraphQL test server?

hard

A. Run mutation with executeOperation, then run query with executeOperation, check query result matches mutation data

B. Run query first, then mutation, then check mutation result

C. Run mutation and query in parallel without waiting, then check results

D. Only run mutation; query testing is unnecessary in integration tests

Solution

1. Step 1: Understand integration test flow

   Integration tests verify that mutations affect data and queries reflect those changes.

2. Step 2: Correct test sequence

   First run mutation to add user, then query to fetch user, then compare results to confirm correctness.

3. Final Answer:

   Run mutation with executeOperation, then run query with executeOperation, check query result matches mutation data -> Option A

4. Quick Check:

   Mutation then query to verify changes [OK]

Hint: Test mutation first, then query to confirm data change [OK]

Common Mistakes:

• Running query before mutation
• Running mutation and query in parallel without order
• Skipping query test after mutation