Why login handling speeds up test suites in Cypress - Automation Benefits in Action

Automate login handling to speed up test suites

Preconditions (2)

Step 1: Visit the login page URL

Step 2: Enter '[e-mail]' in the email input field with id 'email'

Step 3: Enter 'Password123!' in the password input field with id 'password'

Step 4: Click the login button with id 'loginBtn'

Step 5: Verify the URL changes to the dashboard page URL '/dashboard'

Step 6: Verify the dashboard page contains a welcome message with id 'welcomeMsg'

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

Automation Requirements - Cypress

Assertions Needed:

Verify URL is '/dashboard' after login

Verify welcome message is visible on dashboard

Best Practices:

Use custom Cypress command for login to reuse in multiple tests

Avoid UI login in every test by programmatically setting authentication state

Use explicit assertions to confirm login success

Keep selectors stable and meaningful (ids preferred)

Automated Solution

Cypress

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

// cypress/support/commands.js
Cypress.Commands.add('login', (email, password) => {
  cy.visit('/login');
  cy.get('#email').clear().type(email);
  cy.get('#password').clear().type(password);
  cy.get('#loginBtn').click();
  cy.url().should('include', '/dashboard');
  cy.get('#welcomeMsg').should('be.visible');
});

// cypress/e2e/login_spec.cy.js

describe('Login Handling Speeds Up Test Suites', () => {
  beforeEach(() => {
    cy.login('[e-mail]', 'Password123!');
  });

  it('should show dashboard after login', () => {
    cy.url().should('include', '/dashboard');
    cy.get('#welcomeMsg').should('contain.text', 'Welcome');
  });

  it('should allow access to protected page without UI login again', () => {
    cy.visit('/protected-page');
    cy.url().should('include', '/protected-page');
    cy.get('h1').should('contain.text', 'Protected Content');
  });
});

This solution uses Cypress to automate login handling.

First, a custom command cy.login is created in commands.js. It visits the login page, fills in email and password fields, clicks login, and asserts the URL and welcome message to confirm success.

Then, in the test file, beforeEach calls cy.login to perform login once before each test. This avoids repeating UI login steps in every test, speeding up the suite.

The tests verify the dashboard URL and welcome message, and also check access to a protected page without logging in again.

Using a custom command and assertions ensures code reuse, readability, and reliable verification of login success.

Common Mistakes - 4 Pitfalls

Hardcoding selectors that are unstable or change frequently

Performing UI login in every test instead of reusing login state

Not asserting login success explicitly

Using arbitrary waits like cy.wait(5000) instead of proper assertions

Bonus Challenge

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

Show Hint

Practice

1. Why does handling login with cy.session() speed up Cypress test suites?

easy

A. Because it skips all tests except login tests

B. Because it runs login steps twice to ensure reliability

C. Because it caches the login state and avoids repeating login steps in every test

D. Because it disables authentication for faster tests

Solution

1. Step 1: Understand what cy.session() does

   cy.session() caches the login session so Cypress does not need to perform login steps repeatedly.

2. Step 2: Identify the effect on test speed

   By caching login, tests skip slow login steps, making the suite run faster overall.

3. Final Answer:

   Because it caches the login state and avoids repeating login steps in every test -> Option C

4. Quick Check:

   Login caching = faster tests [OK]

Hint: Login caching skips repeated steps for speed [OK]

Common Mistakes:

• Thinking login steps are skipped entirely
• Believing login runs twice for reliability
• Assuming authentication is disabled

2. Which is the correct syntax to cache a login session in Cypress?

easy

A. cy.saveSession('user', () => { cy.visit('/login') })

B. cy.cacheSession('user', () => { cy.visit('/login') })

C. cy.loginCache('user', () => { cy.visit('/login') })

D. cy.session('user', () => { cy.visit('/login') })

Solution

1. Step 1: Recall Cypress API for session caching

   The correct Cypress command to cache sessions is cy.session().

2. Step 2: Match syntax with options

   Only cy.session('user', () => { cy.visit('/login') }) uses cy.session() correctly with a session name and callback.

3. Final Answer:

   cy.session('user', () => { cy.visit('/login') }) -> Option D

4. Quick Check:

   Correct command is cy.session() [OK]

Hint: Remember exact Cypress command: cy.session() [OK]

Common Mistakes:

• Using non-existent commands like cy.cacheSession()
• Confusing session caching with login commands
• Misspelling the method name

3. Given this Cypress test code, what will be the effect on test suite speed?

beforeEach(() => {
  cy.session('user', () => {
    cy.visit('/login')
    cy.get('#username').type('user')
    cy.get('#password').type('pass')
    cy.get('button[type=submit]').click()
  })
})

it('checks dashboard', () => {
  cy.visit('/dashboard')
  cy.contains('Welcome')
})

medium

A. The login steps run only once, speeding up all tests

B. The login steps run before every test, slowing down the suite

C. The login steps are skipped, causing test failures

D. The login steps run twice per test for safety

Solution

1. Step 1: Understand cy.session() behavior in beforeEach

   cy.session() caches the login session so the login steps run only once, even if called in beforeEach.

2. Step 2: Analyze impact on test speed

   Because login runs once, subsequent tests reuse the session, speeding up the suite.

3. Final Answer:

   The login steps run only once, speeding up all tests -> Option A

4. Quick Check:

   cy.session() caches login = faster tests [OK]

Hint: cy.session() runs login once, not every test [OK]

Common Mistakes:

• Assuming login runs before every test
• Thinking login steps are skipped entirely
• Believing login runs multiple times per test

4. You wrote this Cypress code to cache login but tests still run login steps every time:

beforeEach(() => {
  cy.session('user', () => {
    cy.visit('/login')
    cy.get('#username').type('user')
    cy.get('#password').type('pass')
    cy.get('button[type=submit]').click()
  })
})

What is the likely mistake?

medium

A. Using cy.session inside beforeEach instead of before

B. Not returning a value or promise inside the cy.session callback

C. Missing cy.clearCookies() before cy.session

D. Not calling cy.login() instead of cy.session()

Solution

1. Step 1: Check cy.session() callback requirements

   The callback must return a Cypress chainable or promise to signal completion for caching.

2. Step 2: Identify why login runs every time

   If the callback does not return, Cypress cannot cache the session, so login runs every test.

3. Final Answer:

   Not returning a value or promise inside the cy.session callback -> Option B

4. Quick Check:

   Return chainable in cy.session callback [OK]

Hint: Always return Cypress commands inside cy.session callback [OK]

Common Mistakes:

• Putting cy.session in beforeEach is allowed and not a mistake
• Assuming clearing cookies is required before session
• Confusing cy.login() with cy.session()

5. You want to speed up a test suite with 10 tests that require login. Which approach best uses cy.session() to optimize speed and reliability?

hard

A. Use cy.session() once in a before hook to cache login for all tests

B. Use cy.session() inside each test to cache login separately

C. Avoid cy.session() and run full login steps in every test

D. Use cy.session() in afterEach to cache login after tests

Solution

1. Step 1: Understand before vs beforeEach hooks

   before runs once before all tests, beforeEach runs before every test.

2. Step 2: Choose best place for cy.session()

   Using cy.session() in before caches login once, speeding up all 10 tests reliably.

3. Final Answer:

   Use cy.session() once in a before hook to cache login for all tests -> Option A

4. Quick Check:

   Cache login once before all tests [OK]

Hint: Place cy.session() in before hook for all tests [OK]

Common Mistakes:

• Caching login inside each test wastes time
• Running full login every test is slow
• Using afterEach is too late for caching