GraphQL API'lerini Bütünleştirme Sınaması
Sorguları, değişiklikleri ve abonelikleri uçtan uca doğrulayarak GraphQL API'nizin tamamı için bütünleştirme sınamaları gerçekleştirin.
GraphQL API'lerini Bütünleştirme Sınaması, CoddyKit'te ücretsiz bir GraphQL APIs with Spring Boot dersidir. Bu, 4 dersinin 2. dersidir. Aşağıdan dersin tamamını ücretsiz okuyabilir, sonra tarayıcıda yerleşik kod editörü ve 7/24 yapay zeka koçu ile uygulamalı olarak pratik yapabilirsin. Bu, GraphQL APIs with Spring Boot öğrenme yolunun bir parçasıdır ve ilerlemeniz web ve CoddyKit uygulaması arasında senkronize olur. GraphQL APIs with Spring Boot kursu toplamda 4 dersten oluşur.
Bu dersin bazı bölümleri henüz çevrilmemiş olup İngilizce olarak gösterilmektedir.
Why Integration Test GraphQL?
Welcome to integration testing for GraphQL APIs! While unit tests check small parts of your code, integration tests verify that different components work together correctly.
- End-to-End Flow: They simulate real client requests.
- Component Interaction: Ensure your GraphQL schema, resolvers, and data sources all connect properly.
- Confidence: Gives you assurance that your API behaves as expected before deployment.
This lesson focuses on using Spring Boot's testing utilities.
Essential Spring Boot Test Tools
Spring Boot provides powerful tools to make integration testing straightforward:
@SpringBootTest: This annotation loads your full application context, making all your beans available for testing.WebTestClient: A non-blocking client for testing web endpoints. It simulates HTTP requests to your GraphQL API.
Together, these allow you to send actual GraphQL queries/mutations and inspect the responses.
Setting Up Your Test Class
To start, you'll create a test class. Annotate it with @SpringBootTest to load your application context. Then, inject WebTestClient to interact with your GraphQL endpoint.
We typically use @AutoConfigureWebTestClient to configure WebTestClient for testing, often with a specific port or context path.
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class GraphQLIntegrationTest {
@Autowired
private WebTestClient webTestClient;
// Your test methods will go here
}Crafting a Simple Query Test
Let's write a test for a basic GraphQL query. We'll define the query string and then use WebTestClient to send it to the /graphql endpoint.
The query will be sent as a JSON payload in the request body, typically containing a query field and optionally variables.
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class SampleQueryTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testHelloQuery() {
String graphQlQuery = "{ hello }";
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlQuery))
.exchange()
.expectStatus().isOk()
.expectBody()
.jsonPath("$.data.hello").isEqualTo("Hello, GraphQL!");
}
}Runnable: Query & Assert Result
Here's a full runnable example. We have a simple Spring Boot app with a hello GraphQL query, and an integration test verifying its output.
Notice how jsonPath is used to navigate the GraphQL response structure (data.hello) and assert the value.
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.graphql.data.method.annotation.QueryMapping;
import org.springframework.stereotype.Controller;
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
// --- Application Code ---
@SpringBootApplication
public class GraphQLApp {
public static void main(String[] args) {
SpringApplication.run(GraphQLApp.class, args);
}
}
@Controller
class HelloResolver {
@QueryMapping
public String hello() {
return "Hello, GraphQL!";
}
}
// --- Test Code ---
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class HelloQueryIntegrationTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testHelloQuery() {
String graphQlQuery = "{ hello }";
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlQuery))
.exchange()
.expectStatus().isOk()
.expectBody()
.jsonPath("$.data.hello").isEqualTo("Hello, GraphQL!");
}
}Testing Queries with Variables
Many GraphQL queries take arguments. You can pass these as variables in your request payload. The variables field in the JSON request body should be a map of variable names to their values.
Remember to define the variables in your GraphQL query string (e.g., query MyQuery($name: String!)).
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class QueryWithVarsTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testGreetQueryWithName() {
String graphQlQuery = "query Greet($name: String!) { greet(name: $name) }";
Map<String, Object> variables = Map.of("name", "Coddy");
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlQuery, "variables", variables))
.exchange()
.expectStatus().isOk()
.expectBody()
.jsonPath("$.data.greet").isEqualTo("Hello, Coddy!");
}
}Integration Testing a Mutation
Mutations are used for creating, updating, or deleting data. Testing them follows a similar pattern to queries but you'll use the mutation keyword in your GraphQL string.
It's good practice to assert the return value of the mutation and, if applicable, verify the state change (e.g., by performing a subsequent query).
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class MutationIntegrationTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testCreateItemMutation() {
String graphQlMutation = "mutation CreateItem($name: String!) { createItem(name: $name) { id name } }";
Map<String, Object> variables = Map.of("name", "New Widget");
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlMutation, "variables", variables))
.exchange()
.expectStatus().isOk()
.expectBody()
.jsonPath("$.data.createItem.name").isEqualTo("New Widget");
}
}Handling GraphQL Errors in Tests
When your GraphQL API encounters an error (e.g., validation failure, unauthorized access), it typically returns an errors array in the response body, alongside a potential data field (if some parts succeeded).
You can use jsonPath to check for the presence and content of these error messages in your tests.
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class ErrorHandlingTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testInvalidInputError() {
String graphQlMutation = "mutation CreateItem($name: String!) { createItem(name: $name) { id } }";
Map<String, Object> variables = Map.of("name", ""); // Assume empty name is invalid
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlMutation, "variables", variables))
.exchange()
.expectStatus().isOk() // GraphQL errors usually return 200 OK
.expectBody()
.jsonPath("$.errors").isArray()
.jsonPath("$.errors[0].message").isNotEmpty()
.jsonPath("$.errors[0].message").isEqualTo("Item name cannot be empty.");
}
}Testing Protected Endpoints
If your GraphQL API uses Spring Security, you'll want to test how it responds to authenticated and unauthenticated requests. WebTestClient allows you to easily add headers, including authorization tokens.
This ensures your security configuration correctly protects your GraphQL fields and operations.
import org.junit.jupiter.api.Test;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.boot.test.autoconfigure.web.reactive.AutoConfigureWebTestClient;
import org.springframework.boot.test.context.SpringBootTest;
import org.springframework.test.web.reactive.server.WebTestClient;
import java.util.Map;
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
@AutoConfigureWebTestClient
class ProtectedEndpointTest {
@Autowired
private WebTestClient webTestClient;
@Test
void testProtectedQuery_unauthorized() {
String graphQlQuery = "{ protectedData }";
webTestClient.post().uri("/graphql")
.bodyValue(Map.of("query", graphQlQuery))
.exchange()
.expectStatus().isOk() // GraphQL often returns 200 with errors for auth issues
.expectBody()
.jsonPath("$.errors").isArray()
.jsonPath("$.errors[0].message").isEqualTo("Unauthorized access");
}
@Test
void testProtectedQuery_authorized() {
String graphQlQuery = "{ protectedData }";
String validToken = "mock-jwt-token"; // In a real app, generate a valid test token
webTestClient.post().uri("/graphql")
.header("Authorization", "Bearer " + validToken)
.bodyValue(Map.of("query", graphQlQuery))
.exchange()
.expectStatus().isOk()
.expectBody()
.jsonPath("$.data.protectedData").isEqualTo("Secret Info");
}
}Quick Check: Integration Tests
Consider the following GraphQL query and a Spring Boot application that exposes a product(id: ID!) query. Which WebTestClient assertion correctly verifies that a product with ID '123' and name 'Laptop' is returned?
Recap: GraphQL Integration Testing
In this lesson, you learned how to perform integration tests for your GraphQL APIs using Spring Boot.
- We covered setting up your test environment with
@SpringBootTestandWebTestClient. - You saw how to craft and execute GraphQL queries and mutations, including passing variables.
- We explored asserting the expected data in the response using
jsonPath. - Finally, you learned to handle error responses and test protected endpoints.
Integration tests are vital for ensuring the robustness and correctness of your GraphQL API!
Yapay zeka eğitmeniyle GraphQL APIs with Spring Boot öğren — ücretsiz
Tarayıcında gerçek kod yaz ve çalıştır, 7/24 yapay zeka eğitmeninden anında yardım al; web'de ya da uygulamada kaldığın yerden devam et.
- Kurslar
- 12
- Dersler
- 48
Sıkça Sorulan Sorular
“GraphQL API'lerini Bütünleştirme Sınaması” dersi ücretsiz mi?
Evet — “GraphQL API'lerini Bütünleştirme Sınaması” dersin tüm metni burada web'de ücretsiz olarak okunabilir. Etkileşimli olarak pratik yapmak (yerleşik kod editörü ve 7/24 yapay zeka koçu) ve GraphQL APIs with Spring Boot kursunun geri kalanını açmak için CoddyKit PRO'ya yükselt. GraphQL APIs with Spring Boot kursu toplamda 4 dersten oluşur.
“GraphQL API'lerini Bütünleştirme Sınaması” dersinde ne öğreneceğim?
Sorguları, değişiklikleri ve abonelikleri uçtan uca doğrulayarak GraphQL API'nizin tamamı için bütünleştirme sınamaları gerçekleştirin. GraphQL APIs with Spring Boot ile uygulamalı kodu tarayıcıda doğrudan çalıştırarak pratik yaparsın ve 7/24 yapay zeka koçu dersi çalışırken sorularını yanıtlar.
GraphQL APIs with Spring Boot öğrenmeye başlamak için deneyim gerekli mi?
Önceden deneyim gerekmez. CoddyKit'te GraphQL APIs with Spring Boot, başlangıçtan ileri seviyeye kadar yapılandırıldığı için buradan başlayabilir veya başından başlayıp kendi hızında ilerleme yapabilirsin. Bu, 4 dersinin 2. dersidir.
“GraphQL API'lerini Bütünleştirme Sınaması” dersi ne kadar sürer?
Çoğu CoddyKit dersi yaklaşık 5–10 dakika sürer. Her biri kısa ve etkileşimli olduğu için sabit ilerleme yaparsın ve web ile uygulama arasında tam olarak bıraktığın yerden devam edebilirsin.
Bu GraphQL APIs with Spring Boot dersinde kod yazıp çalıştırabilir miyim?
Evet. Her GraphQL APIs with Spring Boot dersi yerleşik bir kod editörü içerir, bu sayede tarayıcıda gerçek kod yazıp çalıştırabilir ve anlık yapay zeka geri bildirimi alırsın — yerel kurulum gerekli değildir.
Bu kursun tüm dersleri
- GraphQL Çözücülerini Birim Olarak Sınama
- GraphQL API'lerini Bütünleştirme Sınaması
- Spring Boot GraphQL'i Dağıtma
- GraphQL API'leri için Sürekli Entegrasyon