GraphQL APIs with Spring Boot · Pelajaran

Pengujian Unit Penyelesai GraphQL

Tulis pengujian unit yang efektif untuk penyelesai GraphQL dan logika pengambilan data di Spring Boot.

Pelajaran 1 dari 411 langkah

Pengujian Unit Penyelesai GraphQL adalah pelajaran GraphQL APIs with Spring Boot gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar GraphQL APIs with Spring Boot, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus GraphQL APIs with Spring Boot mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

Why Unit Test Resolvers?

Unit testing is crucial for ensuring the reliability of your GraphQL API. When we unit test resolvers, we focus on testing individual components in isolation.

Isolation: We test a resolver without needing a running server or database.
Correctness: Verify the resolver's logic, argument handling, and data transformation.
Speed: Unit tests run very fast, providing quick feedback during development.

This lesson will guide you through writing effective unit tests for your Spring Boot GraphQL resolvers.

Spring Boot Resolver Overview

Before testing, let's briefly recall how resolvers are structured in Spring Boot. They are typically Spring @Controller components with methods annotated for GraphQL operations like @QueryMapping or @MutationMapping.

These methods often depend on other Spring @Service components to fetch or manipulate data, which is where mocking comes in handy for testing.

Setting Up Test Environment

For unit testing in Spring Boot, you'll primarily use JUnit 5 and Mockito. These are typically included by default with spring-boot-starter-test.

JUnit 5: The testing framework to write and run your tests.
Mockito: A mocking framework to create mock objects for dependencies, allowing you to isolate the resolver under test.

Ensure your pom.xml or build.gradle includes the spring-boot-starter-test dependency.

Isolating Resolvers with Mocks

Resolvers often interact with services, repositories, or other components. To unit test a resolver, we need to isolate it from these dependencies.

Mockito helps us create 'mock' objects that mimic the behavior of real dependencies. This allows us to control what the dependencies return and verify how they are called, without actually invoking their real logic.

@Mock: Creates a mock instance of a class or interface.
@InjectMocks: Injects the created mocks into the object being tested.
@ExtendWith(MockitoExtension.class): Integrates Mockito with JUnit 5.

Testing a Simple Resolver

Let's start with a basic resolver that doesn't have any external dependencies. We can instantiate it directly and call its method.

This example shows a simple resolver and its corresponding unit test using JUnit 5 assertions.

package com.example.app;

import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertEquals;

// Imagine MyResolver.java exists with a greeting() method
// @Controller
// public class MyResolver {
//   @QueryMapping
//   public String greeting() {
//     return "Hello GraphQL!";
//   }
// }

class MyResolverTest {
  @Test
  void greetingReturnsCorrectMessage() {
    // 1. Arrange: Create an instance of the resolver
    MyResolver resolver = new MyResolver();

    // 2. Act: Call the method under test
    String result = resolver.greeting();

    // 3. Assert: Verify the output
    assertEquals("Hello GraphQL!", result);
  }
}

Testing with Mocked Services

Most resolvers depend on services to perform business logic. Here's how to test a resolver that uses a GreetingService.

We use @Mock for the service and @InjectMocks for the resolver. Then, when().thenReturn() tells the mock what to return when its method is called.

package com.example.app;

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.mockito.Mockito.when;

// Imagine GreetingResolver.java and GreetingService.java exist
// (see previous scenes for context)

@ExtendWith(MockitoExtension.class)
class GreetingResolverTest {
  @Mock
  private GreetingService greetingService;

  @InjectMocks
  private GreetingResolver greetingResolver;

  @Test
  void personalizedGreetingReturnsExpected() {
    // Arrange: Define mock behavior
    when(greetingService.generateGreeting("Alice"))
      .thenReturn("Hello, Alice!");

    // Act: Call resolver method
    String result = greetingResolver.personalizedGreeting("Alice");

    // Assert: Verify resolver's output
    assertEquals("Hello, Alice!", result);
  }
}

Verifying Input Arguments

It's important to ensure that your resolver correctly passes arguments to its underlying services. Mockito's verify() method helps with this.

Mockito.verify(mockObject).method(expectedArgs) confirms that the specified method was called with the exact arguments during the test execution.

package com.example.app;

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;
import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.when;

@ExtendWith(MockitoExtension.class)
class GreetingResolverVerifyTest {
  @Mock
  private GreetingService greetingService;

  @InjectMocks
  private GreetingResolver greetingResolver;

