test(e2e): skip consistently failing Appium confirmations Android smokes (MMQA-2254)

[chrisleewilcox]

Description

appium-confirmations-android-smoke (shards 1 and 2) is consistently failing across unrelated PRs and blocking merges (see Slack / MMQA-2254).

This PR only quarantines the hard/consistent main blockers so other teams can merge.

Skipped:

Shard	Spec	Case
1	7702/batch-transaction.spec.ts	wallet_sendCalls batch (keep smart-account upgrade running)
1	contract-deployment.spec.ts	entire describe (single test)
1	dapp-initiated-transfer.spec.ts	entire describe (single test; can hang ~35m)
2	token-approve/set-approval-for-all.spec.ts	ERC1155 setApprovalForAll
2	token-approve/set-approval-for-all.spec.ts	revoke mode describe (single test; hard-fail on recent main)

Not skipped: ERC721 setApprovalForAll (often recovers), increase-allowance / approve mixes, already-skipped suites.

Changelog

CHANGELOG entry: null

Related issues

Fixes: https://consensyssoftware.atlassian.net/browse/MMQA-2254

Related: https://consensyssoftware.atlassian.net/browse/MMQA-2232

Manual testing steps

Feature: Confirmations Android smoke unblock quarantine

  Scenario: Skipped cases do not run; remaining cases still execute
    Given appium-confirmations-android-smoke on CI
    When the suite runs
    Then the five quarantined cases are reported skipped
    And smart-account upgrade and ERC721 setApprovalForAll still run

Screenshots/Recordings

N/A — skip-only change; no product UI.

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
• I've tested with a power user scenario
• I've instrumented key operations with Sentry traces for production performance metrics

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.

[github-actions]

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.

[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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: SmokeConfirmations
• Selected Performance tags: None (no tests recommended)
• Risk Level: medium
• AI Confidence: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
Hard rule (test-spec-tag-extraction): Spec files changed directly. Running their associated tags: SmokeConfirmations

Performance Test Selection:
No app code was changed — only test spec files had tests skipped. There is no performance-sensitive code path affected, so no performance tests are needed.

View GitHub Actions results

[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