Design Decisions for Perfect JavaScript Testing Framework
summary
Recommends WebdriverIO as the practical Selenium implementation with good docs and page‑object support, labels Protractor and Nightwatch as legacy/problematic, and calls out Cypress as fast and newcomer‑friendly but limited (no XPath, no file upload/download, no multi‑tab/iframe, not true cross‑browser). Praises Puppeteer for Chrome/Firefox with full DevTools control and roughly three times the speed of Selenium, and presents TestCafe as a fast, cross‑browser inside‑browser alternative; suggests choosing by explicit requirements and upgrade story.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:55What Should We Choose for Testing Our Web Applications
- 2:48Why Would You Choose Javascript
- 6:38Browser Test Automation
- 7:23Browser Driver
- 7:48How the Tests Will Be Executed
- 13:27Selenium-Webdriver
- 16:07Testing Framework Nightwatch
- 22:05Limitation and the Principles behind Cypress
- 31:16Requirements for Test Automation
- 34:00Control Flow
- 34:59Sync Mode
- 36:00Cucumber
- 40:06Final Thoughts
related talks
41mDesign Decisions for the Perfect JS Testing Framework
35mDesign Decisions for the Perfect JS Testing Framework
38mModern Web Testing: Going Beyond Selenium
18mModern Solutions for e2e testing
55mModern Web Testing: Going Beyond Selenium
53mModern Web Testing: Going Beyond Selenium
09mPros and cons of UI testing tools
36mModern Web Testing: Going Beyond Selenium
