Apache Maven Beginner to Guru - Using Maven Surefire for JUnit 4 and JUnit 5 Tests

What is the primary purpose of adding the JUnit Jupiter API and Jupiter engine?

• To enable backward compatibility with JUnit 3

• To enhance the performance of tests

• To define the API and run the tests

• To provide a graphical user interface for tests

Why was the JUnit 5 vintage engine added to the project?

• To provide a new testing framework

• To enable integration with third-party tools

• To allow JUnit 4 tests to run in a JUnit 5 context

• To improve test execution speed

What was the outcome after adding the JUnit 5 vintage engine?

• JUnit 3 tests were automatically included

• Both JUnit 4 and 5 tests ran successfully

• JUnit 5 tests were disabled

• JUnit 4 tests failed to run

What is a key benefit of upgrading legacy JUnit 4 tests to JUnit 5?

• Increased test execution time

• Simplified test configuration

• Enhanced support for older Java versions

• Improved compatibility with modern development practices

What is the role of the Surefire plugin in the context of JUnit 5?

• To manage test dependencies

• To provide a user interface for test results

• To automate test case generation

• To ensure compatibility with JUnit 5

What common issue might occur if outdated documentation is followed?

• Tests may run twice

• Tests may require additional dependencies

• Tests may not run at all

• Tests may produce incorrect results

What was the initial step taken to integrate JUnit 4 and 5?

• Upgrading the Java version

• Removing all JUnit 4 tests

• Branching from the JUnit 4 branch

• Creating a new test framework