Maven build lifecycle in Selenium Java - Test Execution Trace

Test Overview

This test runs a Selenium WebDriver test using Maven's build lifecycle. It verifies that the Maven phases compile the code, run tests, and package the application successfully.

Test Code - JUnit 5 with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertTrue;

public class MavenLifecycleTest {
    private WebDriver driver;

    @BeforeEach
    public void setUp() {
        // Assuming chromedriver is in system PATH
        driver = new ChromeDriver();
    }

    @Test
    public void testGoogleSearch() {
        driver.get("https://www.google.com");
        WebElement searchBox = driver.findElement(By.name("q"));
        searchBox.sendKeys("Maven build lifecycle");
        searchBox.submit();

        // Wait for title to contain search term
        for (int i = 0; i < 10; i++) {
            if (driver.getTitle().toLowerCase().contains("maven build lifecycle")) {
                break;
            }
            try {
                Thread.sleep(500);
            } catch (InterruptedException e) {
                // ignore
            }
        }

        assertTrue(driver.getTitle().toLowerCase().contains("maven build lifecycle"));
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 11 Steps

Step	Action	System State	Assertion	Result
1	Maven starts build lifecycle: validate phase	Project structure and POM file are checked for correctness	—	PASS
2	Maven runs compile phase to compile Java source code	Java source files compiled into target/classes directory	No compilation errors	PASS
3	Maven runs test-compile phase to compile test source code	Test Java files compiled into target/test-classes directory	No compilation errors in test code	PASS
4	Maven runs test phase to execute tests	JUnit test MavenLifecycleTest starts execution	Test method testGoogleSearch() runs	PASS
5	Test opens Chrome browser using Selenium WebDriver	Chrome browser window opens	Browser is launched successfully	PASS
6	Test navigates to https://www.google.com	Google homepage is loaded	Page title contains 'Google'	PASS
7	Test finds search input box by name 'q'	Search box element is located	Element is present and interactable	PASS
8	Test enters text 'Maven build lifecycle' and submits search	Search results page loads	Page title contains 'maven build lifecycle'	PASS
9	Test asserts page title contains search term	Title verified	assertTrue(title contains 'maven build lifecycle')	PASS
10	Test closes browser	Browser window closed	Driver quit successfully	PASS
11	Maven runs package phase to create JAR	Target directory contains packaged JAR file	JAR file created without errors	PASS

Failure Scenario

Failing Condition: Search input element with name 'q' is not found on Google homepage

Execution Trace Quiz - 3 Questions

What does the test verify after submitting the search?

A That the page title contains 'maven build lifecycle'

B That the search box is empty

C That the browser closes immediately

D That the URL changes to a different domain

Key Result

Use Maven's lifecycle phases to manage build steps clearly: compile, test-compile, test, and package. This ensures tests run on compiled code and packaging happens only after successful tests.

Practice

1. Which Maven build lifecycle phase is responsible for compiling the source code of a Java project?

easy

A. clean

B. test

C. package

D. compile

Solution

1. Step 1: Understand Maven lifecycle phases

   Maven has phases like clean, compile, test, and package, each with a specific role.

2. Step 2: Identify the phase for compiling source code

   The compile phase compiles the Java source code into bytecode.

3. Final Answer:

   compile -> Option D

4. Quick Check:

   Compile phase compiles code = compile [OK]

Hint: Compile phase always compiles source code [OK]

Common Mistakes:

• Confusing 'test' phase with compiling code
• Thinking 'package' compiles code
• Assuming 'clean' compiles code

2. Which Maven command cleans the project by deleting the target directory?

easy

A. mvn clean

B. mvn compile

C. mvn package

D. mvn test

Solution

1. Step 1: Recall Maven commands and their purposes

   mvn clean deletes the target directory, removing previous build files.

2. Step 2: Match command to cleaning action

   Only mvn clean removes old build artifacts before a fresh build.

3. Final Answer:

   mvn clean -> Option A

4. Quick Check:

   Clean command deletes target folder = mvn clean [OK]

Hint: Clean command always removes old build files [OK]

Common Mistakes:

• Using mvn package to clean project
• Confusing mvn test with cleaning
• Thinking mvn compile cleans files

3. What will happen if you run mvn test on a Maven project that has not been compiled yet?

medium

A. Tests will fail because code is not compiled

B. Maven will compile the code first, then run tests

C. Maven will skip compilation and run tests directly

D. Maven will only clean the project without running tests

Solution

1. Step 1: Understand Maven lifecycle phase dependencies

   Running mvn test triggers all previous phases including compile automatically.

2. Step 2: Predict behavior when code is not compiled

   Maven compiles code before running tests to ensure tests run on compiled classes.

3. Final Answer:

   Maven will compile the code first, then run tests -> Option B

4. Quick Check:

   Test phase runs compile first = compile then test [OK]

Hint: Test phase always runs compile first [OK]

Common Mistakes:

• Assuming tests run without compiling
• Thinking Maven skips compile phase
• Confusing clean with test phase

4. You run mvn package but get an error saying tests failed. What is the best way to fix this without skipping tests?

medium

A. Run mvn package -DskipTests to skip tests

B. Run mvn compile only to compile code

C. Run mvn clean package to clean and rebuild

D. Delete the target folder manually and rerun mvn package

Solution

1. Step 1: Understand the error cause

   Tests failed during package phase, so build stopped.

2. Step 2: Choose a fix that cleans and rebuilds including tests

   Running mvn clean package removes old files and rebuilds fresh, running tests again.

3. Final Answer:

   Run mvn clean package to clean and rebuild -> Option C

4. Quick Check:

   Clean then package reruns tests = mvn clean package [OK]

Hint: Clean before package to fix test errors without skipping [OK]

Common Mistakes:

• Skipping tests instead of fixing them
• Only compiling without packaging
• Manually deleting target folder is error-prone

5. You want to create a Maven build that cleans, compiles, runs tests, and packages your project in one command. Which command should you use?

hard

A. mvn clean package

B. mvn clean compile test package

C. mvn compile test package

D. mvn test package

Solution

1. Step 1: Understand Maven lifecycle chaining

   Running a later phase runs all previous phases automatically.

2. Step 2: Identify the shortest command that runs all phases

   mvn clean package runs clean, compile, test, and package in order.

3. Final Answer:

   mvn clean package -> Option A

4. Quick Check:

   Package phase runs all before it = mvn clean package [OK]

Hint: Run clean then package to do all steps in one [OK]

Common Mistakes:

• Listing all phases explicitly is unnecessary
• Skipping clean phase
• Running test package without clean