Data cleanup approaches in Cypress

Introduction

Data cleanup helps keep tests independent and reliable by removing leftover data after tests run.

After creating test data like users or orders to avoid clutter.

Before running tests to ensure a clean starting point.

When tests modify shared data that could affect others.

To prevent database or system overload from too much test data.

Syntax

Cypress

after(() => {
  // cleanup code here
  cy.request('DELETE', '/api/test-data')
})

after() runs once after all tests in a block finish.

You can also use afterEach() to clean after each test.

Examples

Deletes a test user after all tests complete.

Cypress

after(() => {
  cy.request('DELETE', '/api/users/testuser')
})

Runs cleanup after each test to reset data.

Cypress

afterEach(() => {
  cy.request('POST', '/api/cleanup')
})

Resets database before tests start to ensure clean state.

Cypress

before(() => {
  cy.request('POST', '/api/reset-database')
})

Sample Program

This test suite resets the database before tests, creates a user during the test, and deletes that user after all tests finish.

Cypress

describe('User tests with cleanup', () => {
  before(() => {
    cy.request('POST', '/api/reset-database')
  })

  it('creates a new user', () => {
    cy.request('POST', '/api/users', { username: 'testuser' })
      .then(response => {
        expect(response.status).to.eq(201)
      })
  })

  after(() => {
    cy.request('DELETE', '/api/users/testuser')
  })
})

Important Notes

Always clean data to avoid tests affecting each other.

Use API calls or database commands for faster cleanup than UI actions.

Be careful to only delete test data, not real data.

Summary

Data cleanup keeps tests independent and reliable.

Use before, after, beforeEach, or afterEach hooks for cleanup.

API requests are efficient for cleaning test data.

Practice

1. Why is data cleanup important in Cypress tests?

easy

A. It makes tests run slower

B. It increases the number of test failures

C. It keeps tests independent and reliable

D. It removes the need for assertions

Solution

1. Step 1: Understand test independence

   Tests should not depend on data left by previous tests to avoid false results.

2. Step 2: Recognize reliability benefits

   Cleaning data ensures each test starts fresh, making results trustworthy.

3. Final Answer:

   It keeps tests independent and reliable -> Option C

4. Quick Check:

   Data cleanup = test independence and reliability [OK]

Hint: Data cleanup ensures fresh start for each test [OK]

Common Mistakes:

• Thinking cleanup slows tests
• Believing cleanup causes more failures
• Assuming cleanup removes assertions

2. Which Cypress hook is best to use for cleaning test data after each test?

easy

A. afterEach

B. beforeEach

C. before

D. after

Solution

1. Step 1: Identify hooks for cleanup timing

   afterEach runs after every test, ideal for cleanup after each test.

2. Step 2: Compare other hooks

   before and beforeEach run before tests; after runs once after all tests.

3. Final Answer:

   afterEach -> Option A

4. Quick Check:

   Cleanup after each test = afterEach [OK]

Hint: Use afterEach to clean after every test [OK]

Common Mistakes:

• Using before for cleanup
• Confusing beforeEach with cleanup hook
• Using after which runs only once

3. What will happen if you use this code snippet in Cypress?

after(() => {
  cy.request('DELETE', '/api/test-data')
})

medium

A. Test data is never cleaned

B. Test data is cleaned once after all tests finish

C. Test data is cleaned after each test

D. Test data is cleaned before each test

Solution

1. Step 1: Understand after hook behavior

   after runs once after all tests in the suite complete.

2. Step 2: Analyze the API request timing

   The DELETE request runs only once after all tests, cleaning data once at the end.

3. Final Answer:

   Test data is cleaned once after all tests finish -> Option B

4. Quick Check:

   after = cleanup once after all tests [OK]

Hint: after runs once after all tests finish [OK]

Common Mistakes:

• Thinking after runs after each test
• Confusing after with afterEach
• Assuming cleanup runs before tests

4. You wrote this code to clean test data after each test:

afterEach(() => {
  cy.request('DELETE', '/api/test-data')
})

But test data is not cleaned properly. What is the likely problem?

medium

A. The API endpoint URL might be incorrect or unavailable

B. The afterEach hook is not supported in Cypress

C. You should use beforeEach instead of afterEach

D. The DELETE method is not allowed in HTTP

Solution

1. Step 1: Verify afterEach hook validity

   afterEach is valid and commonly used for cleanup in Cypress.

2. Step 2: Check API request issues

   If data is not cleaned, the DELETE request may fail due to wrong URL or server issues.

3. Final Answer:

   The API endpoint URL might be incorrect or unavailable -> Option A

4. Quick Check:

   Failed cleanup often means API endpoint problem [OK]

Hint: Check API URL if cleanup fails [OK]

Common Mistakes:

• Thinking afterEach is unsupported
• Using wrong HTTP method assumptions
• Switching hooks unnecessarily

5. You want to ensure test data is cleaned efficiently before and after each test in Cypress. Which approach is best?

hard

A. Manually delete data in each test without hooks

B. Use only before hook to clean data once before all tests

C. Use after hook to clean data once after all tests finish

D. Use beforeEach to create data and afterEach to delete data via API requests

Solution

1. Step 1: Understand test data lifecycle

   Creating data before each test and cleaning after each test keeps tests isolated and reliable.

2. Step 2: Use API requests in hooks

   API calls in beforeEach and afterEach efficiently manage test data per test.

3. Final Answer:

   Use beforeEach to create data and afterEach to delete data via API requests -> Option D

4. Quick Check:

   Setup and cleanup per test = beforeEach + afterEach [OK]

Hint: Use beforeEach and afterEach with API calls [OK]

Common Mistakes:

• Cleaning data only once before or after all tests
• Not using hooks for cleanup
• Manually deleting data inside tests