Measuring Coverage and why Cypress Cloud UI Coverage is the Holy Grail
summary
Shows how turning on Cypress Cloud UI Coverage and pairing UI reports with code coverage collected via CI (GitHub Actions) exposes exact untested endpoints and elements, not vague promises. Reports reveal missed attributes like absent data-cy selectors, let teams exclude autogenerated IDs and apply element grouping to collapse repetitive checks, and drive concrete gains: unit tests rise from ~20% to >50%, smoke goes 0→100% and regression to ~95%, enabling release cadence from biweekly to weekly.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:24Coverage terminology explained
- 2:49Feature set coverage approach
- 8:24Code coverage tools and setup
- 12:40Cypress tests and code coverage
- 15:10UI coverage in Cypress Cloud
- 17:15UI coverage configuration tips
- 21:30Lessons learned from UI coverage
- 23:17Final thoughts on coverage types
- 24:41Q&A session
related talks
32mCypress.io – the State of the Art End-to-end Testing Tool
45mAchievement Unlocked: Drive development, increase velocity, and write blissful...
30mTesting Tools and Their Friends
35mSleeping better at night
38mFrontend Tests: what nobody said to you
46mCypress in practice — overview of the most important capabilities
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
01h 00mRequirement Coverage: Myth or an Ultimate Goal