Report publishing in CI in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to initialize the ExtentReports object for report publishing.

Selenium Java

ExtentReports extent = new ExtentReports();
extent.attachReporter(new ExtentHtmlReporter([1]));

Drag options to blanks, or click blank then click option'

Atest-output/report.html

Breport.html

C"test-output/report.html"

D"report"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to put the file path in quotes.

Using a relative path without quotes causing syntax errors.

The ExtentHtmlReporter requires a string path with quotes to specify the report file location.

2fill in blank

medium

Complete the code to flush the ExtentReports so the report is saved after tests.

Selenium Java

extent.[1]();

Drag options to blanks, or click blank then click option'

Aflush

Bwrite

Csave

Dclose

Attempts:

3 left

💡 Hint

Common Mistakes

Using close() which may not save the report properly.

Trying to use save() which does not exist.

The flush() method writes all the test information to the report file.

3fill in blank

hard

Fix the error in the code to correctly add a test log entry with status PASS.

Selenium Java

test.[1](Status.PASS, "Test passed successfully");

Drag options to blanks, or click blank then click option'

Arecord

BaddLog

CwriteLog

Dlog

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like addLog or writeLog.

Trying to use record which is not a method here.

The correct method to log test status in ExtentTest is log().

4fill in blank

hard

Fill both blanks to create a Jenkins pipeline step that archives the test report folder and publishes the HTML report.

Selenium Java

archiveArtifacts '[1]'
publishHTML (target: [allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: '[2]', reportFiles: 'report.html', reportName: 'Test Report'])

Drag options to blanks, or click blank then click option'

Atest-output/**

Btest-output

Creports/**

Dreports

Attempts:

3 left

💡 Hint

Common Mistakes

Using the folder name without wildcards in archiveArtifacts causing no files archived.

Using wrong folder names that don't match the report location.

The archiveArtifacts step needs the folder with wildcard test-output/** to archive all files, and publishHTML uses the folder test-output as the report directory.

5fill in blank

hard

Fill all three blanks to configure a Maven Surefire plugin to generate test reports in XML format for CI integration.

Selenium Java

<configuration>
  <reportsDirectory>[1]</reportsDirectory>
  <testFailureIgnore>[2]</testFailureIgnore>
  <reportFormat>[3]</reportFormat>
</configuration>

Drag options to blanks, or click blank then click option'

Atarget/surefire-reports

Bfalse

Cxml

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Setting testFailureIgnore to true which ignores failures.

Using wrong report format like 'html' instead of 'xml'.

The reports directory for Surefire is target/surefire-reports. To fail the build on test failures, testFailureIgnore should be false. The report format for CI is usually xml.

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