Page Object Model in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test using Page Object Model?

Given the following Page Object and test code, what will be the test result?

Cypress

class LoginPage {
  visit() {
    cy.visit('/login')
  }
  fillUsername(name) {
    cy.get('#username').type(name)
  }
  fillPassword(pass) {
    cy.get('#password').type(pass)
  }
  submit() {
    cy.get('button[type=submit]').click()
  }
}

describe('Login Test', () => {
  it('logs in with valid credentials', () => {
    const login = new LoginPage()
    login.visit()
    login.fillUsername('user1')
    login.fillPassword('pass1')
    login.submit()
    cy.url().should('include', '/dashboard')
  })
})

A Test fails because cy.url() assertion is missing parentheses and throws a syntax error.

B Test fails because the selector '#username' is invalid and causes a timeout error.

C Test fails because the submit button selector is incorrect and click() does nothing.

D Test passes because the Page Object methods correctly interact with the page elements and URL assertion matches after login.

💡 Hint

Check if the selectors match typical HTML input IDs and if the assertion syntax is correct.

The Page Object methods use valid selectors and Cypress commands. The test visits the login page, fills username and password, clicks submit, and asserts the URL includes '/dashboard'. This matches expected behavior, so the test passes.

❓ locator

intermediate

Which locator is best practice for Page Object Model in Cypress?

Choose the best locator strategy for selecting a login button in a Page Object class.

A cy.get('button#loginBtn')

B cy.get('button').contains('Login')

C cy.get('[data-cy=login-button]')

D cy.get('button:nth-child(3)')

💡 Hint

Consider maintainability and stability of selectors when the UI changes.

Using a custom data attribute like data-cy is best practice because it is stable and does not depend on styling or text changes. IDs can change, text can vary, and nth-child is fragile.

❓ assertion

advanced

Which assertion correctly verifies a success message after login?

Given a Page Object method that returns the success message element, which assertion is correct?

Cypress

class DashboardPage {
  getSuccessMessage() {
    return cy.get('.success-msg')
  }
}

const dashboard = new DashboardPage()
dashboard.getSuccessMessage()

A dashboard.getSuccessMessage().should('have.text', 'Login successful')

B dashboard.getSuccessMessage().should('contain.text', 'Login successful')

C dashboard.getSuccessMessage().should('include.text', 'Login successful')

D dashboard.getSuccessMessage().should('contain', 'Login successful')

💡 Hint

Check Cypress assertion syntax for partial text matching.

contain.text checks if the element's text includes the given substring. have.text requires exact match. include.text is invalid syntax. contain works but is less specific than contain.text.

🔧 Debug

advanced

Why does this Page Object test fail with 'Timed out retrying' error?

Analyze the code and identify the cause of the failure.

Cypress

class ProfilePage {
  getSaveButton() {
    return cy.get('.btn-save')
  }
}

describe('Profile update', () => {
  it('saves profile changes', () => {
    const profile = new ProfilePage()
    profile.getSaveButton().click()
    cy.contains('Profile saved').should('be.visible')
  })
})

A The selector '.btn-save' does not exist on the page, causing cy.get() to time out.

B The click() command is missing parentheses, so the button is not clicked.

C The cy.contains() command is used incorrectly and should be cy.get().contains().

D The assertion 'should(be.visible)' is missing quotes around 'be.visible'.

💡 Hint

Check if the element targeted by the selector is present on the page.

If the selector '.btn-save' does not match any element, Cypress will retry until timeout. The other options have correct syntax: click() is called properly, 'be.visible' is quoted, and cy.contains() is valid.

❓ framework

expert

How to implement reusable login with Page Object Model in Cypress for multiple tests?

You want to reuse login steps across many tests using Page Object Model. Which approach is best?

A Create a LoginPage class with login() method and call it inside a beforeEach() hook in test files.

B Write login steps directly inside each test without Page Object to avoid abstraction overhead.

C Use Cypress commands (Cypress.Commands.add) to define login globally and call it in tests without Page Object.

D Create a separate login.spec.js test and run it before other tests to ensure login is done.

💡 Hint

Think about maintainability and reusability with Page Object Model and Cypress hooks.

Using a LoginPage class with a login() method encapsulates login steps. Calling it in beforeEach() ensures login runs before each test, promoting reuse and clarity. Writing login steps in each test duplicates code. Cypress commands are useful but separate from Page Object. Running a separate login test does not share state.

Practice

1. What is the main purpose of using the Page Object Model in Cypress testing?

easy

A. To write tests without any assertions

B. To avoid using selectors in tests

C. To speed up the browser loading time

D. To organize page interactions into reusable classes

Solution

1. Step 1: Understand the role of Page Object Model

   The Page Object Model (POM) organizes web page elements and actions into classes to reuse code easily.

