microsoft / microsoft/winget-cli
Improve Pipeline Handling of Copying Test Results
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
In #6287 it was found that a double copy is happening on test results. This issue is to track an improvement suggestion from that PR
A better solution could be to prevent the double copy from happening to begin with. I believe this could be prevented if we cleared the winget logs during the
OneTimeSetUp. So, each time we call the E2E tests with different options, we would only need to copy what that test run generated.
Originally posted by @florelis in https://github.com/microsoft/winget-cli/issues/6287#issuecomment-4983684307
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 with PR #6287 and the E2E test setup, especially the OneTimeSetUp entry point mentioned in the issue. Trace how winget logs are cleared and how test results are copied for runs with different options. Done means each test run copies only its own generated results, without a double copy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100