This practical, code-first course follows a realistic retail-banking regression suite built with Java, Selenium WebDriver, Cucumber and TestNG. You will see how each major concept maps to a Playwright, TypeScript and playwright-bdd implementation, then walk through side-by-side migrations of real framework patterns.
We begin by examining what a well-built Selenium stack still struggles with: manual synchronization, stale elements, WebDriver round trips, Grid maintenance, limited network visibility, iframes, tabs, downloads and slow repeated logins. You will learn when Playwright is the right move, when a partial migration makes more sense, and when remaining on Selenium is the responsible choice.
The migration walkthrough covers feature files, fixtures, browser lifecycle, Page Objects, step definitions, web-first assertions, form controls, data grids, 3-D Secure frames, new tabs, downloads, uploads, response waits, network stubbing, storageState, workers, CI sharding, reports and trace evidence. It also shows how Selenium and Playwright can coexist during a phased rollout while one Gherkin layer remains the business-facing source of truth.
