Apache Maven Beginner to Guru - Using Maven Surefire for the Plain Old Java Object (POJO) Unit Tests

The video tutorial introduces Pojo tests using the Maven Surefire plugin, starting from a project setup on the Pojo branch. It covers configuring Java 11, setting up application properties, and creating a simple test in Intellij. The tutorial explains Pojo test conventions, such as method naming, and demonstrates running tests with Maven. It concludes with a discussion on Maven Surefire's default behaviors and the simplicity of Pojo tests compared to JUnit or TestNG.

What is the primary purpose of using the Maven Surefire plugin?

• To run unit tests

• To compile Java code

• To manage project dependencies

• To deploy applications

Why was an empty application properties file added under test resources?

• To provide default values for tests

• To ensure Git tracks the directory structure

• To initialize the application

• To store configuration settings

What is the shortcut in IntelliJ to create a test class?

• Ctrl + Shift + T

• Option + Enter

• Alt + F12

• Cmd + N

Which convention does the Surefire plugin use to identify test methods in Pojo tests?

• Methods must start with 'Test'

• Methods must end with 'Test'

• Methods must be annotated with @Test

• Methods must contain 'Test' in the name

What happens if a test assertion fails when running with Maven?

• The test is retried

• The test is marked as failed

• The test is skipped

• The test is marked as passed

What is the default behavior of Maven Surefire regarding test class names?

• It runs classes that contain 'Test' anywhere in the name

• It runs classes that end with 'Test' or 'TestCase'

• It runs classes that are annotated with @Test

• It runs classes that start with 'Test'

What additional functionality do JUnit and TestNG provide over Pojo tests?

• Better integration with Git

• Faster test execution

• Richer assertion capabilities

• Simpler test setup