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.

Practice

1. What is the main purpose of using describe blocks in Cypress tests?

easy

A. To group related test cases together for better organization

B. To run tests faster by skipping some tests

C. To define variables used in tests

D. To style the test output with colors

Solution

1. Step 1: Understand the role of describe blocks

   describe blocks are used to group related tests logically.

2. Step 2: Identify the benefit of grouping tests

   Grouping tests helps keep tests organized and makes reports easier to read.

3. Final Answer:

   To group related test cases together for better organization -> Option A

4. Quick Check:

   describe groups tests = A [OK]

Hint: Remember: describe groups tests, it contains it blocks [OK]

Common Mistakes:

• Thinking describe runs tests faster
• Confusing describe with variable declaration
• Assuming describe styles output

2. Which of the following is the correct syntax to start a describe block in Cypress?

easy

A. describe('Test group') => { ... }

B. describe = 'Test group' { ... }

C. describe: 'Test group' => { ... }

D. describe('Test group', () => { ... })

Solution

1. Step 1: Recall the correct syntax for describe

   The correct syntax uses the function call format: describe('name', callback).

2. Step 2: Check each option for syntax errors

   describe('Test group', () => { ... }) matches the correct syntax. Options B, C, and D have invalid assignment or arrow function usage.

3. Final Answer:

   describe('Test group', () => { ... }) -> Option D

4. Quick Check:

   describe syntax = function call [OK]

Hint: describe uses function call with name and callback [OK]

Common Mistakes:

• Using assignment instead of function call
• Missing parentheses or arrow function syntax
• Confusing colon with equals sign

3. Given the code below, how many tests will run and what will be their names?

describe('Login Tests', () => {
  it('should open login page', () => {});
  it('should submit login form', () => {});
});

medium

A. 2 tests: 'should open login page' and 'should submit login form'

B. 2 tests: 'Login Tests should open login page' and 'Login Tests should submit login form'

C. 1 test: 'Login Tests'

D. No tests will run because describe has no assertions

Solution

1. Step 1: Count the number of it blocks inside describe

   There are 2 it blocks, so 2 tests will run.

2. Step 2: Understand how test names are formed

   Test names combine the describe name and it name, joined by a space.

3. Final Answer:

   2 tests: 'Login Tests should open login page' and 'Login Tests should submit login form' -> Option B

4. Quick Check:

   describe + it names combined = C [OK]

Hint: Test names = describe name + it name combined [OK]

Common Mistakes:

• Counting describe as a test
• Ignoring describe name prefix in test names
• Assuming tests won't run without assertions

4. Identify the error in the following Cypress test code:

describe('User Tests', () => {
  it('checks user profile', () => {
    cy.visit('/profile')
  }
});

medium

A. The it block should not have a callback function

B. describe block name should be a variable, not a string

C. Missing closing parenthesis for the it block function

D. cy.visit cannot be used inside it blocks

Solution

1. Step 1: Check the syntax of the it block

   The it block's arrow function is missing a closing parenthesis before the closing brace.

2. Step 2: Verify other parts for errors

   describe name as string is correct, cy.visit is valid inside it, and it requires a callback function.

3. Final Answer:

   Missing closing parenthesis for the it block function -> Option C

4. Quick Check:

   Syntax error: missing parenthesis = D [OK]

Hint: Count all parentheses and braces carefully [OK]

Common Mistakes:

• Thinking describe name must be a variable
• Believing cy.visit is disallowed inside it
• Removing callback function from it block

5. You want to group tests for 'Signup' and 'Login' separately but run them together. Which is the best way to organize your Cypress tests?

hard

A. Use two separate describe blocks, one for Signup and one for Login, each with their own it tests

B. Put all Signup and Login tests inside a single it block

C. Use multiple it blocks without any describe blocks

D. Use nested describe blocks inside each it block

Solution

1. Step 1: Understand grouping with describe blocks

   Using separate describe blocks for Signup and Login groups tests logically and keeps reports clear.

2. Step 2: Evaluate other options

   Putting all tests in one it block is bad practice. Multiple it without describe loses grouping. Nested describe inside it is invalid.

3. Final Answer:

   Use two separate describe blocks, one for Signup and one for Login, each with their own it tests -> Option A

4. Quick Check:

   Separate describe blocks for groups = B [OK]

Hint: Use describe to group related tests, not inside it blocks [OK]

Common Mistakes:

• Putting many tests inside one it block
• Not using describe blocks for grouping
• Nesting describe inside it blocks