microsoft / microsoft/RepoLaunch
Has Anyone Tried Running Only PR-Relevant Tests?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 145
- Forks
- 13
- Avg merge
- 5h 25m
- Merged PRs (30d)
- 2
Description
Hi! We've found that a significant portion of the repository construction process is spent running the entire test suite and parsing the test logs.
We're wondering whether it would be possible to first identify a subset of test cases that are relevant to a given PR, and then only validate those test cases afterward.
Have you ever tried something similar? If so, we'd really appreciate it if you could share your experience or any insights.
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
The issue names no files, tests, or entry points. Start by tracing how RepoLaunch currently runs the full test suite and parses its logs, then investigate how a PR-relevant subset could be identified. Done would require a defined approach and evidence that the selected tests adequately validate a PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100