Description

Introduces an automated pipeline that collects test metrics after every successful push to main and writes them to a qa-stats.json artifact.

• New qa-stats.yml workflow — triggers after CI succeeds on main (excludes PRs, forks, failed runs)
• New collect-qa-stats.mjs — extensible script that fetches CI artifacts via GitHub API (paginated) and collects component_view_tests_count and unit_tests_count (passed + failed, excludes skipped/todo). Collector failures are isolated and don't crash the run
• ci.yml — shard jobs now extract a minimal {"count": N} via jq instead of uploading full Jest JSON; removed redundant merge-cv-test-coverage job (folded into merge-unit-and-component-view-tests), saving one yarn install per CI run; renamed coverage artifact to lcov.info

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

Feature: QA Stats collection on main

  Scenario: CI completes successfully on main
    Given a push to the main branch triggers the ci workflow
    And all cv-test shards complete successfully

    When the merge-cv-test-coverage job runs
    Then a cv-test-stats artifact is uploaded containing { "component_view_test_number": N }

    When the QA Stats workflow is triggered via workflow_run
    Then a qa-stats artifact is uploaded containing { "component_view_test_number": N }

Screenshots/Recordings

Before

N/A — new workflow, no prior state.

After

N/A — CI-only change; artifacts visible in GitHub Actions run summary after merging to main.

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.

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.