Page Object Model concept in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Page Object Model (POM) in software testing?

POM is a design pattern that creates an object for each page of the application. It helps organize code by keeping page elements and actions in one place, making tests easier to read and maintain.

beginner

Why use the Page Object Model in test automation?

It reduces code duplication, improves test maintenance, and makes tests more readable by separating page structure from test logic.

beginner

In POM, where do you store locators and page actions?

Locators and page actions are stored inside the page object class representing that page. Tests call these methods instead of directly accessing elements.

intermediate

How does POM help when the UI changes?

Since locators are in one place (the page object), you only update them there. Tests don’t need changes, saving time and reducing errors.

beginner

Give a simple example of a page object method.

For a login page, a method could be login(username, password) that fills fields and clicks the login button. Tests call this method to perform login.

What does the Page Object Model primarily help with?

A Creating database schemas

B Writing UI code

C Organizing test code by page

D Designing user interfaces

POM organizes test code by creating objects for each page, making tests easier to manage.

Where are locators stored in the Page Object Model?

A Inside the test scripts

B In the UI code

C In the database

D In the page object class

Locators are stored inside the page object class to keep them centralized.

How does POM improve test maintenance?

A By separating page details from tests

B By duplicating code

C By mixing UI and test code

D By removing all locators

POM separates page details from test logic, so changes affect only page objects.

If a button’s locator changes, what do you update in POM?

A The page object only

B The UI code

C All test scripts

D The database

Only the page object needs updating, not all tests.

Which of these is a good practice in POM?

A Writing locators inside test cases

B Creating methods for page actions

C Mixing test logic with UI code

D Avoiding page objects

Creating methods for page actions keeps tests clean and reusable.

Explain the Page Object Model and its benefits in your own words.

Think about how you organize things in folders to keep your desk tidy.

Describe how you would update tests if a page button’s locator changes when using POM.

Imagine changing a phone number in one contact card instead of telling everyone separately.