การทดสอบหน่วยของคอมโพเนนต์แบบสหพันธ์

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.