Preserving state between tests in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test code?

Consider the following Cypress test code that uses cy.session() to preserve login state between tests. What will be the value of loggedIn after both tests run?

Cypress

let loggedIn = false;

describe('Session preservation', () => {
  before(() => {
    cy.session('user-session', () => {
      cy.visit('/login');
      cy.get('#username').type('user');
      cy.get('#password').type('pass');
      cy.get('#login-button').click();
    });
  });

  it('Test 1: sets loggedIn to true', () => {
    cy.visit('/dashboard');
    cy.get('h1').should('contain', 'Dashboard');
    loggedIn = true;
  });

  it('Test 2: checks loggedIn value', () => {
    expect(loggedIn).to.equal(true);
  });
});

A The second test fails with a ReferenceError for loggedIn.

B The second test fails because loggedIn is false.

C The second test passes because loggedIn is true.

D The second test passes but loggedIn is undefined.

💡 Hint

cy.session() preserves browser session state, but JavaScript variables declared outside tests persist across it blocks automatically.

In Cypress, JavaScript variables like loggedIn declared at the top level of the spec file persist across tests because the file executes in a single scope. The second test passes as loggedIn is true. Separately, cy.session() preserves browser state like cookies and localStorage.

❓ assertion

intermediate

Which assertion correctly verifies that a cookie is preserved between tests?

You want to check that the cookie named auth_token is preserved between two Cypress tests. Which assertion inside the second test will correctly verify this?

A expect(cy.getCookie('auth_token')).to.have.property('value');

B expect(cy.getCookie('auth_token')).to.exist;

C cy.getCookie('auth_token').should('have.value');

D cy.getCookie('auth_token').should('exist');

💡 Hint

Remember that cy.getCookie() returns a Cypress chainable, so assertions should be chained.

Option D correctly chains should('exist') to the Cypress command cy.getCookie(). Options A and B incorrectly use expect on a Cypress command without resolving it. Option D uses an invalid assertion.

🔧 Debug

advanced

Why does this Cypress test fail to preserve localStorage between tests?

Look at this Cypress test suite. The localStorage is set in the first test but is empty in the second test. Why?

Cypress

describe('LocalStorage test', () => {
  it('sets localStorage item', () => {
    cy.visit('/');
    cy.window().then((win) => {
      win.localStorage.setItem('token', 'abc123');
    });
    cy.get('#status').should('contain', 'Logged in');
  });

  it('checks localStorage item', () => {
    cy.visit('/');
    cy.window().then((win) => {
      const token = win.localStorage.getItem('token');
      expect(token).to.equal('abc123');
    });
  });
});

A localStorage is cleared between tests by Cypress, so the second test sees empty localStorage.

B localStorage.setItem() is asynchronous and not awaited, so the item is not saved.

C localStorage is not accessible in Cypress tests due to security restrictions.

D The second test runs before the first test, so localStorage is empty.

💡 Hint

Think about how Cypress resets the browser state between tests.

Cypress clears localStorage between tests to ensure test isolation. To preserve localStorage, you must explicitly save and restore it using hooks or plugins.

❓ framework

advanced

Which Cypress command is designed to preserve state like cookies and localStorage between tests?

To avoid logging in before every test, which Cypress command helps preserve session state automatically?

A cy.preserve()

B cy.session()

C cy.cache()

D cy.keepState()

💡 Hint

Check Cypress documentation for session management commands.

cy.session() is the official Cypress command to cache and restore session data like cookies and localStorage between tests. The other commands do not exist.

🧠 Conceptual

expert

What is the main reason Cypress isolates state between tests by default?

Why does Cypress clear cookies, localStorage, and sessionStorage between tests unless explicitly preserved?

A To ensure tests are independent and do not affect each other, improving reliability.

B To speed up test execution by clearing browser data.

C Because Cypress cannot access browser storage across tests due to security policies.

D To force developers to write longer tests that include login steps every time.

💡 Hint

Think about test best practices and why isolation matters.

Isolating tests prevents flaky tests caused by leftover state. It ensures each test starts fresh, making results more reliable and easier to debug.