Micro Frontends Architecture with Module Federation · レッスン

アプリ横断のエンドツーエンドテスト

複数のFederation構成アプリケーションにまたがるユーザーフローをシミュレートするエンドツーエンドテストを実装します。

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

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

E2E Testing for Micro Frontends

Welcome! In this lesson, we'll dive into End-to-End (E2E) testing for Micro Frontends (MFEs). E2E tests are crucial for verifying that your entire application, composed of multiple independent MFEs, works seamlessly from a user's perspective.

Why E2E is Vital for MFEs

While unit and integration tests validate individual components or modules, E2E tests simulate real user interactions across the complete system.

They ensure critical user journeys function correctly.
They catch integration issues between different MFEs.
They validate the overall user experience.

This is especially important when MFEs are developed and deployed independently.

Key Challenges in MFE E2E

E2E testing in a Micro Frontend architecture presents unique challenges:

Independent Deployments: MFEs are deployed separately, requiring a stable testing environment.
Cross-MFE Communication: Ensuring data and events flow correctly between federated modules.
Environment Setup: Orchestrating multiple running MFEs for a single test run can be complex.
Stability: Tests can be brittle due to network latency or MFE loading times.

Choosing an E2E Framework

Several powerful E2E testing frameworks can be used for Micro Frontends:

Cypress: Known for its speed, developer-friendliness, and real-time reloading.
Playwright: Supports multiple browsers (Chromium, Firefox, WebKit) and languages, strong for automation.
Selenium: A classic, highly robust tool supporting many languages and browsers, often used for larger, complex applications.

For our examples, we'll use a Cypress-like syntax due to its readability.

Setting Up Your E2E Environment

To start E2E testing, you'll need to:

Install the framework: E.g., npm install cypress --save-dev.
Configure: Set up your framework's configuration file (e.g., cypress.json) to point to your application's base URL.
Run MFEs: Ensure all necessary Micro Frontends are running and accessible (e.g., http://localhost:3000 for the host, http://localhost:3001 for a remote).

Identifying Cross-MFE User Flows

The core of MFE E2E testing is focusing on user journeys that span across different federated applications.

Example: Imagine a user journey where they:

Log in using an Authentication MFE.
Browse products in a Product MFE.
Add an item to a cart managed by a Cart MFE.
Proceed to checkout via a Checkout MFE.

Each step involves a different MFE.

E2E Test: Basic Login Flow

Let's write a simplified test to simulate a user logging in. This test interacts primarily with an Authentication MFE and verifies redirection to a Dashboard MFE.

describe('Authentication MFE', () => {
  it('successfully logs in a user', () => {
    cy.visit('http://localhost:3000/login'); // Auth MFE route
    cy.get('#username').type('testuser');
    cy.get('#password').type('password123');
    cy.get('button[type="submit"]').click();
    cy.url().should('include', '/dashboard'); // Should redirect to Dashboard MFE
    cy.contains('Welcome, testuser').should('be.visible');
  });
});

E2E Test: Cross-MFE Interaction

Now, let's extend our scenario to interact with a Product MFE and a Cart MFE after a successful login. We'll use a custom command cy.login() for brevity.

describe('Product & Cart MFE Flow', () => {
  beforeEach(() => {
    cy.login('testuser', 'password123'); // Custom command for login
    cy.visit('http://localhost:3001/products'); // Product MFE route
  });

  it('adds a product to cart and views cart', () => {
    cy.get('.product-item').first().find('button.add-to-cart').click();
    cy.get('.cart-count').should('contain', '1'); // Cart MFE element
    cy.get('.cart-icon').click();
    cy.url().should('include', '/cart'); // Cart MFE route
    cy.contains('Your Cart').should('be.visible');
  });
});

Handling MFE Loading & Stability

When testing MFEs, dynamic loading can sometimes cause elements to not be immediately available. Use:

Explicit waits: cy.wait(ms) (use sparingly) or cy.wait('@alias') for network requests.
Assertions: Frameworks like Cypress automatically retry assertions, waiting for elements to appear.
Custom Commands: Encapsulate complex or repeated actions, like waiting for a specific MFE to render, into reusable commands.

Best Practices for MFE E2E

To make your E2E tests effective and maintainable for Micro Frontends:

Focus on Critical Paths: Test the most important user journeys, not every single detail.
Isolated Environments: Run tests against a dedicated, stable integration environment.
Automate in CI/CD: Integrate E2E tests into your Continuous Integration/Deployment pipeline.
Maintainability: Keep tests readable, modular, and resilient to minor UI changes.

Quick Check: E2E in MFEs

End-to-End (E2E) testing for Micro Frontends ensures that a user's entire journey across different, independently developed and deployed applications works as expected. It simulates real user interactions to catch integration issues that unit or integration tests might miss.

Recap: E2E Across Apps

We explored End-to-End testing for Micro Frontends, understanding its crucial role in validating full user journeys across independently deployed applications. We discussed common challenges, essential tools like Cypress, and walked through examples of testing cross-MFE interactions. E2E tests are vital for ensuring a seamless user experience in a federated architecture.

よくある質問

「アプリ横断のエンドツーエンドテスト」レッスンは無料ですか？

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

「アプリ横断のエンドツーエンドテスト」で何を学びますか？

複数のFederation構成アプリケーションにまたがるユーザーフローをシミュレートするエンドツーエンドテストを実装します。ブラウザで直接実行するハンズオンコードでMicro Frontends Architecture with Module Federationを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

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

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

「アプリ横断のエンドツーエンドテスト」レッスンにはどのくらい時間がかかりますか？

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

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

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

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

← Micro Frontends Architecture with Module Federationに戻る