e2e-testing

Automate reliable end-to-end tests for MetaMask extension and mobile apps.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/abretonc7s/metamask-skills --skill e2e-testing-abretonc7s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/abretonc7s/metamask-skills/tree/main/domains/testing/skills/e2e-testing
Command: npx skills add https://github.com/abretonc7s/metamask-skills --skill e2e-testing-abretonc7s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides structured guidelines and best practices for conducting reliable and maintainable end-to-end tests of MetaMask's extension and mobile applications, reducing flaky failures and ensuring consistent quality.

Core Features & Use Cases

  • Test Organization: Defines clear folder structures for logical grouping of tests.
  • Framework Principles: Emphasizes Page Object Model, setup fixtures, and proper wait strategies.
  • Test Stability: Offers solutions for flaky tests caused by timing, element states, or network issues.
  • Flow Creation: Guides on building reusable user flow objects for complex multi-page interactions.
  • Use Case: Developers write robust, scalable tests for critical user workflows, such as onboarding or transaction signing, ensuring smooth updates and releases.

Quick Start

Use the e2e skills guide to write a test that reliably logs into the extension, performs a transaction, and verifies the result.

Frequently Asked Questions about e2e-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write reliable end-to-end tests for MetaMask extension and mobile apps?

To write reliable MetaMask end-to-end tests, use the Page Object Model, apply proper wait strategies, and control application state programmatically to reduce flakiness and ensure maintainability.

What is the best way to organize e2e testing files for complex MetaMask workflows?

The best way to organize MetaMask e2e testing files is using a defined folder structure for logical grouping, alongside reusable user flow objects for complex multi-page interactions like onboarding or transaction signing.

Why does my MetaMask e2e testing fail intermittently during element interactions?

Intermittent MetaMask e2e testing failures are often caused by timing, element states, or network issues, which can be resolved by implementing proper wait strategies and setup fixtures.

Can I automate transaction signing flows for the MetaMask extension without encountering flaky tests?

Yes, you can automate transaction signing flows without flaky tests by building reusable user flow objects and controlling the application state programmatically to ensure consistent execution.

Do I need to use the Page Object Model for mobile and extension e2e testing of MetaMask?

Using the Page Object Model is highly recommended for MetaMask mobile and extension e2e testing because it provides framework principles that ensure your tests remain maintainable and scalable.