Has Anyone Tried Running Only PR-Relevant Tests?

Open
#36 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
testing-qa

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.

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.

Dominant language
Python
Stars
145
Forks
13
Avg merge
5h 25m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/RepoLaunch

All issues in microsoft/RepoLaunch

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.