Description

Tightens the declarative MetaMetrics expectations static scan in collect-qa-stats.mjs so QA stats include every event naming pattern used under tests/helpers/analytics/expectations/.
The metametrics slice of qa-stats.json is built by regex-parsing expectation modules. Several valid patterns produced no counted event names, so Grafana / coverage metrics understated E2E analytics coverage even when expectations existed.

Cases that were previously missed

Not a regression / intentional: eventNames: [ ...someArray ] — spread segments are ignored here because the referenced const (e.g. transactionEventNames, expectedEventNames) is still ingested via the existing const *Names* / event-ish array path.

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

N/A

Screenshots/Recordings

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.