From generic to specific test automation architecture with Playwright
summary
Shows a concrete recipe: map the gTAA layers to Playwright’s code generator for bootstrapping, a refactored Test Definition as reusable helpers and locators, Test Execution via Playwright runner integrated with GitHub Actions and the HTML reporter, plus extra logging with Winston. Demonstrates using stable test ID locators, parallel runs, timeout sync between runner and CI, and examples of what was built and works rather than vague architecture theory.
AI-written summary · about
chapters (10)
- 0:00Playwright test automation intro
- 1:11Why architecture matters
- 2:16Generic test automation
- 4:27Test generation with Playwright
- 6:58Test definition and code
- 9:29Test execution with GitHub Actions
- 11:15Playwright reporting tools
- 14:50Test adaptation layer
- 16:40Four-layer architecture recap
- 17:45Q&A
related talks
14mAdvanced Playwright Techniques for flawless testing
42mMichal Slezak: Creating a Framework with Playwright - How to Do It Right?
10mCreate, Run and Deploy end-to-end tests with Playwright and GitHub Actions
01h 31mAdvanced Playwright with AI
29mPlaying your tests wright
41mTesting Web Applications with Playwright
51mAdvanced Playwright Techniques for Flawless Testing
49mReal World Lessons from Scaling Test Automation