Running tests via Maven in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output when running Maven test with this POM snippet?

Given this Maven pom.xml snippet configuring the Surefire plugin to run tests, what will be the output when you run mvn test?

Selenium Java

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>3.0.0-M7</version>
  <configuration>
    <includes>
      <include>**/*Test.java</include>
    </includes>
  </configuration>
</plugin>

A Maven skips tests because no test classes are specified in the configuration.

B Maven runs all Java files ending with 'Tests.java' as test classes and reports test results.

C Maven runs all Java files in the src/main/java folder as tests and reports results.

D Maven runs all Java files ending with 'Test.java' as test classes and reports test results.

💡 Hint

Look carefully at the <include> pattern used in the Surefire plugin configuration.

The Surefire plugin runs tests matching the pattern **/*Test.java. This means any Java class ending with 'Test' will be executed as a test class. Other patterns or folders are not included unless specified.

❓ assertion

intermediate

Which Maven command runs tests and skips compiling the main code?

You want to run tests using Maven but skip compiling the main source code to save time. Which command achieves this?

A mvn test -Dmaven.main.skip=true

B mvn test -DskipCompile=true

C mvn test -Dmaven.compiler.skipMain=true

D mvn test -DskipTests=false

💡 Hint

Check the correct Maven property to skip compiling main code.

The property maven.compiler.skipMain=true skips compiling the main source code but still runs tests. Other options either don't exist or do not skip main compilation.

🔧 Debug

advanced

Why does Maven fail to find tests when running mvn test?

Given this project structure and pom.xml configuration, Maven fails to find any tests when running mvn test. What is the most likely cause?

Project structure:
src/
  main/
    java/
  test/
    java/
      com/example/tests/MyTest.java

pom.xml snippet:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M7</version>
<configuration>
<includes>
<include>**/*Tests.java</include>
</includes>
</configuration>
</plugin>

A The Surefire plugin version 3.0.0-M7 does not support Java test execution.

B The include pattern '**/*Tests.java' does not match 'MyTest.java', so no tests are found.

C The test source folder is incorrectly named 'test' instead of 'tests'.

D The test class 'MyTest.java' is missing the @Test annotation.

💡 Hint

Check the file name and the include pattern carefully.

The include pattern '**/*Tests.java' looks for files ending with 'Tests.java' (plural). The test file is named 'MyTest.java' (singular), so it does not match and is skipped.

❓ framework

advanced

How to configure Maven to run only tests tagged with @Category(SmokeTests.class)?

You want Maven to run only tests marked with the JUnit 4 category @Category(SmokeTests.class). Which Surefire plugin configuration snippet achieves this?

A

<configuration>
  <includedGroups>com.example.categories.SmokeTests</includedGroups>
</configuration>

B

<configuration>
  <groups>com.example.categories.SmokeTests</groups>
</configuration>

C

<configuration>
  <tags>SmokeTests</tags>
</configuration>

D

<configuration>
  <excludedGroups>com.example.categories.SmokeTests</excludedGroups>
</configuration>

💡 Hint

Look for the correct Surefire configuration element to include test groups.

The Surefire plugin uses includedGroups to specify which JUnit 4 categories to run. excludedGroups excludes them. groups and tags are not valid configuration elements for this purpose.

🧠 Conceptual

expert

What is the effect of running mvn clean test -Dtest=MyTest#testMethod?

Explain what happens when you run the following Maven command:

mvn clean test -Dtest=MyTest#testMethod

A Maven cleans the project, then runs only the single test method 'testMethod' in the 'MyTest' class.

B Maven cleans the project, then runs all tests in the 'MyTest' class except 'testMethod'.

C Maven cleans the project, then runs all tests in all classes matching 'MyTest*'.

D Maven cleans the project, then runs all tests in the project ignoring the -Dtest parameter.

💡 Hint

Check how the -Dtest parameter with method name works.

The -Dtest=MyTest#testMethod syntax tells Maven Surefire to run only the specified test method 'testMethod' inside the 'MyTest' class after cleaning the project.