Page Object Model — Top 10 Q&A

A: POM is a design pattern where each web page is represented by a Java class. The class has private locators and public action methods. Why: (1) Maintainability — locator changes in one place, not across 50 test files. If the login button id changes from "login" to "signin", I update one file: LoginPage.java. (2) Readability — tests read like user stories: loginPage.enterUsername("admin"); loginPage.clickLogin(); dashboardPage.verifyWelcomeMessage("Hello Admin"). (3) Reusability — loginPage.login("admin", "pass") is called from 20 different tests. (4) Separation of concerns — test logic (what to test) is separate from page interaction (how to interact). In my framework, I have page objects for every page: LoginPage, DashboardPage, TransferPage, CartPage. Each constructor accepts WebDriver and calls super(driver) to initialize the BasePage.

A: BasePage is the parent class of all page objects. It holds the WebDriver and WebDriverWait instances and provides common interaction methods that all pages need. My BasePage contains: (1) Constructor that accepts WebDriver and initializes WebDriverWait. (2) waitForVisible(By locator) — returns WebElement after it is visible. (3) waitForClickable(By locator) — waits and clicks. (4) type(By locator, String text) — clears the field and types. (5) getText(By locator) — waits and returns text. (6) isDisplayed(By locator) — returns boolean without throwing exception. (7) scrollToElement(WebElement element) — scrolls to center of viewport. (8) Abstract method isPageLoaded() — each page must implement this. Why this matters: every page object inherits these methods, so I never duplicate wait logic. If I need to change how clicking works (add logging, add retry), I change it once in BasePage.

A: Page Factory uses @FindBy annotation and PageFactory.initElements(): @FindBy(id = "username") private WebElement usernameField; initialized in constructor with PageFactory.initElements(driver, this). By locators use driver.findElement() inside methods: private By usernameField = By.id("username"); public void enterUsername(String user) { waitForVisible(usernameField).sendKeys(user); }. I prefer By locators because: (1) Page Factory initializes elements eagerly — if the page DOM changes (SPA navigation, AJAX), you get StaleElementReferenceException because the reference is stale. By locators re-find the element fresh every time. (2) By locators work naturally with explicit waits — wait.until(EC.visibilityOfElementLocated(locator)). (3) Easier to debug — you see the locator string in logs. (4) No dependency on PageFactory class. Many modern frameworks have moved away from Page Factory for these reasons.

A: When a page action navigates to a new page, the method returns the new page object. loginPage.clickLogin() returns DashboardPage: public DashboardPage clickLogin() { waitForClickable(loginButton); return new DashboardPage(driver); }. This enables fluent chaining: DashboardPage dashboard = loginPage.enterUsername("admin").enterPassword("pass").clickLogin(). For methods that stay on the same page (like entering text), I return "this": public LoginPage enterUsername(String user) { type(usernameField, user); return this; }. For methods where the outcome is uncertain (login could succeed or fail), I have two methods: clickLoginExpectSuccess() returns DashboardPage, clickLoginExpectError() returns LoginPage. This makes the test code explicit about the expected behavior.

A: Components that appear on multiple pages get their own class — not a full page object, but a component object. I create HeaderComponent with methods like clickLogo(), searchFor(String term), clickCart(), logout(). Then pages that have a header use composition: public class DashboardPage extends BasePage { private HeaderComponent header; public DashboardPage(WebDriver driver) { super(driver); this.header = new HeaderComponent(driver); } public HeaderComponent getHeader() { return header; } }. Usage in tests: dashboardPage.getHeader().searchFor("laptop"). This avoids duplicating header locators and methods in every page object. Same approach for footers, sidebars, and modal dialogs. The key principle: DRY — if the same UI component appears on 5 pages, there should be one component class, not 5 copies of the same locators.

A: Every page object has an isPageLoaded() method that verifies the page identity. My BasePage declares it as abstract, forcing each page to implement it. LoginPage checks for the username field: public boolean isPageLoaded() { return isDisplayed(usernameField); }. DashboardPage checks for the welcome banner. I call this in the constructor: public LoginPage(WebDriver driver) { super(driver); if (!isPageLoaded()) { throw new IllegalStateException("LoginPage did not load. Current URL: " + driver.getCurrentUrl()); } }. This catches navigation errors early — if a test expects to be on the dashboard but the login failed, the exception fires immediately with a clear message instead of a confusing NoSuchElementException three steps later.

A: (1) Putting assertions in page objects — page objects should only interact with the page, not validate test expectations. Assertions belong in test classes. (2) Exposing WebElements publicly — locators must be private. public WebElement loginButton breaks encapsulation. (3) Making page objects too granular or too monolithic — one class per page is the right level, not one class per section or one class for the entire application. (4) Not using a BasePage — leads to duplicated wait logic across every page object. (5) Storing WebElements as instance variables with Page Factory — causes stale references on dynamic pages. (6) Hardcoding waits in page methods — use configurable timeouts from config.properties. (7) Not handling page transitions — methods that navigate should return the target page object.

A: Scenario: the dev team changes the login button from id="login" to id="signin" and moves the error message from a div to a span. Without POM: you would grep through 30+ test files, find every reference to the old id, and update each one. Miss one and the test breaks silently. With POM: open LoginPage.java, change the loginButton locator from By.id("login") to By.id("signin"), and update the errorMessage locator. Done. All 30 tests work immediately because they call loginPage.clickLogin() — they never directly reference the locator. In my project, a major UI redesign changed 40+ locators. With POM, I updated only the page object files (about 12 classes). Zero test classes were modified. That is the power of encapsulation.

A: For tables, I add utility methods to the page object: getRowCount(), getCellText(int row, int col), clickActionInRow(String identifier) which finds a row by text and clicks a button in it. Internally: //table//tr[td[text()="John"]]//button[@class="edit"]. For pagination: method getAllTableData() that clicks next page, collects data from each page, and returns a complete List<Map<String, String>>. For dynamic content (elements that appear after AJAX calls): all methods use explicit waits before interaction, and I add a waitForTableToLoad() method that waits for at least one row to be visible. For infinite scroll: I scroll to the bottom and wait for new elements to appear. The page object encapsulates all this complexity — the test just calls tablePage.getRowByName("John").clickEdit().

A: Yes. LoginPage extends BasePage. Private locators: By usernameField = By.id("username"), By passwordField = By.id("password"), By loginButton = By.id("login-btn"), By errorMessage = By.cssSelector(".error-message"). Constructor: public LoginPage(WebDriver driver) { super(driver); }. Methods: public LoginPage enterUsername(String user) { type(usernameField, user); return this; }. public LoginPage enterPassword(String pass) { type(passwordField, pass); return this; }. public DashboardPage clickLogin() { waitForClickable(loginButton); return new DashboardPage(driver); }. public String getErrorMessage() { return getText(errorMessage); }. Convenience method: public DashboardPage login(String user, String pass) { enterUsername(user); enterPassword(pass); return clickLogin(); }. Test usage: DashboardPage dashboard = new LoginPage(driver).login("admin", "pass123"); assertEquals(dashboard.getWelcomeText(), "Welcome Admin");