MetaMask / MetaMask/metamask-extension

ci: e2e report displays incorrect test status for certain specs

Open
#34,926 0 comments 0 reactions 0 assignees View on GitHub
needs-triage team-extension-platform
Dominant language
TypeScript
Stars
13.2k
Forks
5.6k
Avg merge
2d 5h
Merged PRs (30d)
451

Description

### What is this about?

e2e report displays incorrect test status for certain specs.

Example: https://github.com/MetaMask/metamask-extension/actions/runs/16797281515/job/47572038085?pr=34888

Image

Image

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by inspecting the linked GitHub Actions run and compare the displayed e2e report statuses with the results for the affected specs. Trace the report-generation entry point in the TypeScript CI code and verify that the corrected status is shown for those specs; the issue provides no file or test path, so repository-wide investigation is required.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.