Automated Coveralls Coverage Drop Alerts
Every hour, WebRun checks Coveralls for repositories whose test coverage dropped more than two percentage points on the latest build, messages the team on WhatsApp with the before and after numbers, and adds a Google Calendar reminder to review the drop at the next standup.
How do I catch a code coverage drop before it becomes normal?
WebRun checks Coveralls every hour for any repository whose coverage dropped more than two percentage points on its latest build, messaging the team on WhatsApp with the before and after numbers. It also adds a Google Calendar reminder to review the drop at the next standup, so a real coverage gap gets a conversation instead of being ignored.
- Coverage drops get flagged within the hour instead of surfacing weeks later
- The team gets a scheduled standup review instead of an easily ignored alert
- Real coverage gaps get a conversation before they become a pattern
Built for Engineering teams · QA leads · engineering managers · 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
coveralls.io/sign-inin a real browser with your saved login - no setup, no API keys. -
1
Coveralls - check for coverage drops
- Open Coveralls and review the latest coverage percentage per repository
- Compare it against the previous build's coverage
- Flag any repository that dropped more than two percentage points
Done when Every repository with a coverage drop over two points is identified with its before and after numbers.
-
2
WhatsApp - message the team
whatsapp.com
WebRun opens WhatsApp to message the team. - Message the team on WhatsApp for each repository with a coverage drop
- Include the repository name, the coverage before and after, and the build link
- Keep the message short and direct
Done when The team has been messaged about every coverage drop over two points.
-
3
Google Calendar - schedule a review reminder
calendar.google.com
WebRun opens Google Calendar to schedule a review reminder. - Add a reminder to the team's Google Calendar for the next standup
- Title it as a coverage review for the affected repository
- Include the coverage numbers in the event notes
Done when A review reminder is scheduled on the calendar for the next standup.
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
Will WebRun write tests to bring coverage back up?
No. It only detects the drop and notifies the team. Writing the missing tests stays with the developers who own that code.
Why two percentage points as the threshold?
A drop that small is usually a real gap in test coverage rather than normal noise from a small file change, though the threshold can be adjusted for your repositories.
Does it flag every commit or just merged builds?
It checks the coverage reported on each build Coveralls records, so it reflects whatever your CI pipeline is already reporting.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.