Trust Issues With UI Automation
summary
Claims a Testability Validation Service (TSVS) that plugs into CI/Jenkins, runs static analysis, runtime checks, runs five times by default and parallel/platform checks before a test PR merges, and enforces a 15‑minute PR test window. It chunks nightly runs, does log analysis against a known‑error library, retries against mock services, auto‑disables flaky tests and files JIRA bugs. Results: flaky failures drop to >85% green, release cadence shrinks from three months to one week and ROI on automation rises well above the original 3%.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:57UI Automation Stability
- 4:54Regression Analysis
- 6:16Regression Results
- 7:01E2E Test Automation
- 7:47Test Failure
- 8:42Solution?
- 9:02Test Stability Validation Service
- 11:38Testing your Test
- 16:49Reality
- 17:26Test Maintenance
- 20:12Log Analysis
- 25:53Realized Improvements
- 27:57Future for TSVS
related talks
39mBuilding The Blocks of Trust In Automation
40mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
43mTransformative Culture
34mUsing Test Automation for Continuous Integration, Delivery and Quality
38mScaling Automated Testing & Architecture from Startup to Enterprise
51mRedefining test automation
31mThe Build That Cried Broken: Building Trust in Your Continuous Integration Tests
33mIntentional and Unintentional Compromises in Test Automation