  @Test
  void serviceCalledWithCorrectArgument() {
    // Arrange
    when(greetingService.generateGreeting("Bob"))
      .thenReturn("Hi Bob!");

    // Act
    greetingResolver.personalizedGreeting("Bob");

    // Assert: Verify service method was called with "Bob"
    verify(greetingService).generateGreeting("Bob");
  }
}

Testing for Expected Return Values

After a resolver processes data, it should return the correct output. JUnit's assertions are used to confirm these return values.

assertEquals(expected, actual): Checks if two values are equal.
assertNotNull(object): Checks if an object is not null.
assertTrue(condition): Checks if a condition is true.

Always assert the final state or return value of the resolver method.

package com.example.app;

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;
import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.mockito.Mockito.when;

@ExtendWith(MockitoExtension.class)
class GreetingResolverAssertTest {
  @Mock
  private GreetingService greetingService;

  @InjectMocks
  private GreetingResolver greetingResolver;

  @Test
  void personalizedGreetingReturnsExpectedValue() {
    String name = "Charlie";
    String expectedGreeting = "Hello, Charlie!";

    // Arrange
    when(greetingService.generateGreeting(name))
      .thenReturn(expectedGreeting);

    // Act
    String actualGreeting = 
      greetingResolver.personalizedGreeting(name);

    // Assert
    assertEquals(expectedGreeting, actualGreeting);
  }
}

Testing Error Scenarios

Robust resolvers should handle errors gracefully. Unit tests can verify that your resolvers throw expected exceptions or handle them appropriately.

Use JUnit's assertThrows to confirm that a specific exception type is thrown when certain conditions are met, such as a service failing.

package com.example.app;

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.extension.ExtendWith;
import org.mockito.InjectMocks;
import org.mockito.Mock;
import org.mockito.junit.jupiter.MockitoExtension;
import static org.junit.jupiter.api.Assertions.assertThrows;
import static org.mockito.Mockito.when;

@ExtendWith(MockitoExtension.class)
class ErrorHandlingResolverTest {
  @Mock
  private GreetingService greetingService;

  @InjectMocks
  private GreetingResolver greetingResolver;

  @Test
  void personalizedGreetingThrowsExceptionOnError() {
    String name = "ErrorUser";

    // Arrange: Mock service to throw an exception
    when(greetingService.generateGreeting(name))
      .thenThrow(new RuntimeException("Service failed"));

    // Act & Assert: Verify that the resolver throws
    assertThrows(RuntimeException.class, () -> {
      greetingResolver.personalizedGreeting(name);
    });
  }
}

Quick Check: Unit Test Concepts

When unit testing a Spring Boot GraphQL resolver that depends on a UserService, what is the primary purpose of using Mockito's @Mock annotation on the UserService instance within your test class?

Jawab di pelajaran interaktif

Recap & What's Next

Congratulations! You've learned the fundamentals of unit testing your GraphQL resolvers in Spring Boot.

We understood the importance of isolation for unit tests.
We used Mockito to mock service dependencies.
We wrote tests to verify resolver logic, argument passing, and return values.
We also covered testing error scenarios.

By applying these techniques, you can ensure your GraphQL resolvers are robust and behave as expected. Next, you might explore integration testing to verify your entire GraphQL API end-to-end.

Gratis untuk memulai

Belajar GraphQL APIs with Spring Boot dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus: 12
Pelajaran: 48

Mulai belajar gratis Lihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Pengujian Unit Penyelesai GraphQL” gratis?

Ya — teks lengkap “Pengujian Unit Penyelesai GraphQL” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus GraphQL APIs with Spring Boot, upgrade ke CoddyKit PRO. Kursus GraphQL APIs with Spring Boot mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Pengujian Unit Penyelesai GraphQL”?

Tulis pengujian unit yang efektif untuk penyelesai GraphQL dan logika pengambilan data di Spring Boot. Kamu berlatih GraphQL APIs with Spring Boot dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai GraphQL APIs with Spring Boot?

Tidak diperlukan pengalaman sebelumnya. GraphQL APIs with Spring Boot di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Pengujian Unit Penyelesai GraphQL” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran GraphQL APIs with Spring Boot ini?

Ya. Setiap pelajaran GraphQL APIs with Spring Boot menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

Pengujian Unit Penyelesai GraphQL
Pengujian Integrasi API GraphQL
Menerapkan Spring Boot GraphQL
Integrasi Berkelanjutan untuk API GraphQL

← Kembali ke GraphQL APIs with Spring Boot