Learn Java Unit Testing with JUnit 5 in 20 Steps - Step 07 - Setting up data for every test - @BeforeEach, @AfterEach

What is the primary purpose of the 'before each' annotation in JUnit?

• To execute a test case multiple times

• To set up a scenario before each test

• To clean up resources after each test

• To skip a test case

How does the 'before each' annotation help in test setup?

• It deletes test data after execution

• It combines multiple test cases into one

• It skips the setup process

• It allows for the setup to be repeated in each test

What is the role of the 'after each' annotation in JUnit?

• To clean up after each test

• To execute tests in parallel

• To skip tests based on conditions

• To initialize data before each test

Why is it important to use annotations like 'before each' and 'after each'?

• They allow for flexible method naming

• They ensure tests are executed in a specific order

• They help in setting up and cleaning up test environments

• They provide detailed test reports

What is the function of the Test Info class in JUnit?

• To generate test reports

• To execute tests in a specific order

• To identify which test is currently running

• To provide information about the test environment

How does JUnit 5 differ from JUnit 4 in terms of annotations?

• JUnit 5 does not support annotations

• JUnit 5 uses different names for 'before each' and 'after each'

• JUnit 5 does not allow method naming flexibility

• JUnit 5 requires annotations to be imported manually

Which feature is exclusive to JUnit 5 and not present in JUnit 4?

• Annotations for test setup

• Support for multiple test frameworks

• The ability to run tests in parallel

• The Test Info parameter