describe blocks for grouping in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of describe blocks in Cypress tests

What is the main purpose of using describe blocks in Cypress test files?

A To execute tests in parallel automatically

B To skip tests temporarily without deleting them

C To group related tests together for better organization and readability

D To define variables that are shared across all tests globally

💡 Hint

Think about how you organize chapters in a book to keep related topics together.

describe blocks help group related tests logically. This makes test files easier to read and maintain. They do not control execution order or variable scope globally.

❓ Predict Output

intermediate

Output order of nested describe and it blocks

Consider this Cypress test code. What is the order of test names printed in the test runner?

Cypress

describe('Group A', () => {
  it('Test 1', () => {});
  describe('Group B', () => {
    it('Test 2', () => {});
  });
  it('Test 3', () => {});
});

A Group A Test 1, Group B Test 2, Test 3

B Group A Test 1, Group A Group B Test 2, Group A Test 3

C Test 1, Test 2, Test 3

D Group B Test 2, Group A Test 1, Group A Test 3

💡 Hint

Tests run in the order they appear inside their describe blocks, preserving nesting.

The test runner shows full nested names. The order is Test 1, then nested Test 2 inside Group B, then Test 3.

❓ assertion

advanced

Correct assertion inside nested describe block

Which assertion correctly checks that a button with id submitBtn is visible inside a nested describe block in Cypress?

Cypress

describe('Form Tests', () => {
  describe('Submit Button', () => {
    it('should be visible', () => {
      // Which assertion is correct here?
    });
  });
});

A cy.get('#submitBtn').should('be.visible');

B cy.get('submitBtn').should('exist');

C cy.find('#submitBtn').isVisible();

D cy.get('#submitBtn').assertVisible();

💡 Hint

Remember the correct Cypress command to select elements and check visibility.

Option A uses the correct selector #submitBtn and the Cypress assertion should('be.visible'). Other options use invalid commands or selectors.

🔧 Debug

advanced

Why does a test inside describe block not run?

A developer wrote this code but the test inside describe does not run. What is the reason?

Cypress

describe('Login Tests', () => {
  it('should log in successfully', () => {
    cy.visit('/login');
    cy.get('#username').type('user');
    cy.get('#password').type('pass');
    cy.get('#submit').click();
  });
});

// Outside describe
it('should log out', () => {
  cy.get('#logout').click();
});

A The test outside the describe block runs but the one inside does not because describe is not called properly

B The test outside the describe block runs but the one inside does not because describe blocks must be named 'describe.only'

C The test inside describe does not run because it is missing a callback function

D The test inside describe runs normally; the test outside runs independently. Both run unless skipped.

💡 Hint

Both tests are valid and should run unless skipped or filtered.

Both tests run normally. Tests inside and outside describe blocks run unless skipped or filtered. The describe block is correctly defined.

❓ framework

expert

Best practice for setup code in nested describe blocks

In Cypress, where should you place beforeEach hooks to run setup code for all tests inside a nested describe block?

A Inside the nested describe block, before the it blocks

B Outside all describe blocks, at the top of the test file

C Inside each it block separately

D Inside the afterEach hook of the nested describe block

💡 Hint

Think about running setup code before each test in a group.

Placing beforeEach inside the nested describe runs setup before each test in that group only. Outside describe runs for all tests. afterEach runs after tests.