codecov / codecov/codecov-action
Tests tab doesn't tell you why a flaky test is failing
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 260
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 1
Description
At first glance, it looks useful to see which tests are the most flaky in the Tests tab.
However, this turns out to be of limited use, when you can't see any way to see the test failures.
I'd propose adding links to the failed CI runs for each test somewhere, so we can actually debug the flaky tests in future.
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 identifies the Tests tab and failed CI runs but names no repository files or tests. Start by locating the Tests tab entry point and tracing how flaky tests are displayed; done means each test exposes links to the failed CI runs needed for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100