Automated Codecov Coverage Reporting
Every Monday, WebRun signs in to Codecov, reads the coverage percentage for each repository and how it moved over the last week, lists the files with the lowest coverage and the most uncovered lines, posts the ranked report to Microsoft Teams, and drafts the tech lead a WhatsApp summary of the worst offenders.
How do I find the least tested code across all my repositories?
WebRun signs in to Codecov every Monday, records coverage for each repository and how it moved over the week, and lists the files holding the most uncovered lines. It posts the ranked report to Microsoft Teams and drafts the tech lead a WhatsApp summary of the biggest regressions.
- The team picks testing work from a ranked list rather than a hunch
- Coverage regressions are named in the week they happen
- One report covers every repository instead of a dashboard per repo
Built for engineering managers · platform teams · QA leads · open source maintainers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.codecov.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Codecov - read coverage across repos
codecov.io
WebRun opens Codecov to read coverage across repos. - Sign in to Codecov and open your organisation's repository list
- Record the current coverage percentage for each repository on its default branch
- Compare each figure with the same day last week and note the change
- Open the file view for the repositories that moved down or sit lowest
- List the files with the most uncovered lines, since a big file at 70 percent hides more risk than a tiny file at 40 percent
Done when Every repository has a coverage figure, a weekly change and its worst files listed.
-
2
Microsoft Teams - post the ranked report
microsoft.com
WebRun opens Microsoft Teams to post the ranked report. - Post the weekly coverage report to your engineering channel in Microsoft Teams
- Show one line per repository with coverage, the weekly change and an arrow
- Underneath, list the ten files with the most uncovered lines across the organisation
- Put repositories that fell this week at the top so the regression is the first thing read
Done when The engineering team has this week's coverage report and worst files in Teams.
-
3
WhatsApp - brief the tech lead
whatsapp.com
WebRun opens WhatsApp to brief the tech lead. - Draft a short WhatsApp message for the tech lead with the three biggest coverage regressions
- Include the organisation-wide coverage figure and its direction
- Leave the message as a draft to review and send, so nobody is pinged automatically out of hours
- Skip the draft in a week where nothing regressed
Done when The tech lead has a drafted summary of this week's regressions.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change any repository settings or thresholds?
No. WebRun reads Codecov and nothing else. It never edits a coverage target, a YAML config, a status check or a repository setting, so no pull request starts failing because of this run.
Will it message developers directly?
No. The report goes to your internal Microsoft Teams channel, and the WhatsApp summary is left as a draft for the tech lead. No individual developer is contacted by WebRun.
Why rank by uncovered lines instead of percentage?
Because a large file at 70 percent can hide far more untested code than a small file at 40 percent. The report shows both, with the files holding the most uncovered lines listed first.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.