Overcome the trap of reproducing test failures with smart troubleshooting
summary
Shows a concrete workflow: enable browser-level recordings so headless runs produce viewable videos, and capture a DOM snapshot at failure (HTML source) so invisible overlays and corrupted attributes are inspected. Demo runs two browsers (headless and headed), intentionally fails both, and proves the recordings plus saved HTML let a tester find the root cause without manual reproduction. Recommends investing in open‑source tools that automatically save these artifacts during test failures.
AI-written summary · about
related talks
24mPlaying your tests wright
33mRecording Video During Test Runs
19mWorking Well: The Future of Web Testing
13mUsing Headless Browsers to ship reliable and performant apps
27mPlaying your tests wright
19mDevTools and Headless Chrome - The Automation Power-Couple
47mDebugging, Profiling, & Rocking Out with Browser-Based Developer Tools!
54mDebugging Effectively