MetaMask / MetaMask/metamask-extension
[SPIKE]: Document brief technical proposal on scope and solution of automated migration/version tests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
- document 3-4 cases of regressions that could have been prevented by automated migration e2e tests
- explain why they would not have been caught by existing tests
- describe, in written form, the tests that would have prevented the regression: the assertions needed, the flows to automate, the fixtures needed
- propose a general system or set of guidelines
Output should be roughly 1-2 google docs pages of content. Can be done within github comments
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 identifying 3-4 migration or version regressions that automated end-to-end tests could have prevented, then compare them with the existing tests. Document the necessary assertions, automated flows, fixtures, and a general testing system or guidelines in roughly 1-2 pages, either in Google Docs or a GitHub comment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100