Data cleanup approaches in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is data cleanup important in automated tests?

Imagine you run automated tests that create users in a system. Why should you clean up this test data after the tests finish?

A To make the test reports look nicer

B Because cleaning data makes tests run faster

C To avoid cluttering the database and causing false test results in future runs

D Because Cypress requires data cleanup to start tests

💡 Hint

Think about how leftover data might affect later tests.

Cleaning test data prevents leftover entries from interfering with future tests, ensuring tests run reliably and results stay accurate.

❓ Predict Output

intermediate

What is the output of this Cypress test cleanup code?

Consider this Cypress command that deletes a user by ID after a test:

afterEach(() => {
  cy.request('DELETE', '/api/users/123')
    .then((response) => {
      cy.log(response.status)
    })
})

What will be logged if the user is successfully deleted?

Cypress

afterEach(() => {
  cy.request('DELETE', '/api/users/123')
    .then((response) => {
      cy.log(response.status)
    })
})

A 200

B 404

C 500

D undefined

💡 Hint

HTTP 200 means success for DELETE requests.

If the user exists and is deleted, the server responds with status 200, which is logged by cy.log.

❓ assertion

advanced

Which assertion correctly verifies test data cleanup?

You want to check that a user with ID 456 no longer exists after cleanup. Which Cypress assertion is correct?

Cypress

cy.request({ method: 'GET', url: '/api/users/456', failOnStatusCode: false })
  .its('status')
  .should(/* fill here */)

A .should('eq', 200)

B .should('be.null')

C .should('not.exist')

D .should('eq', 404)

💡 Hint

Think about the HTTP status code when a resource is not found.

A 404 status means the user was not found, confirming cleanup was successful.

🔧 Debug

advanced

Why does this cleanup code fail to delete test data?

Look at this Cypress cleanup code snippet:

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

Tests pass but data is not deleted. What is the likely cause?

A Cypress cannot send DELETE requests

B The after() hook runs after all tests, but the deletion request is asynchronous and not waited on

C The user ID 789 does not exist, so deletion silently fails

D The DELETE method is not supported by the API

💡 Hint

Consider how Cypress handles asynchronous commands in hooks.

after() runs once after all tests, but without returning or chaining the request, Cypress may finish before the request completes, so deletion might not happen.

❓ framework

expert

Which Cypress approach ensures reliable test data cleanup across multiple tests?

You have many tests creating users. You want to clean all test users after the test suite finishes. Which approach is best?

A Use an <code>after()</code> hook to send a single API request that deletes all test users by a shared tag

B Use <code>afterEach()</code> to delete users one by one after each test

C Manually delete users in the UI after tests finish

D Do not clean data; rely on database resets between test runs

💡 Hint

Think about efficiency and reliability for large test suites.

Using an after() hook with a single API call to delete all test users by a tag is efficient and ensures cleanup happens once after all tests.

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