Skip to content

Conversation

@javiergarciavera
Copy link
Contributor

@javiergarciavera javiergarciavera commented Nov 11, 2025

Description

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

Pre-merge reviewer checklist

  • I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

Note

Adds a comprehensive appwright/README.md documenting the mobile performance test setup, execution, and reporting.

  • Documentation:
    • Adds appwright/README.md detailing:
      • Test structure and directories (appwright.config.ts, fixtures/, reporters/, tests/performance/*, utils/, test-reports/).
      • Configuration: projects (local Android/iOS, BrowserStack variants), timeouts, reporters, report paths.
      • Running tests: yarn scripts and Appwright CLI usage with --project and --config.
      • Test categories: login, onboarding, predict; key specs listed.
      • Page Object Model: screen objects location, example usage, shared flows in utils/Flows.js.
      • Environment variables: BrowserStack creds/devices/app URLs and test SRPs/passwords.
      • Reports and metrics: HTML report location and custom performance JSON outputs; metrics tracked and timer example.
      • Best practices, troubleshooting, additional resources, contributing, and support guidance.

Written by Cursor Bugbot for commit a1ad827. This will update automatically on new commits. Configure here.

@github-actions
Copy link
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamaskbot metamaskbot added the team-qa QA team label Nov 11, 2025
@javiergarciavera javiergarciavera added no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed No QA Needed Apply this label when your PR does not need any QA effort. labels Nov 11, 2025
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

No QA Needed Apply this label when your PR does not need any QA effort. no-changelog no-changelog Indicates no external facing user changes, therefore no changelog documentation needed size-M team-qa QA team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants