performance-testing

Automate end-to-end performance measurement on real devices with TimerHelper and platform thresholds.

3.0k|1.6k|Updated Jul 18, 2018
One-click install
npx skills add https://github.com/MetaMask/metamask-mobile --skill performance-testing-metamask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-testing
Source: https://github.com/MetaMask/metamask-mobile/tree/main/.agents/skills/performance-testing
Command: npx skills add https://github.com/MetaMask/metamask-mobile --skill performance-testing-metamask

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

E2E Performance Testing for real devices and networks is unified, standardized, and repeatable, enabling teams to measure real user flows with deterministic timers and clear ownership.

Core Features & Use Cases

  • Real-device measurements on physical hardware or cloud devices to capture authentic performance data.
  • Timer-based measurements with platform-specific thresholds to quantify user-perceived latency.
  • Page-object pattern and structured data collection to ensure repeatability and maintainability.
  • Use Case: Create, edit, or review performance tests for onboarding, login, and common flows with predefined templates and metrics.

Quick Start

Define and run a basic performance test by selecting a real-device flow, a TimerHelper timer, and a platform-specific threshold, then collect and review the results.

Frequently Asked Questions about performance-testing

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

FAQPage Schema
How do I automate end-to-end performance testing on real devices?

Measure real-user flows on physical or cloud hardware by applying TimerHelper, PerformanceTracker, and page-object patterns to capture authentic performance data with platform-specific thresholds.

What is the best way to measure user-perceived latency for onboarding and login flows?

Use timer-based measurements with platform-specific thresholds to quantify user-perceived latency for onboarding, login, and Dapp-connect scenarios, ensuring repeatability through structured data collection.

Does this performance testing approach work with Playwright automation?

Yes, this approach integrates with Playwright automation to execute end-to-end performance tests, utilizing TimerHelper and PerformanceTracker to capture deterministic timer granularities across real-device flows.

Can I use page-object patterns to structure my E2E performance tests?

Yes, you can apply the page-object pattern to ensure the repeatability and maintainability of your E2E performance tests while collecting structured data across onboarding and login scenarios.

How do I define platform-specific thresholds for performance testing?

Define platform-specific thresholds by selecting a real-device flow, configuring a TimerHelper timer, and setting the acceptable latency limits to quantify user-perceived latency for that specific platform.

Why do I need to register resources when creating performance tests?

Proper resource registration is required to satisfy team tagging requirements and ensure deterministic timer granularities, maintaining unified and standardized performance measurement across testing environments.