describe blocks for grouping in Cypress - Build an Automation Script

Group login page tests using describe blocks

Preconditions (2)

Step 1: Open the login page at 'https://example.com/login'

Step 2: Verify the page title contains 'Login'

Step 3: Enter '[e-mail]' in the email input field

Step 4: Enter 'Password123' in the password input field

Step 5: Click the login button

Step 6: Verify the URL changes to the dashboard page URL 'https://example.com/dashboard'

Step 7: Verify the dashboard page contains a welcome message

✅ Expected Result: All login related tests are grouped inside a describe block named 'Login Page Tests' and all assertions pass successfully

Automation Requirements - Cypress

Assertions Needed:

Page title contains 'Login'

URL changes to 'https://example.com/dashboard' after login

Dashboard page contains welcome message

Best Practices:

Use describe block to group related tests

Use it blocks for individual test cases

Use beforeEach hook to visit login page before each test

Use clear and descriptive test names

Use Cypress commands consistently

Automated Solution

Cypress

describe('Login Page Tests', () => {
  beforeEach(() => {
    cy.visit('https://example.com/login')
  })

  it('should have the correct page title', () => {
    cy.title().should('include', 'Login')
  })

  it('should login successfully and redirect to dashboard', () => {
    cy.get('input#email').type('[e-mail]')
    cy.get('input#password').type('Password123')
    cy.get('button#login').click()
    cy.url().should('eq', 'https://example.com/dashboard')
    cy.contains('Welcome').should('be.visible')
  })
})

The describe block groups all tests related to the login page under the name 'Login Page Tests'. This helps organize tests clearly.

The beforeEach hook runs before each test to open the login page, so each test starts fresh.

The first it block checks the page title includes 'Login'.

The second it block performs the login steps: entering email and password, clicking login, then verifying the URL and welcome message on the dashboard.

Using cy.get with IDs ensures stable selectors. Assertions use should to verify expected outcomes.

Common Mistakes - 4 Pitfalls

Not using describe blocks to group related tests

Visiting the login page inside each it block instead of beforeEach

{'mistake': "Using vague test names like 'test1' or 'check login'", 'why_bad': 'Does not clearly describe what the test does, making debugging harder', 'correct_approach': "Use descriptive names like 'should login successfully and redirect to dashboard'"}

Using unstable selectors like XPath or complex CSS selectors

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials inside the describe block

Show Hint

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