The Page Object Model wraps each page (or component) in a class that exposes intent-revealing methods (login(user, pass)) and hides locators and waits. Rule Why Tests contain no locators UI changes are fixed in one place Page methods return the next page object fluent, readable flows No assertions inside page objects (mostly) keep pages reusable; assert in tests Components for repeated widgets (header, cart drawer) avoid duplication Waits live inside page methods tests read like user stories A BasePage can hold the driver, a shared WebDriverWait and helpers like click(By) and type(By, text).
Key Takeaways
Keep locators and waits inside page objects, never in tests.
Page methods express user intent and return the next page.
Put assertions in tests so page objects stay reusable.