it blocks for test cases in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of nested it blocks in Cypress

Consider this Cypress test code snippet:

describe('My Test Suite', () => {
  it('Test case 1', () => {
    cy.visit('https://example.com')
  })

  it('Test case 2', () => {
    it('Nested test case', () => {
      cy.get('h1').should('be.visible')
    })
  })
})

What will happen when you run this test suite?

Cypress

describe('My Test Suite', () => {
  it('Test case 1', () => {
    cy.visit('https://example.com')
  })

  it('Test case 2', () => {
    it('Nested test case', () => {
      cy.get('h1').should('be.visible')
    })
  })
})

A Only 'Test case 1' will run; the others will be ignored silently.

B Both 'Test case 2' and 'Nested test case' will run sequentially without errors.

C 'Nested test case' will run but 'Test case 2' will be skipped.

D The test runner will throw an error because nesting it blocks is not allowed.

💡 Hint

Think about how Cypress structures test cases and the role of it blocks.

Cypress does not allow it blocks to be nested inside other it blocks. Nesting causes the test runner to throw an error because it defines a test case and cannot contain other test cases.

❓ assertion

intermediate

Correct assertion placement in it blocks

Which of the following is the correct way to write an assertion inside an it block in Cypress?

A it('checks title', () => { cy.title().should('eq', 'My Page') })

B it('checks title', () => { cy.title().then(title => { expect(title).to.eq('My Page') }) })

C it('checks title', () => { expect(cy.title()).to.eq('My Page') })

D it('checks title', () => { cy.title().should('equal', 'My Page') })

💡 Hint

Remember how Cypress commands and assertions work asynchronously.

Option A uses Cypress's built-in should assertion correctly on the cy.title() command. Option A works but is more verbose. Option A is incorrect because cy.title() returns a chainable, not the title string directly. Option A uses equal, which performs loose (==) equality, instead of the strict eq (===).

🔧 Debug

advanced

Debugging skipped tests inside it blocks

You have this Cypress test suite:

describe('Suite', () => {
  it.skip('skipped test', () => {
    cy.visit('https://example.com')
  })

  it('normal test', () => {
    cy.visit('https://example.com')
  })
})

What will be the result when running this suite?

Cypress

describe('Suite', () => {
  it.skip('skipped test', () => {
    cy.visit('https://example.com')
  })

  it('normal test', () => {
    cy.visit('https://example.com')
  })
})

A Neither test runs because one test is skipped.

B Both tests run normally without skipping.

C Only 'normal test' runs; 'skipped test' is ignored and marked as skipped in the report.

D The test runner throws an error because of the skip keyword.

💡 Hint

Think about the purpose of it.skip in Cypress.

The it.skip marks a test to be skipped. The test runner will not execute it but will show it as skipped in the test report. Other tests run normally.

🧠 Conceptual

advanced

Purpose of it blocks in Cypress

What is the main purpose of an it block in Cypress testing?

A To group multiple test suites together.

B To define a single test case that Cypress will execute.

C To set up preconditions before running tests.

D To clean up after all tests have run.

💡 Hint

Think about what you want Cypress to do step-by-step.

The it block defines a single test case. Cypress runs each it block as an individual test. Grouping multiple tests is done with describe. Setup and cleanup use before, after, beforeEach, and afterEach.

❓ framework

expert

Handling asynchronous commands inside it blocks

Consider this Cypress test:

it('checks element text', () => {
  let textContent = ''
  cy.get('#my-element').then(el => {
    textContent = el.text()
  })
  expect(textContent).to.equal('Hello')
})

What will be the result of this test?

Cypress

it('checks element text', () => {
  let textContent = ''
  cy.get('#my-element').then(el => {
    textContent = el.text()
  })
  expect(textContent).to.equal('Hello')
})

A The test will fail because the expect runs before the textContent is set.

B The test will pass because textContent is set correctly before the assertion.

C The test will throw a syntax error due to incorrect use of then.

D The test will be skipped because of asynchronous commands.

💡 Hint

Remember how Cypress commands run asynchronously and how JavaScript handles promises.

The expect assertion runs immediately after the cy.get command is queued, but before the then callback executes. So, textContent is still an empty string when expect runs, causing the test to fail.

Practice

1. What is the main purpose of an it block in Cypress testing?

