0Pricing
Micro Frontends Architecture with Module Federation · Lesson

End-to-End Testing Across Apps

Implement end-to-end tests that simulate user flows across multiple federated applications.

End-to-End Testing Across Apps is a free Micro Frontends Architecture with Module Federation lesson on CoddyKit — lesson 3 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.

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:

  1. Install the framework: E.g., npm install cypress --save-dev.
  2. Configure: Set up your framework's configuration file (e.g., cypress.json) to point to your application's base URL.
  3. 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.

Frequently asked questions

Is the “End-to-End Testing Across Apps” lesson free?

Yes — the full text of “End-to-End Testing Across Apps” 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 “End-to-End Testing Across Apps”?

Implement end-to-end tests that simulate user flows across multiple federated applications. 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 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “End-to-End Testing Across Apps” 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

  1. Unit Testing Federated Components
  2. Integration Testing Strategies
  3. End-to-End Testing Across Apps
  4. Contract Testing Between Micro Frontends
← Back to Micro Frontends Architecture with Module Federation