Why does building a robust automation framework matter?
summary
Shows a working, reusable automation framework built with Cucumber + Playwright + TypeScript that swaps to Selenium with almost no code change (only init differences) and runs the same feature files and step definitions. Uses Cucumber World to give segregated browser/page context per scenario, JSON host/page/element mappings for portable selectors, and a babel compile step so cucumber.js accepts TypeScript hooks. Proof‑of‑concept compares Cypress, Playwright and Selenium, finds Playwright handles iframes and long forms better and is ~10s faster across 50 tests, and the framework successfully scales across multiple apps.
AI-written summary · about
chapters (17)
- 0:00Start
- 1:58Why Does Automation Framework Architecture Matter
- 2:45The Importance of Proof of Concepting
- 3:42Architecture Discussions
- 13:53Hidden Iframes
- 14:19Support for Safari
- 14:45How Did We Build this Framework Architecture
- 19:41Cucumber Js
- 24:03Global Config
- 24:30Global Variables
- 26:22Page Configs
- 30:55Get Element Function
- 32:35Get Element Text
- 33:39Dynamic Pages
- 34:03Generic Steps
- 36:48Files Folder Structure
- 37:41Key Successes
related talks
46mTest Automation with Selenium, Cypress, and Playwright
16mE2E Test Automation Framework Selection | Comparing with Pros & Cons
20mPlaywright or Selenium? The Modern Approach to UI Test Automation
51mCypress, Playwright or Selenium: choosing the right testing tool
32mWhat framework should I use for web testing?
29mAccelerating Software Quality with Open Source Test Frameworks
08m"Selecting a framework that documents your product"
41mDesign Decisions for the Perfect JS Testing Framework