it blocks for test cases in Cypress - Build an Automation Script

Verify login functionality with valid credentials

Preconditions (1)

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

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

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

Step 4: Wait for the dashboard page to load

✅ Expected Result: User is redirected to the dashboard page with URL containing '/dashboard' and a welcome message with id 'welcomeMsg' is visible

Automation Requirements - Cypress

Assertions Needed:

Verify URL contains '/dashboard' after login

Verify welcome message with id 'welcomeMsg' is visible

Best Practices:

Use 'it' blocks to define individual test cases

Use 'cy.get' with valid selectors for elements

Use assertions like 'should' for verification

Avoid hardcoded waits; use Cypress automatic waits

Keep tests isolated and independent

Automated Solution

Cypress

describe('Login Tests', () => {
  it('should login successfully with valid credentials', () => {
    cy.visit('https://example.com/login');
    cy.get('#email').type('[e-mail]');
    cy.get('#password').type('Password123!');
    cy.get('#loginBtn').click();
    cy.url().should('include', '/dashboard');
    cy.get('#welcomeMsg').should('be.visible');
  });
});

The describe block groups related tests under 'Login Tests'.

The it block defines one test case: logging in with valid credentials.

cy.visit opens the login page.

cy.get selects elements by their IDs and type enters text.

click clicks the login button.

cy.url().should('include', '/dashboard') asserts the URL changed to dashboard.

cy.get('#welcomeMsg').should('be.visible') asserts the welcome message is visible.

This structure uses Cypress best practices: clear selectors, no hard waits, and isolated test case in an it block.

Common Mistakes - 3 Pitfalls

Using hardcoded waits like cy.wait(5000) after clicking login

{'mistake': "Not using 'it' blocks and putting all steps inside 'describe' only", 'why_bad': "Makes tests hard to read and maintain; 'describe' is for grouping, 'it' for test cases.", 'correct_approach': "Use 'it' blocks for each test case to keep tests clear and isolated."}

Using invalid or overly complex selectors like absolute XPath

Bonus Challenge

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

Show Hint

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