Why patterns scale test suites in Cypress - Automation Benefits in Action

Verify login functionality using Page Object pattern

Preconditions (1)

Step 1: Enter '[e-mail]' in the email input field

Step 2: Enter 'Password123' in the password input field

Step 3: Click the login button

Step 4: Verify that the URL changes to the dashboard page

Step 5: Verify that the dashboard heading is visible

✅ Expected Result: User is successfully logged in and redirected to the dashboard page with the dashboard heading visible

Automation Requirements - Cypress

Assertions Needed:

URL contains '/dashboard'

Dashboard heading is visible

Best Practices:

Use Page Object pattern to separate selectors and actions

Use Cypress commands for actions and assertions

Use explicit assertions to verify outcomes

Avoid hardcoding selectors in test files

Automated Solution

Cypress

/// <reference types="cypress" />

// cypress/support/pageObjects/LoginPage.js
export class LoginPage {
  emailInput() {
    return cy.get('#email');
  }

  passwordInput() {
    return cy.get('#password');
  }

  loginButton() {
    return cy.get('button[type="submit"]');
  }

  visit() {
    cy.visit('/login');
  }

  login(email, password) {
    this.emailInput().clear().type(email);
    this.passwordInput().clear().type(password);
    this.loginButton().click();
  }
}

// cypress/support/pageObjects/DashboardPage.js
export class DashboardPage {
  heading() {
    return cy.get('h1').contains('Dashboard');
  }
}

// cypress/e2e/login.spec.js
import { LoginPage } from '../support/pageObjects/LoginPage';
import { DashboardPage } from '../support/pageObjects/DashboardPage';

describe('Login Test Suite', () => {
  const loginPage = new LoginPage();
  const dashboardPage = new DashboardPage();

  it('should login successfully and show dashboard', () => {
    loginPage.visit();
    loginPage.login('[e-mail]', 'Password123');

    cy.url().should('include', '/dashboard');
    dashboardPage.heading().should('be.visible');
  });
});

This test uses the Page Object pattern to keep selectors and actions organized in separate classes. LoginPage handles all login page elements and actions, while DashboardPage handles dashboard elements.

The test visits the login page, performs login with given credentials, then asserts the URL contains '/dashboard' and the dashboard heading is visible. This separation makes the test easier to maintain and scale as the application grows.

Using Cypress commands ensures reliable interaction and assertions. Selectors are stored in page objects to avoid duplication and make updates easier.

Common Mistakes - 3 Pitfalls

Hardcoding selectors directly in test files

Not using assertions after actions

Using fixed waits like cy.wait(5000)

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials

Show Hint

Practice

1. Why do patterns help when you have many tests in a Cypress test suite?

easy

A. They make tests run slower but more detailed.

B. They keep tests organized and easier to maintain.

C. They remove the need for assertions in tests.

D. They force tests to use only one browser.

Solution

1. Step 1: Understand test suite growth

   As test suites grow, managing many tests becomes harder without structure.

2. Step 2: Role of patterns in organization

   Patterns provide a clear structure, making tests easier to read and update.

3. Final Answer:

   They keep tests organized and easier to maintain. -> Option B

4. Quick Check:

   Patterns = organization and maintainability [OK]

Hint: Patterns organize tests for easier maintenance [OK]

Common Mistakes:

• Thinking patterns slow down tests
• Believing patterns remove assertions
• Assuming patterns limit browser choice

2. Which of the following is the correct way to reuse code in Cypress tests using patterns?

easy

A. Write all test steps inside one big test.

B. Copy and paste the same code in every test.

C. Create custom commands or functions to reuse code.

D. Avoid using functions to keep tests simple.

Solution

1. Step 1: Identify code reuse methods

   Copy-pasting repeats code and causes errors; functions/custom commands avoid this.

2. Step 2: Use Cypress features for reuse

   Cypress supports custom commands and helper functions to reuse code cleanly.

3. Final Answer:

   Create custom commands or functions to reuse code. -> Option C

4. Quick Check:

   Code reuse = custom commands/functions [OK]

Hint: Use custom commands to reuse code in Cypress [OK]

Common Mistakes:

• Copy-pasting code instead of reusing
• Writing one large test instead of small ones
• Avoiding functions thinking they complicate tests

3. Given this Cypress test snippet using a pattern:

cy.get('.btn').click()
cy.get('.input').type('hello')
cy.get('.btn').click()

What is a benefit of using a pattern to avoid repeating cy.get('.btn').click() twice?

medium

A. It reduces code duplication and makes maintenance easier.

B. It hides errors from the test report.

C. It causes the test to fail because of missing clicks.

D. It makes the test run twice as slow.

Solution

1. Step 1: Identify repeated code

   The command cy.get('.btn').click() appears twice, repeating code.

2. Step 2: Understand pattern benefits

   Using a pattern like a helper function avoids repetition, easing updates and reducing mistakes.

3. Final Answer:

   It reduces code duplication and makes maintenance easier. -> Option A

4. Quick Check:

   Patterns reduce duplication = easier maintenance [OK]

Hint: Patterns reduce repeated code for easier fixes [OK]

Common Mistakes:

• Thinking patterns slow tests
• Believing patterns hide errors
• Assuming repeated code is harmless

4. You have this Cypress test code with a pattern:

function clickButton() {
  cy.get('.btn').click()
}

clickButton()
clickButton()

But the test fails because the button is disabled after the first click. What is the best fix using patterns?

medium

A. Remove the second call to clickButton().

B. Add a wait between clicks to let the button enable again.

C. Ignore the error and keep the code as is.

D. Change the pattern to check if the button is enabled before clicking.

Solution

1. Step 1: Identify the problem with the pattern

   The pattern blindly clicks the button twice, but the button disables after first click.

2. Step 2: Improve the pattern for reliability

   Modify the pattern to check if the button is enabled before clicking to avoid errors.

3. Final Answer:

   Change the pattern to check if the button is enabled before clicking. -> Option D

4. Quick Check:

   Pattern fix = add condition check before action [OK]

Hint: Add checks in patterns to avoid disabled element errors [OK]

Common Mistakes:

• Removing needed test steps
• Using fixed waits causing flaky tests
• Ignoring errors instead of fixing patterns

5. You want to scale your Cypress test suite for a large app. Which pattern combination best helps keep tests fast, maintainable, and easy to update?

hard

A. Use page objects for selectors, custom commands for repeated actions, and fixtures for test data.

B. Write all tests in one file with repeated code for clarity.

C. Avoid using custom commands to keep tests simple and short.

D. Use only inline selectors and no helper functions.

Solution

1. Step 1: Identify patterns for scaling

   Page objects organize selectors, custom commands reuse actions, fixtures manage test data cleanly.

2. Step 2: Understand benefits of combining patterns

   Combining these patterns reduces duplication, improves readability, and speeds up maintenance.

3. Final Answer:

   Use page objects for selectors, custom commands for repeated actions, and fixtures for test data. -> Option A

4. Quick Check:

   Combine patterns = faster, maintainable tests [OK]

Hint: Combine page objects, commands, fixtures for scalable tests [OK]

Common Mistakes:

• Putting all tests in one file
• Avoiding helpers thinking they add complexity
• Using only inline selectors causing duplication