Automated BrowserStack Test Coverage Scorecard
Every Friday afternoon, WebRun opens BrowserStack, compiles the week's automated test run results across every browser and device combination, logs the pass rate and total coverage to Airtable, and emails the QA team a short summary so testing gaps surface before the next release.
How do I track my weekly BrowserStack test coverage automatically?
WebRun compiles your week's BrowserStack automated test results every Friday, totaling the pass rate by browser and device. It logs the numbers to an Airtable tracker so trends build over time, and emails the QA team a short internal summary, so coverage gaps surface before the next release goes out.
- Testing gaps surface every Friday instead of at release time
- Browser and device coverage is tracked automatically week over week
- QA gets a summary without compiling results by hand
Built for QA teams · test engineers · release managers · engineering teams
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
www.browserstack.com/users/sign_inin a real browser with your saved login - no setup, no API keys. -
1
BrowserStack - compile the week's test run results
- Open BrowserStack Automate and pull this week's test run history
- Total the pass and fail counts by browser and device
- Note which browser or device combinations had the most failures
Done when The week's test runs are totaled by browser and device with pass and fail counts.
-
2
Airtable - log the weekly coverage numbers
airtable.com
WebRun opens Airtable to log the weekly coverage numbers. - Log this week's totals as a new row in the test coverage tracker
- Record the pass rate and the browsers or devices with the most failures
- Keep prior weeks in place so the trend is visible
Done when This week's coverage numbers are logged as a new row in Airtable.
-
3
Gmail - email the QA team a summary
gmail.com
WebRun opens Gmail to email the QA team a summary. - Draft a short internal summary email to the QA team
- Include the pass rate, total runs, and the weakest browser or device coverage
- Send it to the internal QA distribution list
Done when The QA team has this week's summary email.
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 run or change any tests?
No. WebRun only reads completed test results from BrowserStack. Writing or changing tests stays with your QA and engineering teams.
Who receives the summary email?
Your internal QA distribution list. It is an internal report, never sent to a customer or outside your team.
Can I see trends over time, not just this week?
Yes. Every week's numbers are added as a new row in the same Airtable tracker, so the coverage trend builds up automatically.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.