Should you use the page object model in Cypress?

The page object model wraps a page's selectors and actions in a class or module. It originated with remote-driver frameworks where direct DOM access was expensive. Cypress can query the DOM directly and retries assertions, so the original motivation is weaker, but the readability benefit can remain for large pages.

export const loginPage = {
  visit() {
    cy.visit("/login");
  },
  fill(email: string, password: string) {
    cy.get("[data-cy=email]").type(email);
    cy.get("[data-cy=password]").type(password);
  },
  submit() {
    cy.get("[data-cy=submit]").click();
  },
};

loginPage.visit();
loginPage.fill("asha@example.com", "secret123");
loginPage.submit();
cy.location("pathname").should("eq", "/dashboard");

Cypress-friendly alternatives

• App actions: call the API or set state directly instead of clicking through setup UI
• Small helper functions that return a chain
• Custom commands for repeated user intent
• Page objects focused on actions and selectors, not on assertions
• A shared fixture or factory for test data

The main risk is a page object that asserts internally and returns nothing. When it fails, the test body does not show what was expected, and the object becomes a second test suite. Keep assertions in the spec, or expose a clear, named action that the spec can assert around.