How to Stop Hating Tests with Jest, Supertest and Cypress
summary
Shows a concrete setup: Jest + Supertest for backend by exporting the app and hitting endpoints without running a separate server, plus Cypress for browser E2E with real-network tests or stubbed fixtures, screenshots and recorded videos. Demonstrates using mocks, snapshots and coverage to catch API contract changes, a zipcode autofill test that stubs the address response, and practical rules: one assertion per test, arrange-act-assert, readable tests and CI-friendly configs.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:13Why do you hate testing?
- 6:29Tests can do 3 things
- 7:46Common problems
- 19:07End to end tests in the back end? how?
- 19:41You can test your endpoints
- 26:20DON'T Stub The Response
- 28:18Stub Response
- 34:20Write clean test code
related talks
23mIt's a Testing Trap
39mTesting, Testing, 1, 2, NaN
19mWhy you should Jest use Cypress for React component testing
23mGaining Confidence with Cypress Tests
39mGaining Confidence with Cypress Tests
01h 02mWriting better tests for your JavaScript app
35mCypress Tales: Effective E2E Testing
15mCypress Component Testing - Lightning talk