Mastering UI tests
summary
Advocates replacing slow full end-to-end runs with many fast UI-focused tests: stub the backend with Cypress intercept AJAX requests to create UI integration tests that take ~2–3s each instead of ~20s for full e2e. Keep only 5–20 full e2e happy‑path checks and 100–200 UI integration checks, assert request payloads and responses, import app constants, expose test shortcuts to set auth state, and rely on time-travel and automatic waits plus screenshots/videos for precise, actionable failures.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:35Testing principles
- 2:34Frontend testing
- 7:33Writing endtoend tests
- 13:33Waiting for deterministic events
- 17:53Frontend shortcuts
- 21:07Frontend constants
- 24:00Endtoend tests
- 25:43Selectors vs contents
- 28:23Why test manually
- 35:12Does it support only Chrome
- 36:29Is it all about frontend testing
related talks
35mSpeeding Up UI Tests
35mCypress Tales: Effective E2E Testing
38mFrontend Tests: what nobody said to you
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
23mRun your end-to-end tests at light speed with Cypress
47mEnd to End Testing with Cypress
51mUI tests are dead, long live UI tests!
53mModern Web Testing: Going Beyond Selenium