Micro Frontends Architecture with Module Federation · 课时

跨应用端到端测试

实现端到端测试，模拟跨多个联邦化应用的用户流程。

跨应用端到端测试 是 CoddyKit 上的免费 Micro Frontends Architecture with Module Federation 课时。这是第 3 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 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.

常见问题解答

「跨应用端到端测试」课时是免费的吗？

是的 — 「跨应用端到端测试」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Micro Frontends Architecture with Module Federation 课程的其余内容，请升级到 CoddyKit PRO。 Micro Frontends Architecture with Module Federation 课程共包含 4 节课。

「跨应用端到端测试」这节课中我会学到什么？

实现端到端测试，模拟跨多个联邦化应用的用户流程。你通过在浏览器中直接运行的动手代码来练习 Micro Frontends Architecture with Module Federation，全天候 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