Automated Applitools Browser Coverage Checks
Every night, WebRun opens Applitools, reads the batches that ran, lists which browsers and viewports each application was actually tested on, compares that against the matrix you support, posts the gaps to Telegram, and texts the QA lead when a supported browser was skipped entirely.
How do I check which browsers and viewports my visual tests never ran on?
WebRun checks your Applitools coverage every night. It reads last night's batches, lists the browsers and viewports each application actually ran on, compares that against the matrix you support, posts the missing combinations to Telegram, and texts the QA lead when a supported browser was never tested at all.
- An untested browser is caught overnight, not in a production bug report
- Coverage is measured against your supported matrix, not guessed
- The QA lead gets a text only when a browser had zero runs
Built for QA leads · test engineers · release managers · frontend 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
eyes.applitools.com/app/loginin a real browser with your saved login - no setup, no API keys. -
1
Applitools - read last night's batches
applitools.com
WebRun opens Applitools to read last night's batches. - Open Applitools and list the batches from the last 24 hours
- For each application, record which browsers and viewport sizes tests ran on
- Compare that set against the browser and viewport matrix you support
- Note every combination in the matrix with no test at all last night
Done when Each supported browser and viewport combination is marked as covered or missing.
-
2
Telegram - post the coverage gaps
telegram.org
WebRun opens Telegram to post the coverage gaps. - Post the coverage table to the QA channel with covered and missing marked clearly
- List the missing combinations first, per application
- Show how the gap compares against the previous night
Done when The QA channel has last night's coverage table in Telegram.
-
3
Twilio - text the QA lead
twilio.com
WebRun opens Twilio to text the QA lead. - Send a short SMS only when a supported browser had no test run at all
- Name the application and the browser so the fix is obvious before standup
- Text only your own saved QA numbers. No customer is ever contacted
Done when The QA lead has a text when a supported browser went completely untested.
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 start test runs or approve results?
No. WebRun reads the batches that already ran and reports what was missing. Triggering a run, accepting a baseline, or approving a diff stays a decision your QA team makes.
Where does the supported matrix come from?
You give it to WebRun once: the browsers and viewport sizes your product officially supports. Every nightly run compares the Applitools batches against that list.
Who gets the text message?
Only the internal QA numbers you save. Twilio is used to reach your own on-call phone when a supported browser had zero coverage, never to message a customer or an outside address.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.