Running PyTest in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

PyTest command output in Jenkins pipeline

You run the following PyTest command in a Jenkins pipeline step:

pytest tests/ --junitxml=results.xml

What will be the main effect of this command?

PyTest

pytest tests/ --junitxml=results.xml

A PyTest runs tests but fails because '--junitxml' is not a valid option.

B PyTest runs tests and outputs results only to the console, ignoring the XML file.

C PyTest runs tests in the 'tests/' folder and saves test results in XML format to 'results.xml'.

D PyTest runs tests and saves results in JSON format to 'results.xml'.

💡 Hint

Look for the meaning of the '--junitxml' option in PyTest.

The '--junitxml=results.xml' option tells PyTest to save test results in JUnit XML format to the specified file. This file can be used by Jenkins to display test reports.

❓ Configuration

intermediate

Jenkinsfile step to run PyTest and archive results

Which Jenkinsfile snippet correctly runs PyTest tests and archives the JUnit XML test report for Jenkins to display?

A

steps {
  sh 'pytest tests/ --junitxml=results.xml'
  junit 'results.xml'
}

B

steps {
  sh 'pytest tests/'
  archiveArtifacts 'results.xml'
}

C

steps {
  sh 'pytest tests/ --junitxml=results.xml'
  archiveArtifacts 'results.xml'
}

D

steps {
  sh 'pytest tests/ --xml=results.xml'
  junit 'results.xml'
}

💡 Hint

Jenkins uses the 'junit' step to process JUnit XML reports.

The 'sh' step runs PyTest with the '--junitxml' option to generate the XML report. The 'junit' step tells Jenkins to read and display the test results from that XML file.

❓ Troubleshoot

advanced

PyTest test results not showing in Jenkins

You configured Jenkins to run PyTest with '--junitxml=results.xml' and added 'junit "results.xml"' in the pipeline. However, Jenkins shows no test results after the build. What is the most likely cause?

A The 'junit' step must be called before running PyTest.

B The 'results.xml' file was not created because PyTest failed before tests ran.

C Jenkins cannot read XML files generated by PyTest.

D The 'junit' step requires the XML file to be named 'test-results.xml'.

💡 Hint

Check if the XML file exists after the build.

If PyTest fails before running tests, it may not create the XML file. Without the file, Jenkins cannot display test results.

🔀 Workflow

advanced

Best Jenkins pipeline stage order for PyTest and coverage

You want to run PyTest with coverage reporting in Jenkins and publish both test results and coverage reports. Which pipeline stage order is correct?

A Publish coverage report, run PyTest with coverage, then publish test results.

B Run PyTest with coverage, publish coverage report, then publish test results.

C Publish test results, run PyTest with coverage, then publish coverage report.

D Run PyTest with coverage, publish test results, then publish coverage report.

💡 Hint

Test results must be published after tests run.

First run PyTest with coverage to generate reports. Then publish test results so Jenkins can show them. Finally, publish coverage reports.

🧠 Conceptual

expert

Why use '--junitxml' option with PyTest in Jenkins?

What is the main reason to use the '--junitxml' option when running PyTest in a Jenkins pipeline?

A To generate an XML file that Jenkins can parse to display detailed test results and trends.

B To speed up test execution by running tests in parallel.

C To automatically fix failing tests during the build.

D To convert test results into JSON format for Jenkins.

💡 Hint

Think about how Jenkins shows test reports.

The '--junitxml' option creates a JUnit XML report file. Jenkins reads this file to show test results, failures, and trends in its interface.