Micro Frontends Architecture with Module Federation · レッスン

Federatedコンポーネントの単体テスト

Micro Frontend内の個々のコンポーネントに対する効果的な単体テストの書き方を学びます。

「Federatedコンポーネントの単体テスト」はCoddyKit上の無料Micro Frontends Architecture with Module Federationレッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはMicro Frontends Architecture with Module Federation学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Micro Frontends Architecture with Module Federationコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Unit Testing MFE Components

Welcome! In this lesson, we'll dive into unit testing for individual components within your Micro Frontends.

Unit testing focuses on testing the smallest, isolated parts of your code, like a single button or an input field. For Micro Frontends, this ensures each component works perfectly on its own before integration.

Why Unit Test MFEs?

Unit testing is crucial for Micro Frontends due to their independent nature:

Isolation: Test components without relying on other Micro Frontends.
Faster Feedback: Catch bugs early, specific to a component.
Independent Deployment: Confidently deploy a component knowing its core logic is sound.
Clear Contracts: Ensure components behave as expected when exposed or consumed.

Key Testing Tools

For JavaScript-based Micro Frontends, especially those using React, two tools are very popular:

Jest: A powerful JavaScript testing framework. It acts as a test runner, assertion library, and mocking utility. Think of it as 'how' you run your tests.
React Testing Library (RTL): A set of utilities to test React components in a way that resembles how users interact with your app. It focuses on 'what' the user sees and interacts with, not internal implementation details.

Our Simple Component

Let's create a very basic React component that we'll unit test. This component could be part of any Micro Frontend and exposed via Module Federation later.

It's just a simple button that displays text and can trigger an action.

import React from 'react';

const MyButton = ({ label, onClick }) => {
  return (
    <button onClick={onClick}>
      {label}
    </button>
  );
};

export default MyButton;

Setting Up Your Test File

Unit tests are typically placed in files ending with .test.js or .spec.js alongside the component or in a __tests__ folder.

We'll use Jest and React Testing Library. First, you import the component and the necessary RTL functions.

import React from 'react';
import { render, screen } from '@testing-library/react';
import MyButton from './MyButton'; // Our component to test

Basic Component Rendering Test

Let's write our first unit test to check if the MyButton component renders correctly with a given label.

We use render() to 'mount' the component and screen.getByText() to find the rendered text, then expect() to assert its presence.

import React from 'react';
import { render, screen } from '@testing-library/react';
import MyButton from './MyButton';

describe('MyButton', () => {
  test('renders with the correct label', () => {
    render(<MyButton label="Hello World" />);
    expect(screen.getByText(/Hello World/i)).toBeInTheDocument();
  });
});

Testing User Interactions

Components often respond to user actions, like clicks. We can simulate these interactions in our tests to ensure the component behaves as expected.

We use fireEvent.click() from RTL to simulate a user click and assert that our handler was called using Jest's mock functions.

import React from 'react';
import { render, screen, fireEvent } from '@testing-library/react';
import MyButton from './MyButton';

describe('MyButton', () => {
  test('calls onClick handler when clicked', () => {
    const handleClick = jest.fn(); // Jest's mock function
    render(<MyButton label="Click Me" onClick={handleClick} />);
    
    const buttonElement = screen.getByText(/Click Me/i);
    fireEvent.click(buttonElement);
    
    expect(handleClick).toHaveBeenCalledTimes(1);
  });
});

Mocking Dependencies

Unit tests should be isolated. If your component relies on external services, API calls, or even other complex modules, you should 'mock' them.

Mocking replaces real dependencies with controlled, fake versions. Jest provides powerful mocking capabilities (e.g., jest.fn() for functions, jest.mock() for modules) to ensure your component is tested in isolation.

Why Mock in MFEs?

In Micro Frontends, mocking is especially vital:

Decoupling: Test a component without requiring other Micro Frontends or shared libraries to be fully functional.
Speed: Mocks run instantly, avoiding slow network requests or complex computations.
Control: Simulate various scenarios (e.g., API success, failure, loading states) that are hard to trigger with real dependencies.

Unit Test Best Practices

To write effective unit tests for your federated components:

Test One Thing: Each test should focus on a single piece of functionality.
Keep it Simple: Avoid complex logic within tests.
Test Public API: Focus on what the component does (its output, interactions), not how it does it (internal state).
Maintainable: Use clear, descriptive test names.

Quick Check on Unit Testing

Which of the following are key benefits of unit testing individual components in a Micro Frontend architecture?

Recap: Unit Testing Components

Great job! You've learned the fundamentals of unit testing individual components within a Micro Frontend architecture.

We explored why isolation is key and how tools like Jest and React Testing Library help.
You saw examples of testing component rendering and user interactions.
Understanding mocking is crucial for maintaining test isolation and speed.

Mastering unit tests ensures each piece of your federated application is robust and reliable.

よくある質問

「Federatedコンポーネントの単体テスト」レッスンは無料ですか？

はい。「Federatedコンポーネントの単体テスト」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Micro Frontends Architecture with Module Federationコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Micro Frontends Architecture with Module Federationコースには全4レッスンが含まれています。

「Federatedコンポーネントの単体テスト」で何を学びますか？

Micro Frontend内の個々のコンポーネントに対する効果的な単体テストの書き方を学びます。ブラウザで直接実行するハンズオンコードでMicro Frontends Architecture with Module Federationを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Micro Frontends Architecture with Module Federationを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのMicro Frontends Architecture with Module Federationは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「Federatedコンポーネントの単体テスト」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このMicro Frontends Architecture with Module Federationレッスンでコードを書いて実行できますか？

はい。すべてのMicro Frontends Architecture with Module Federationレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Micro Frontends Architecture with Module Federationに戻る