Data cleanup approaches in Cypress - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of data cleanup in testing?

Data cleanup ensures that test data does not affect other tests by removing or resetting data after tests run. It keeps tests independent and reliable.

beginner

Name two common data cleanup approaches in Cypress tests.

1. Using API calls to delete or reset data before or after tests.
2. Using database commands or scripts to clean test data directly.

intermediate

How can you use Cypress hooks for data cleanup?

Use hooks like afterEach() or after() to run cleanup code that deletes or resets data after tests finish.

intermediate

Why is it better to clean data via API calls rather than UI actions in Cypress?

API calls are faster and more reliable for cleanup because they avoid UI delays and flakiness. They directly modify data without needing user interface steps.

beginner

What is a potential risk if data cleanup is not done properly?

Tests may fail unpredictably due to leftover data causing conflicts, making test results unreliable and hard to debug.

Which Cypress hook is best for cleaning data after each test?

A it()

B before()

C beforeEach()

D afterEach()

The afterEach() hook runs after every test, making it ideal for cleaning up data after each test.

What is a common method to clean test data in Cypress?

A Using API calls to delete data

B Refreshing the browser tab

C Clicking the logout button

D Waiting for 5 seconds

API calls directly remove or reset data, which is a reliable cleanup method.

Why avoid cleaning data only through UI actions in Cypress?

A UI actions are slower and less reliable

B UI actions are faster

C UI actions do not affect data

D UI actions are always disabled

UI actions can be slow and flaky, making cleanup less reliable.

What happens if test data is not cleaned properly?

A Tests run faster

B Tests may fail due to leftover data

C Tests become more secure

D Tests skip cleanup automatically

Leftover data can cause conflicts and test failures.

Which is NOT a good practice for data cleanup in Cypress?

A Using database scripts to reset data

B Using afterEach() hook for cleanup

C Ignoring cleanup and relying on manual reset

D Using API calls to delete test data

Ignoring cleanup leads to unreliable tests and is not recommended.

Explain why data cleanup is important in automated testing with Cypress.

Think about how leftover data can affect other tests.

Describe two ways to perform data cleanup in Cypress tests and their benefits.

Consider speed and reliability when choosing cleanup methods.

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