Auto-testing for situational awareness
summary
Auto-tests focus on timelines not just pass/fail: nightly GitLab CI runs on Alpha correlate test durations, executed-test counts and reruns to reveal that a Wi‑Fi-default-off change blocks the out‑of‑box flow, causes stuck GUI navigation and breaks page object model tests. Strategy uses YAML retries, per-job cleanup scripts and a page object model to recover tests, ELK/ Elastic stack dashboards to spot trends, and a small open‑source Python behave GUI to review Gherkin steps — together they catch regressions early and distinguish genuine failures from flakiness.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:35Invest in automated testing
- 3:40Situational awareness in testing
- 7:12Observability and testing pyramid
- 9:46Correlating timelines for insights
- 11:56Cost of unreliable test runs
- 13:22Detecting regressions case study
- 19:56Situational awareness in action
- 22:26Out-of-box regression
- 25:17Broken tests after changes
- 28:50Strategies for more tests
- 34:01Page object model
- 40:49Avoiding GUI dependency pitfalls
- 43:42Demonstrating Behave GUI tool
- 50:32Focusing on trends
- 51:39Tester-developer collaboration
related talks
53mTest architecture is a real thing
21mThe Essential Pillars of Automation Testing for Success
57mAdvanced Testing Techniques: Tips from the trenches
56mTestOps at scale
27mQuest for Adequate Autotest Coverage
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
55mThe art of living with broken things
32mLiving on Crotches or UI Automation Antipatterns
