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.

Practice

1. What is the basic Maven command to run all Selenium tests in a project?

easy

A. mvn test

B. mvn clean

C. mvn compile

D. mvn install

Solution

1. Step 1: Understand Maven lifecycle phases

   Maven has phases like clean, compile, test, package, install. The test phase runs tests.

2. Step 2: Identify command for running tests

   The command mvn test runs all tests in the project, including Selenium tests.

3. Final Answer:

   mvn test -> Option A

4. Quick Check:

   Maven test phase = mvn test [OK]

Hint: Use mvn test to run all tests quickly [OK]

Common Mistakes:

• Using mvn clean which only cleans files
• Using mvn compile which only compiles code
• Confusing mvn install with running tests

2. Which Maven command runs a specific Selenium test class named LoginTest?

easy

A. mvn run -Dtest=LoginTest

B. mvn test -Dtest=LoginTest

C. mvn test -Dclass=LoginTest

D. mvn compile -Dtest=LoginTest

Solution

1. Step 1: Recall Maven syntax for running specific tests

   Maven uses -Dtest=ClassName to run a specific test class.

2. Step 2: Match correct command format

   mvn test -Dtest=LoginTest runs only the LoginTest class.

3. Final Answer:

   mvn test -Dtest=LoginTest -> Option B

4. Quick Check:

   Run single test = -Dtest=ClassName [OK]

Hint: Use -Dtest=ClassName to run one test class [OK]

Common Mistakes:

• Using -Dclass instead of -Dtest
• Using mvn run which is not a valid phase
• Trying to run tests during compile phase

3. Given the Maven command mvn test -Dtest=LoginTest, what will be the output if LoginTest has 3 passing Selenium tests?

medium

A. No tests run because -Dtest is ignored

B. All tests run, but only 3 tests from LoginTest pass

C. Only 3 tests from LoginTest run and all pass

D. Tests fail because mvn test can't run specific tests

Solution

1. Step 1: Understand -Dtest effect

   The -Dtest=LoginTest option runs only tests in the LoginTest class.

2. Step 2: Interpret test results

   If LoginTest has 3 tests and all pass, only those 3 tests run and pass.

3. Final Answer:

   Only 3 tests from LoginTest run and all pass -> Option C

4. Quick Check:

   -Dtest runs specified tests only [OK]

Hint: Specific test runs only those tests, others skipped [OK]

Common Mistakes:

• Thinking all tests run despite -Dtest
• Assuming -Dtest is ignored
• Believing mvn test can't run specific tests

4. You run mvn test -Dtest=LoginTest but get an error: Could not find or load main class LoginTest. What is the likely cause?

medium

A. Maven does not support running specific tests

B. The pom.xml file is missing

C. You forgot to compile the project before testing

D. The test class name is misspelled or not in the correct package

Solution

1. Step 1: Analyze error message

   The error says it cannot find the LoginTest class, meaning the name or location is wrong.

2. Step 2: Check common causes

   Misspelling the class name or incorrect package path causes this error. Maven supports running specific tests, so A is wrong. Compile errors or missing pom.xml cause different errors.

3. Final Answer:

   The test class name is misspelled or not in the correct package -> Option D

4. Quick Check:

   Class not found = wrong name or package [OK]

Hint: Check test class spelling and package path first [OK]

Common Mistakes:

• Assuming Maven can't run specific tests
• Ignoring compilation errors
• Thinking missing pom.xml causes this error

5. You want to run all Selenium tests but exclude the SlowTests class using Maven. Which command achieves this?

hard

A. mvn test -Dtest=!SlowTests

B. mvn test -DexcludedTests=SlowTests

C. mvn test -Dtest='*' -DexcludedTests=SlowTests

D. mvn test -Dtest='*' -DexcludeTests=SlowTests

Solution

1. Step 1: Recall Maven syntax for excluding tests

   Maven allows excluding tests by prefixing the class name with an exclamation mark in -Dtest, like -Dtest=!ClassName.

2. Step 2: Match correct command

   mvn test -Dtest=!SlowTests runs all tests except SlowTests. Other options use invalid or unsupported properties.

3. Final Answer:

   mvn test -Dtest=!SlowTests -> Option A

4. Quick Check:

   Exclude test with -Dtest=!ClassName [OK]

Hint: Use -Dtest=!ClassName to exclude tests [OK]

Common Mistakes:

• Using -DexcludedTests which is unsupported
• Using wrong property names like excludeTests
• Trying to exclude tests without exclamation mark