MetaMask / MetaMask/metamask-extension
Define a manual QA process and add e2e coverage for older browsers
Open
Nobody has claimed this yet.
needs-qa
team-extension-platform
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
What: define QA manual process and add e2e coverage for older browsers.
cc @Gudahtt
Oldest versions we are supporting:
- FireFox:
68.0https://github.com/MetaMask/metamask-extension/blob/develop/app/manifest/v2/firefox.json#L5 - Chrome:
66https://github.com/MetaMask/metamask-extension/blob/develop/app/manifest/v2/chrome.json#L7
How: as per @pedronfigueiredo 's suggestion, we could investigate whether Browser Stack fits our needs.
Relevant related issues:
- https://consensys.slack.com/archives/GTQAGKY5V/p1669860469331419
- Notify users that we are dropping support for their current browser https://github.com/MetaMask/metamask-extension/issues/16283
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the supported versions in app/manifest/v2/firefox.json and app/manifest/v2/chrome.json, then evaluate whether BrowserStack fits the older-browser testing needs. Done means documenting a manual QA process and adding end-to-end coverage for Firefox 68 and Chrome 66, with the support-notification issue considered as related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100