Chapter Summary

What You Learned

• POM separates locators and page logic from test logic. One UI change = one file update.
• BasePage provides common methods (click, type, getText, waits) that all pages inherit.
• Each page has private locators and public action methods. Tests never see By locators.
• Action methods return the next page object for fluent navigation. Return "this" when staying on the same page.
• Use composition for shared components (header, sidebar) — not inheritance.
• Never put assertions in page objects. Page objects provide state, tests make assertions.
• Prefer By-based POM over PageFactory. PageFactory caches elements and breaks on dynamic pages.
• Handle dynamic elements with parameterized methods that build locators at runtime.
• Project structure: base/ → pages/ → components/ → tests/ → utils/ → resources/.
• Tests become readable, maintainable, and scale to hundreds of test cases.

POM is the foundation of every professional automation framework. Everything we build from here — data-driven testing, complete test suites, CI/CD integration — uses POM as the base. If you only learn one design pattern for automation, make it POM.