Report publishing in CI in Selenium Java - Test Execution Trace

Test Overview

This test runs a Selenium Java test case in a Continuous Integration (CI) environment and verifies that the test report is generated and published successfully after test execution.

Test Code - JUnit with Selenium WebDriver

Selenium Java

import org.junit.AfterClass;
import org.junit.Assert;
import org.junit.BeforeClass;
import org.junit.Test;
import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import java.io.File;

public class ReportPublishingCITest {
    private static WebDriver driver;
    private static final String REPORT_PATH = "target/surefire-reports/index.html";

    @BeforeClass
    public static void setUp() {
        // Set path to chromedriver executable if needed
        driver = new ChromeDriver();
    }

    @Test
    public void testGoogleSearch() {
        driver.get("https://www.google.com");
        WebElement searchBox = driver.findElement(By.name("q"));
        searchBox.sendKeys("Selenium testing");
        searchBox.submit();
        WebElement results = driver.findElement(By.id("search"));
        Assert.assertTrue(results.isDisplayed());
    }

    @AfterClass
    public static void tearDown() {
        if (driver != null) {
            driver.quit();
        }
        // Verify report file exists after tests
        File reportFile = new File(REPORT_PATH);
        Assert.assertTrue("Test report should be generated", reportFile.exists());
    }
}

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts - JUnit initializes and runs setUp method	ChromeDriver instance is created, browser window opens	—	PASS
2	Browser navigates to https://www.google.com	Google homepage is loaded in browser	—	PASS
3	Finds search input box by name 'q'	Search input box is located on the page	—	PASS
4	Types 'Selenium testing' into search box and submits form	Search results page loads with query results	—	PASS
5	Finds search results container by id 'search'	Search results container is present and visible	Assert that search results container is displayed	PASS
6	Test finishes, tearDown method runs and browser closes	Browser window is closed, WebDriver quits	—	PASS
7	Check if test report file 'target/surefire-reports/index.html' exists	CI environment file system contains test report file	Assert that test report file exists	PASS

Failure Scenario

Failing Condition: Test report file is not generated or not found at expected path after test execution

Execution Trace Quiz - 3 Questions

What does the test verify after closing the browser?

A That the test report file exists in the expected location

B That the browser window is still open

C That the search results contain a specific keyword

D That the ChromeDriver executable is installed

Key Result

Always verify that test reports are generated and accessible in your CI environment to ensure test results are properly published and can be reviewed.

Practice

1. What is the main purpose of publishing test reports in a Continuous Integration (CI) pipeline?

easy

A. To increase the speed of test execution

B. To automatically fix failed tests

C. To reduce the number of test cases

D. To quickly show test results after code changes

Solution

1. Step 1: Understand CI pipeline goals

   CI pipelines aim to integrate code changes frequently and provide feedback quickly.

2. Step 2: Role of test reports in CI

   Publishing test reports helps teams see if tests passed or failed right after changes.

3. Final Answer:

   To quickly show test results after code changes -> Option D

4. Quick Check:

   Test reports in CI = Quick feedback [OK]

Hint: Test reports in CI = fast feedback on code changes [OK]

Common Mistakes:

• Confusing report publishing with speeding up tests
• Thinking reports reduce test cases
• Believing reports fix tests automatically

2. Which of the following is the correct way to configure a Jenkins pipeline to publish JUnit test reports generated by Selenium Java tests?

easy

A. Use the junit '**/target/surefire-reports/*.xml' step in the pipeline script

B. Add publishJUnitReports() in the Java test code

C. Call driver.publishReports() in Selenium test methods

D. Use archiveArtifacts('**/*.html') to publish XML reports

Solution

1. Step 1: Identify Jenkins syntax for JUnit reports

   Jenkins uses the junit step with a file pattern to locate XML reports.

2. Step 2: Match correct usage

   junit '**/target/surefire-reports/*.xml' correctly points to JUnit XML files generated by Maven Surefire plugin.

3. Final Answer:

   Use the junit '**/target/surefire-reports/*.xml' step in the pipeline script -> Option A

4. Quick Check:

   Jenkins pipeline uses junit step with XML path [OK]

Hint: Jenkins publishes JUnit XML with junit('path') step [OK]

Common Mistakes:

• Trying to publish reports from Java code directly
• Using wrong Jenkins steps for report publishing
• Archiving HTML instead of XML for JUnit reports

3. Given the following Jenkins pipeline snippet, what will be the result of the junit '**/target/surefire-reports/*.xml' step if no XML files are found?

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn test'
        junit '**/target/surefire-reports/*.xml'
      }
    }
  }
}

medium

A. The build will fail with an error about missing reports

B. The build will pass with no test results recorded

C. The build will retry the test stage automatically

D. The build will pass but mark tests as skipped

Solution

1. Step 1: Understand junit step behavior with missing files

   If no XML files match, Jenkins does not fail the build but records no test results.

2. Step 2: Confirm build status

   Since no test results are found, the build passes but shows zero tests executed.

3. Final Answer:

   The build will pass with no test results recorded -> Option B

4. Quick Check:

   No XML files = build passes, no tests recorded [OK]

Hint: No XML files found means no tests recorded, build still passes [OK]

Common Mistakes:

• Assuming build fails if reports missing
• Thinking tests are marked skipped automatically
• Expecting automatic retries on missing reports

4. You configured your CI pipeline to publish Selenium test reports, but the reports are not visible in the CI dashboard. Which of the following is the most likely cause?

medium

A. The CI server does not support publishing reports

B. The Selenium tests did not run any assertions

C. The test report files are generated in a different directory than specified in the CI config

D. The test code uses deprecated Selenium APIs

Solution

1. Step 1: Check report file paths in CI config

   If the CI pipeline looks for reports in the wrong folder, it won't find or display them.

2. Step 2: Verify report generation location

   Ensure test reports are generated where the CI expects them, matching the configured path.

3. Final Answer:

   The test report files are generated in a different directory than specified in the CI config -> Option C

4. Quick Check:

   Report path mismatch = no reports shown [OK]

Hint: Check report file paths match between test and CI config [OK]

Common Mistakes:

• Blaming test assertions for missing reports
• Assuming CI server cannot publish reports
• Thinking deprecated APIs affect report visibility

5. You want to publish Selenium Java test reports in a CI pipeline that uses GitHub Actions. Which combination of steps correctly collects and publishes the test results?

hard

A. Run tests with Maven, then use actions/upload-artifact to save reports, and configure actions/junit-report to display them

B. Run tests with Maven, then use actions/download-artifact to save reports, and actions/junit-report to display them

C. Run tests with Maven, then use actions/upload-artifact to save reports, and actions/upload-test-report to display them

D. Run tests with Maven, then use actions/upload-artifact to save reports, and no further steps are needed to display reports

Solution

1. Step 1: Save test reports as artifacts

   Use actions/upload-artifact to store test report files after running tests.

2. Step 2: Use a report action to display results

   Configure actions/junit-report or similar to parse and show test results in GitHub UI.

3. Final Answer:

   Run tests with Maven, then use actions/upload-artifact to save reports, and configure actions/junit-report to display them -> Option A

4. Quick Check:

   Upload artifact + report action = published test results [OK]

Hint: Upload reports artifact then use report action to display [OK]

Common Mistakes:

• Using upload-test-report action which does not exist
• Downloading artifacts instead of uploading
• Skipping report display step after upload