lecture 4 of 160 completed

The Page Object Model

Selenium teams live or die by this pattern. It keeps locators in one place so a UI change is one edit.

What you'll learn

  • Why repeated locators make one UI change expensive
  • How to keep locators in one place
  • Why page objects should not assert

These lines appear in eight different test files:

full course

Keep reading with the full course

The Foundations track and the first lessons in each framework are free. This lesson needs full course access. A course plan includes all lessons for Playwright, Cypress and Selenium.

See course plans →