[cmd-ob]

Description

Complements MetaMask/github-tools#274 (merged) for MMQA-2013.

Slack links from the Playwright Appium test health report were 404ing because Playwright reports paths relative to testDir (tests/smoke-appium), e.g. accounts/foo.spec.ts, while GitHub blob URLs need the repo-relative path.

This PR:

1. Pins playwright-test-health-report to the merged github-tools main commit (a4a179a) that adds path normalization and the test-source-prefix input
2. Passes test-source-prefix: tests/smoke-appium from .github/workflows/flaky-test-report.yml

Validation

Manual workflow_dispatch on this branch succeeded:
https://github.com/MetaMask/metamask-mobile/actions/runs/30814511794

That run used test-source-prefix: tests/smoke-appium against the pre-merge github-tools commit; pin was then retargeted to the merged main SHA (a4a179a).

Changelog

CHANGELOG entry: null

Related issues

Fixes: MMQA-2013
Refs: MetaMask/github-tools#274

Manual testing steps

Feature: Appium Playwright health report Slack links

  Scenario: workflow dispatch generates report with valid blob URLs
    Given MetaMask/github-tools#274 is merged on main
    And secrets for the Playwright health Slack webhook are configured

    When a maintainer runs workflow_dispatch on "Flaky test report" with job=appium
    Then the Slack report spec links resolve to files under tests/smoke-appium/
    And absolute CI paths under tests/ also resolve without 404s

Validated via workflow_dispatch: https://github.com/MetaMask/metamask-mobile/actions/runs/30814511794 (success).

Screenshots/Recordings

N/A — CI workflow / Slack link formatting only; no app UI changes.

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

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.

  

[metamask-ci]

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

• Pre-merge author checklist has unchecked items (e.g. "I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors."). Every box must be consciously checked — see docs/readme/ready-for-review.md.

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud