MetaMask / MetaMask/metamask-extension
Allow test-suite to detect trivial changes and not re-run tests
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
I don't know if this is a thing that anyone does yet, but there are some cases where we can plainly say tests don't need to run again, because they definitely will not affect our tests:
- README update
- CHANGELOG update
And some types of changes that don't need a _full_ run of the suite, which _may_ be detectable with static analysis:
- Lint fixes
- Code style fixes
- Some kinds of code organization?
Just opening an aspirational issue here to say "It'd be great if we didn't need to run our 20 minute test suite for every trivial change" :)
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
No files, tests, or entry points are named. Start by examining the current test-suite configuration and how changes trigger it. Define which README and CHANGELOG updates can safely skip testing, and which other changes can use partial runs, then verify that trivial changes avoid the full suite without reducing required coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100