Micro Frontends Architecture with Module Federation · Lesson

Unit Testing Federated Components

Learn to write effective unit tests for individual components within your Micro Frontends.

Unit Testing Federated Components is a free Micro Frontends Architecture with Module Federation lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Micro Frontends Architecture with Module Federation learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

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.

Frequently asked questions

Is the “Unit Testing Federated Components” lesson free?

Yes — the full text of “Unit Testing Federated Components” is free to read here on the web, and the Micro Frontends Architecture with Module Federation course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Micro Frontends Architecture with Module Federation course, upgrade to CoddyKit PRO.

What will I learn in “Unit Testing Federated Components”?

Learn to write effective unit tests for individual components within your Micro Frontends. You practise Micro Frontends Architecture with Module Federation with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Micro Frontends Architecture with Module Federation?

No prior experience is required. Micro Frontends Architecture with Module Federation on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Unit Testing Federated Components” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Micro Frontends Architecture with Module Federation lesson?

Yes. Every Micro Frontends Architecture with Module Federation lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

Unit Testing Federated Components
Integration Testing Strategies
End-to-End Testing Across Apps
Contract Testing Between Micro Frontends

← Back to Micro Frontends Architecture with Module Federation