A witches guide to testing
summary
A haunted webshop story shows concrete failures: a cart bug that drops quantity, a performance regression and distracting animations. The cure is layered testing: unit testing with Jest/Jasmine/Mocha to catch function/component regressions fast, integration testing (mocking backend) to verify add‑to‑cart calls between components, and end-to-end testing with Cypress/Puppeteer against a test environment to validate checkout across services. Test‑first (red/green/refactor) and the testing pyramid guide how many and which tests to run; tests reduce debugging time and give deploy confidence.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:19WE NEED PROTECTION
- 4:21Unit Test Spell - Casting
- 7:27Functional Test Spell - Incantation building blocks
- 8:48Integration Test Spell - Casting
- 9:36Integration Test Incantation
- 12:33Functional Test Spell - Casling
- 14:02Why use those spells?
- 15:38How many spells should I performa
- 16:29Testing pyramid - the ultimate truth?
- 17:42Implementation first
- 20:26Test driven development - WHY??
related talks
26mModern Testing Practices in Frontend Applications
23mIt's a Testing Trap
39mTesting, Testing, 1, 2, NaN
35mTesting in Frontend World
30mIt's a (testing) trap! - Common end-to-end pitfalls and how to solve them
42mSurviving the JS Testing Tools Jungle
40mFrontend testing for Wix viewer, case study
16mA unit test walks into a bar