Report publishing in CI in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Report Publishing in CI Pipelines

Which statement best describes the purpose of publishing test reports in a Continuous Integration (CI) pipeline?

A To store test reports only on the local developer machine for privacy.

B To automatically fix failed tests without developer intervention.

C To prevent the CI pipeline from running if tests fail.

D To provide a visual summary of test results accessible after each build to help developers quickly identify failures.

💡 Hint

Think about why teams want to see test results after every code change.

Publishing reports in CI pipelines allows teams to see test results immediately after builds. This helps catch issues early and speeds up debugging.

❓ Predict Output

intermediate

TestNG Report Publishing Behavior in Jenkins

Given the following Jenkins pipeline snippet that runs TestNG tests and archives reports, what will be the outcome in Jenkins after the build completes?

Selenium Java

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

A Jenkins will archive the raw XML files but not display any test summary.

B Jenkins will fail the build because the junit step requires HTML reports, not XML.

C Jenkins will display a test report summary with passed, failed, and skipped tests after the build.

D Jenkins will ignore the junit step and not publish any report.

💡 Hint

Consider what the junit step does with XML test reports.

The junit step in Jenkins processes XML test result files and generates a test report summary visible in the Jenkins UI.

❓ assertion

advanced

Valid Assertion for Selenium Test Report Verification

Which assertion correctly verifies that the Selenium test report contains exactly 5 failed tests using Java and TestNG?

Selenium Java

int failedTests = report.getFailedTestCount();

A Assert.assertEquals(failedTests, 5);

B Assert.assertTrue(failedTests > 5);

C Assert.assertFalse(failedTests == 5);

D Assert.assertNull(failedTests);

💡 Hint

Think about how to check for exact equality in TestNG assertions.

Assert.assertEquals checks if the actual value matches the expected value exactly, which is needed here.

🔧 Debug

advanced

Debugging Missing Test Report in CI

A Selenium test suite runs successfully in Jenkins, but the test report is missing from the Jenkins UI. Which is the most likely cause?

A The test report XML files were not generated or saved to the expected directory.

B The Selenium tests did not run any assertions.

C The test code uses deprecated Selenium APIs.

D The Jenkins server is offline during the build.

💡 Hint

Think about what Jenkins needs to display reports.

Jenkins requires the test report files to be generated and saved in the correct location to display them. If files are missing, no report appears.

❓ framework

expert

Configuring Allure Report Publishing in a CI Pipeline

Which Jenkins pipeline snippet correctly runs Selenium tests with Maven and publishes Allure reports assuming Allure plugin is installed?

A

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
      }
    }
    stage('Allure Report') {
      steps {
        archiveArtifacts 'target/allure-results/*'
      }
    }
  }
}

B

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
      }
    }
    stage('Allure Report') {
      steps {
        allure includeProperties: false, jdk: '', results: [[path: 'target/allure-results']]
      }
    }
  }
}

C

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
      }
    }
    stage('Allure Report') {
      steps {
        publishHTML(target: [reportDir: 'target/allure-results', reportFiles: 'index.html', reportName: 'Allure Report'])
      }
    }
  }
}

D

pipeline {
  agent any
  stages {
    stage('Test') {
      steps {
        sh 'mvn clean test'
      }
    }
    stage('Allure Report') {
      steps {
        junit 'target/allure-results/*.xml'
      }
    }
  }
}

💡 Hint

Recall the Jenkins Allure plugin syntax for publishing reports.

The allure step is used to publish Allure reports in Jenkins. It requires specifying the results path. Using junit or publishHTML won't correctly publish Allure reports.