Testing GraphQL Endpoints in Spring Boot

Spring for GraphQL ships GraphQlTester, which makes testing feel natural — you write a query document, execute it, and assert on JSON paths with a fluent API rather than brittle string equality on entire response bodies.

Two-tier testing strategy:

• For fast feedback, use @GraphQlTest slice tests with @MockBean services; these load only the controller, schema, and exception resolvers — no database, no security; they run in milliseconds and catch the most common bugs: method names that don't match schema fields, argument mismatches, and missing @SchemaMapping wiring
• For full stack coverage, use @SpringBootTest with HttpGraphQlTester on a random port; this exercises JWT authentication, real repositories, DataLoader batching, and error mapping

Testing error scenarios — the critical gap:

• The .errors().satisfy() API lets you verify that BookNotFoundException produces a NOT_FOUND classification with the right extensions, not just that "an error happened"
• Use .mutate().header("Authorization", "Bearer " + jwt) to simulate authenticated requests and verify that anonymous calls produce a FORBIDDEN error classification
• Without error path tests, every exception looks like INTERNAL_ERROR in client-facing responses and your monitoring

Path-based assertions:

• Use .path("books[0].title") assertions rather than comparing entire JSON responses; path-based assertions survive adding backward-compatible fields without breaking tests
• Assert on the specific fields that represent the contract, not the full response structure

Transport-level tests:

• Keep a few raw WebTestClient tests for CORS headers, content type, and malformed request handling — these are invisible to GraphQlTester but have caused real production issues

I recommend one test per resolver mapping, one test per error classification, and one test per authorization boundary as the minimum coverage floor for every GraphQL controller.