easy

A. To define reusable functions for tests

B. To group multiple test suites together

C. To hold and describe a single test case with its steps

D. To configure the Cypress environment settings

Solution

1. Step 1: Understand the role of it blocks

   it blocks are used to write individual test cases in Cypress.

2. Step 2: Differentiate from other blocks

   Unlike describe which groups tests, it holds one test with steps and description.

3. Final Answer:

   To hold and describe a single test case with its steps -> Option C

4. Quick Check:

   it block = single test case [OK]

Hint: Remember: it means 'this test' [OK]

Common Mistakes:

• Confusing it with describe
• Thinking it configures environment
• Using it to group multiple tests

2. Which of the following is the correct syntax to write an it block in Cypress?

easy

A. it('checks title') => cy.title().should('include', 'Home')

B. it 'checks title' { cy.title().should('include', 'Home') }

C. it: 'checks title' => { cy.title().should('include', 'Home') }

D. it('checks title', () => { cy.title().should('include', 'Home') })

Solution

1. Step 1: Check the function call syntax

   The it block requires a string description and a callback function wrapped in parentheses.

2. Step 2: Validate arrow function and braces

   it('checks title', () => { cy.title().should('include', 'Home') }) correctly uses arrow function with braces and parentheses.

3. Final Answer:

   it('checks title', () => { cy.title().should('include', 'Home') }) -> Option D

4. Quick Check:

   Correct it syntax uses parentheses and arrow function [OK]

Hint: Use parentheses and arrow function for it [OK]

Common Mistakes:

• Omitting parentheses around parameters
• Using colon or wrong arrow syntax
• Missing braces for function body

3. What will be the result of running this Cypress test?

it('checks page title', () => { cy.visit('https://example.com'); cy.title().should('eq', 'Example Domain'); });

medium

A. Test fails because cy.visit is missing a callback

B. Test passes if the page title is exactly 'Example Domain'

C. Test throws a syntax error due to missing semicolon

D. Test passes regardless of the page title

Solution

1. Step 1: Analyze the test steps

   The test visits 'https://example.com' and checks if the page title equals 'Example Domain'.

2. Step 2: Understand assertion behavior

   The assertion should('eq', 'Example Domain') passes only if the title matches exactly.

3. Final Answer:

   Test passes if the page title is exactly 'Example Domain' -> Option B

4. Quick Check:

   Correct assertion = test passes if title matches [OK]

Hint: Check exact match with should('eq', ...) [OK]

Common Mistakes:

• Assuming cy.visit needs a callback
• Ignoring assertion conditions
• Confusing semicolons with syntax errors

4. Identify the error in this it block:

it('checks button', () => { cy.get('#submit').click() cy.get('#message').should('be.visible') })

medium

A. No error; the test will run correctly

B. Missing semicolon after click() causes syntax error

C. The it block is missing a description string

D. The selector #submit is invalid

Solution

1. Step 1: Check syntax for semicolons

   JavaScript allows optional semicolons; missing one here does not cause error.

2. Step 2: Verify test structure and selectors

   The it block has a description and valid selectors; no syntax or logic errors.

3. Final Answer:

   No error; the test will run correctly -> Option A

4. Quick Check:

   Missing semicolons often allowed; test runs fine [OK]

Hint: Semicolons optional in JS; focus on logic errors [OK]

Common Mistakes:

• Assuming missing semicolon always causes error
• Confusing missing description with error
• Thinking selectors are invalid without context

5. You want to write two it blocks to test login and logout separately. Which is the best practice?

hard

A. Write two it blocks inside one describe block, each with clear descriptions

B. Write both tests inside a single it block to save time

C. Write it blocks without descriptions to keep code short

D. Use multiple describe blocks but only one it block

Solution

1. Step 1: Understand test organization

   Each it block should hold one test case with a clear description.

2. Step 2: Group related tests

   Using one describe block to group login and logout tests keeps tests organized and readable.

3. Final Answer:

   Write two it blocks inside one describe block, each with clear descriptions -> Option A

4. Quick Check:

   Separate tests in it blocks grouped by describe [OK]

Hint: Group tests with describe, separate with it [OK]

Common Mistakes:

• Combining multiple tests in one it block
• Skipping descriptions for it blocks
• Using multiple describe blocks unnecessarily