Schema testing in GraphQL - Step-by-Step Execution

Concept Flow - Schema testing

Define Schema

↓

Write Test Queries/Mutations

↓

Run Tests Against Schema

↓

Check Responses Match Expected

↓

Pass or Fail Test

↓

Fix Schema or Tests if Fail

↩Back to Write Test Queries

Schema testing means writing queries or mutations to check if the GraphQL schema works as expected, then running these tests and fixing issues if tests fail.

Execution Sample

GraphQL

query GetUser {
  user(id: "1") {
    id
    name
  }
}

This query asks the schema for a user with id 1 and requests the id and name fields.

Execution Table

Step	Action	Query Part	Schema Check	Result
1	Parse Query	query GetUser	Valid syntax	Pass
2	Validate Field 'user'	user(id: "1")	Field exists with argument id	Pass
3	Validate Subfields	id, name	Fields exist on User type	Pass
4	Execute Resolver	user with id=1	Returns user object	{"id":"1","name":"Alice"}
5	Compare Response	Response vs Expected	Matches expected data	Pass

💡 All schema checks passed and response matched expected data

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
query	undefined	Parsed query object	Validated fields	Executed resolver	Response data
response	undefined	undefined	undefined	{"id":"1","name":"Alice"}	{"id":"1","name":"Alice"}

Key Moments - 2 Insights

Why do we check if fields exist on the User type?

Because if a field does not exist on the type, the schema is invalid for that query. See execution_table row 3 where subfields are validated.

What happens if the resolver returns wrong data?

The test will fail at the response comparison step (row 5), indicating the schema or resolver logic needs fixing.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of validating the 'user' field?

A Pass

B Fail

C Skipped

D Error

💡 Hint

Check execution_table row 2 under Result column

At which step is the resolver executed?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at execution_table Step column and Action 'Execute Resolver'

If the response data did not match expected, which step would show failure?

A Step 3

B Step 4

C Step 5

D Step 1

💡 Hint

See execution_table row 5 comparing response vs expected

Concept Snapshot

Schema testing in GraphQL:
- Write queries/mutations to test schema
- Validate query syntax and fields
- Execute resolvers to get data
- Compare response with expected
- Fix schema or tests if failures occur

Full Transcript

Schema testing in GraphQL involves writing queries or mutations that ask for data defined in the schema. The process starts by parsing the query to check syntax. Then, each field and argument is validated against the schema to ensure they exist and are correct. After validation, the resolver functions run to fetch or compute the data. The returned response is compared to the expected result to confirm correctness. If any step fails, the schema or test queries are fixed and tested again. This cycle ensures the schema works as intended and helps catch errors early.