JUnit XML reporting for CI in PyTest - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

JUnit XML report generation with pytest

What is the output file generated by pytest when using the option --junitxml=report.xml?

PyTest

pytest --junitxml=report.xml

A No file is created; the option only prints XML to the console.

B A JSON file named <code>report.xml</code> is created with test results.

C A file named <code>report.xml</code> containing test results in JUnit XML format is created.

D A binary file named <code>report.xml</code> is created containing test logs.

💡 Hint

JUnit XML is a standard XML format for test reports used by CI tools.

The --junitxml=filename option tells pytest to write test results in JUnit XML format to the specified file. This file is XML, not JSON or binary.

❓ assertion

intermediate

Validating JUnit XML report content

Which assertion correctly checks that the JUnit XML report contains a test case with the name test_example?

PyTest

import xml.etree.ElementTree as ET

with open('report.xml') as f:
    tree = ET.parse(f)
    root = tree.getroot()

A assert root.find('testcase[@name="test_example"]') is None

B assert any(tc.attrib.get('name') == 'test_example' for tc in root.iter('testcase'))

C assert root.find('testcase').attrib['name'] == 'test_example'

D assert 'test_example' in root.text

💡 Hint

JUnit XML test cases are under elements with a 'name' attribute.

Option B correctly iterates over all elements and checks if any has the name 'test_example'. Option B checks for None which is opposite. Option B only checks the first testcase. Option B checks text content which is unreliable.

🔧 Debug

advanced

Fixing missing JUnit XML report in CI pipeline

A CI pipeline runs pytest with --junitxml=results.xml but the results.xml file is missing after the run. What is the most likely cause?

A The file was created but deleted by pytest after the run.

B The <code>--junitxml</code> option is deprecated and ignored by pytest.

C The test suite had no tests, so no report was generated.

D The pytest command ran in a different directory than expected, so the file was created elsewhere.

💡 Hint

Check the working directory of the pytest command in the CI job.

Pytest creates the JUnit XML file in the current working directory. If the CI job runs pytest in a different directory than expected, the file will be created there, not in the expected location. The option is not deprecated. Pytest creates the file even if no tests run. Pytest does not delete the file after creation.

❓ framework

advanced

Configuring pytest to always generate JUnit XML reports

How can you configure pytest to always generate a JUnit XML report named junit-report.xml without specifying --junitxml on the command line?

A Add <code>addopts = --junitxml=junit-report.xml</code> under the [pytest] section in <code>pytest.ini</code>.

B Set an environment variable <code>PYTEST_JUNITXML=junit-report.xml</code>.

C Create a <code>junit.xml</code> file manually before running pytest.

D Add <code>junitxml = junit-report.xml</code> under the [pytest] section in <code>pytest.ini</code>.

💡 Hint

pytest.ini can add default command line options.

The addopts setting in pytest.ini allows adding default command line options like --junitxml=filename. There is no junitxml config option. Creating a file manually or environment variable does not trigger report generation.

🧠 Conceptual

expert

Interpreting JUnit XML test suite attributes

In a JUnit XML report generated by pytest, what does the testsuite attribute failures represent?

A The number of test cases that failed due to assertion failures.

B The number of test cases skipped or marked as expected failures.

C The total number of tests executed including passed, failed, and skipped.

D The number of tests that passed successfully.

💡 Hint

Failures count tests that failed assertions.

The failures attribute counts tests that failed due to assertion failures. Skipped tests are counted separately. Total tests is in tests attribute. Passed tests are total minus failures, errors, and skipped.