One Step at a Time
summary
Starts with a recorded Selenium IDE export and shows concrete refactors: move the export into WebDriver, add a getUniqueEmail helper so repeated runs succeed, then replace raw locators with page objects, lift orchestration into a registration workflow, model input as domain objects, and keep assertions and DB checks in dedicated asserters. Also adds randomized input (RFC‑compliant emails uncovered a regex bug) and CI execution infrastructure so tests actually run and remain maintainable.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:25Test automation evolution
- 3:31Selenium IDE to WebDriver
- 7:05Refactoring scripts
- 10:40Decoupling tests
- 12:46Page Object Model
- 15:13Overloaded Page Objects
- 17:00Workflow layer
- 18:45Domain Objects
- 21:11Behavior in Domain Objects
- 23:43Continuous refactoring and brainstorming
- 24:46Execution infrastructure
- 25:50Data generation
- 27:59Overloaded layers
- 28:46Q&A
related talks
40mSelenium and the Four Rules of Simple Design
51mAutomating to augment testing
39mSelenium and the Four Rules of Simple Design
17mSurviving Growing from Zero to 15,000 Selenium Tests
01h 14mContinuous Testing
38mFreeing up Selenium
29mUsing Selenium and Cucumber to test a healthcare information system
32mAll about web application testing