Answers to Your Burning Questions About Testing
summary
Ten concrete answers about end-to-end testing appear: tests are independent confirmation, long E2E flows split into checkpoints and state resets, run tests on every commit, keep tests with the code (start separate repo to adopt), use stable selectors like data-test-id, retries diagnose failures but do not hide flakiness, and Cypress gets practical attention for debugging/maintenance. If those specific practices and tradeoffs are what matters, watch it.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:19Answers to Your Questions About Testing
- 2:10What is a test?
- 4:35Where should the test live?
- 6:02How long should a test be?
- 6:30E Tests Should Be Meaningful
- 7:16The test is too long
- 9:44When should you run your
- 12:17What are the signs of a bad test?
- 13:47Do you have confidence in your tests?
- 15:09Should you retry your tests on failure?
- 17:02How do you pick a test runner
- 17:37Testing Tools Effort Simulator
- 19:26The Testing Matrix Helps refine the testing strategy through iteration
- 20:01How do you push for more testing?
related talks
35mCypress Tales: Effective E2E Testing
29mEnd-to-end Testing Is Hard - But It Doesn't Have to Be
41mEnd-2-end testing without the pain
26mSpeed Up Your End-to-End Tests with Cypress
30mEnd to End Testing: The Game Has Changed
32mCypress.io – the State of the Art End-to-end Testing Tool
47mEnd to End Testing with Cypress
43mLessons from E2E Testing Web Applications with Avindra Fernando