Design Decisions for the Perfect JS Testing Framework

on YouTube ↗35m

" summary

Compares JavaScript end-to-end testing options and the design tradeoffs when building a testing framework: use WebDriver for cross‑browser standardization, Puppeteer/Playwright for Chrome DevTools and raw browser APIs, Cypress for fast in‑frame developer testing with iframe/domain limitations, and TestCafe for proxy‑based cross‑browser runs and simple startup. Also covers architectural choices like async model (promise chains vs async/await), separating low‑level browser control from high‑level tests, and the likelihood of painful rewrites when drivers break or major upgrades change APIs.

AI-written summary · about

" chapters (16)

1. 0:00Introduction
2. 3:06JavaScript for testing
3. 5:37Test framework structure
4. 7:28Browser drivers overview
5. 9:58Protractor success
6. 11:43Selenium reliability
7. 13:09Playwright control
8. 16:42DevTools Protocol
9. 19:37TestCafe cross-browser
10. 21:24Async test flow
11. 23:11Driver pros/cons
12. 25:38Cucumber myths vs reality
13. 27:05Strategic test design
14. 28:52Separate test logic
15. 31:41Tool selection guide
16. 33:06Q&A

" related talks

• 41mDesign Decisions for the Perfect JS Testing FrameworkMichael Bodnarchuk · DelEx Conf 2019
• 41mDesign Decisions for Perfect JavaScript Testing FrameworkMichael Bodnarchuk · TestCon Europe 2019
• 38mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · Voxxed Days Frontend Bucharest 2019
• 18mModern Solutions for e2e testingAnastasiia Dragich · Frontend Love 2020
• 36mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · TestCon Vilnius 2018
• 55mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · NDC Minnesota 2019
• 53mModern Web Testing: Going Beyond SeleniumDmitry Vinnik · GeeCON 2019
• 42mSurviving the JS Testing Tools JungleLise Quesnel · Devfest Strasbourg 2023