When Should You Use Page Object Model?

POM becomes particularly useful when your automation project starts growing.

Contents

Consider using POM when:

If you have only two or three small tests, POM may feel unnecessary.

But when you have dozens or hundreds of tests, maintaining repeated locators becomes harder.

For example, if many tests interact with:

Login Page
Checkout Page
User Profile Page

creating page objects can help centralize the common interactions.

If the same locator appears across multiple test files, it may be a good candidate for a page object.

For applications with many modules and workflows, POM can provide a clear structure.

For example:

pages/
    LoginPage.ts
    DashboardPage.ts
    UserPage.ts
    ProductPage.ts
    CartPage.ts
    PaymentPage.ts

A consistent structure becomes more valuable when several people contribute to the automation project.

When Should You NOT Use POM?

POM is useful, but it doesn’t mean you must use it for every single test.

For a very small automation project, creating many classes can add unnecessary complexity.

For example, if you have one simple test:

test('Open homepage', async ({ page }) => {
    await page.goto('https://example.com');
});

Creating a separate page object just for this may not provide much value.

The goal is not:

“Use POM everywhere.”

The goal is:

“Use POM where it makes the automation easier to maintain.”