Automated LambdaTest Failed Test Triage
Every morning, WebRun opens LambdaTest, collects the test sessions that failed overnight, groups them by build and browser, separates repeat failures from one off flakes, opens a Trello card per real failure with the session link, and records the whole run in Airtable.
How do I triage last night's failed test sessions before standup?
WebRun collects your overnight LambdaTest failures every morning and groups them by build, browser, and operating system. It labels repeat failures as likely regressions and reruns that passed as flaky, opens a Trello card with the session link for each real failure, and records the night in Airtable.
- Real regressions separated from flaky reruns before standup
- One ordered list instead of scanning the dashboard
- A daily failure trend recorded rather than remembered
Built for QA engineers · test automation leads · engineering managers · release 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
accounts.lambdatest.com/loginin a real browser with your saved login - no setup, no API keys. -
1
LambdaTest - collect overnight failures
lambdatest.com
WebRun opens LambdaTest to collect overnight failures. - Open LambdaTest and list the test sessions run since yesterday with a failed status
- Group the failures by build and by browser and operating system
- Read each failure's log line and capture the session link
- Compare against the previous runs: mark a test that failed repeatedly as a likely regression, and one that passed on rerun as flaky
Done when Every overnight failure is grouped by build and browser and labelled regression or flaky.
-
2
Trello - open a triage card per failure
trello.com
WebRun opens Trello to open a triage card per failure. - Create a card on your QA board for each likely regression
- Put the test name, build, browser, failing log line, and session link in the card
- Add flaky failures to a separate list rather than the main triage lane
- Update an existing card instead of opening a duplicate when the same test fails again
Done when Every real failure has a card with its session link ready to pick up.
-
3
Airtable - record the run history
airtable.com
WebRun opens Airtable to record the run history. - Write one row per failed session with build, browser, test name, and label
- Add the date so the same test failing across nights is easy to spot
- Keep a daily count of failures, regressions, and flakes for the trend
- Leave the code to your engineers. WebRun never reruns a test, merges, or deploys
Done when The night's failures are recorded with the running trend.
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 it rerun tests or touch the build?
No. WebRun reads session results and reports them. It never reruns a test, retries a build, merges a branch, or deploys anything. Fixing the failure stays with your engineers.
How does it separate a regression from a flake?
By history. A test failing across consecutive runs is labelled a likely regression and gets a triage card. A test that passed on a rerun goes to a separate flaky list so it does not crowd the board.
Will the same failure open a new card every morning?
No. When a test that already has a card fails again, WebRun updates that card with the new session link and date rather than opening a duplicate.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.