2. Step 2: Identify the main benefit in Cypress tests

   Using POM makes tests easier to write, read, and maintain by grouping page logic separately from test logic.

3. Final Answer:

   To organize page interactions into reusable classes -> Option D

4. Quick Check:

   Page Object Model = reusable page classes [OK]

Hint: POM groups page actions into classes for reuse [OK]

Common Mistakes:

• Thinking POM speeds up browser loading
• Believing POM removes need for assertions
• Assuming POM avoids selectors entirely

2. Which of the following is the correct way to define a method inside a Cypress Page Object class to click a button with selector button.submit?

easy

A. clickSubmit() { cy.get('button.submit').click(); }

B. clickSubmit() => { cy.get('button.submit').click(); }

C. function clickSubmit() { cy.get('button.submit').click(); }

D. clickSubmit: function() { cy.get('button.submit').click(); }

Solution

1. Step 1: Recognize class method syntax in JavaScript

   Inside a class, methods are defined as methodName() { ... } without the function keyword or arrow syntax.

2. Step 2: Match the correct syntax for Cypress command

   The method should call cy.get('button.submit').click(); inside the method body.

3. Final Answer:

   clickSubmit() { cy.get('button.submit').click(); } -> Option A

4. Quick Check:

   Class method syntax = clickSubmit() { cy.get('button.submit').click(); } [OK]

Hint: Class methods use name() { } syntax, no function keyword [OK]

Common Mistakes:

• Using arrow functions inside class methods incorrectly
• Adding 'function' keyword inside class method
• Using object literal syntax inside class

3. Given this Page Object class snippet:

class LoginPage {
  visit() {
    cy.visit('/login')
  }
  enterUsername(name) {
    cy.get('#username').type(name)
  }
  enterPassword(pass) {
    cy.get('#password').type(pass)
  }
  submit() {
    cy.get('button[type=submit]').click()
  }
}

What will happen when the test calls:
const page = new LoginPage(); page.visit(); page.enterUsername('user1'); page.enterPassword('pass1'); page.submit();

medium

A. The login page loads, username and password are typed, and submit button is clicked

B. Only the login page loads, but no typing or clicking happens

C. Syntax error because methods are not async

D. The test fails because selectors are incorrect

Solution

1. Step 1: Analyze method calls in sequence

   The test creates a LoginPage object and calls methods to visit the page, type username and password, then click submit.

2. Step 2: Confirm Cypress commands are correct

   Selectors like #username, #password, and button[type=submit] are valid and commands are chained properly.

3. Final Answer:

   The login page loads, username and password are typed, and submit button is clicked -> Option A

4. Quick Check:

   Method calls execute Cypress commands in order [OK]

Hint: Methods run Cypress commands sequentially as called [OK]

Common Mistakes:

• Thinking Cypress commands need async/await
• Assuming selectors are invalid without checking
• Believing only visit() runs without chaining

4. You have this Page Object method:

login(username, password) {
  cy.get('#user').type(username)
  cy.get('#pass').type(password)
  cy.get('button.login').click()
}

But your test calls cy.visit('/login') before login(), yet fails because the username input is not found. What is the likely problem?

medium

A. The click() command must come before typing

B. The selector #user is incorrect or outdated

C. The method should use cy.find() instead of cy.get()

D. You forgot to call cy.visit() before login

Solution

1. Step 1: Identify cause of element not found error

   If the username input is not found, the selector #user might be wrong or changed on the page.

2. Step 2: Evaluate other options

   While missing cy.visit() can cause failure, the question states the failure is specifically about the username input not found, pointing to selector issue.

3. Final Answer:

   The selector #user is incorrect or outdated -> Option B

4. Quick Check:

   Element not found = wrong selector [OK]

Hint: Element not found usually means wrong selector [OK]

Common Mistakes:

• Assuming cy.find() fixes selector issues
• Thinking click() must come before typing
• Ignoring the need to visit page first

5. You want to create a Page Object for a form with multiple input fields and a submit button. Which approach best follows Cypress Page Object Model best practices?

hard

A. Use global variables for selectors and call Cypress commands directly in tests

B. Write all test steps directly inside the test without any class or methods

C. Create a class with methods for each field interaction and a submit method, using clear selectors

D. Create one method that types all fields and clicks submit without separate methods

Solution

1. Step 1: Understand POM best practices

   Best practice is to create a class that groups page elements and actions into clear, reusable methods with good selectors.

2. Step 2: Compare options

   Writing all steps in tests or using global variables reduces reusability and clarity. One big method reduces flexibility and readability.

3. Final Answer:

   Create a class with methods for each field interaction and a submit method, using clear selectors -> Option C

4. Quick Check:

   Clear methods + selectors = POM best practice [OK]

Hint: Use classes with clear methods for each page action [OK]

Common Mistakes:

• Putting all steps directly in tests
• Using global selectors without encapsulation
• Combining all actions into one big method