JUnit XML reporting for CI in PyTest - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to run pytest and generate a JUnit XML report named 'results.xml'.

PyTest

import pytest

pytest.main(['tests', '--junitxml=[1]'])

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

Aresults.xml

Boutput.txt

Creport.json

Dlog.xml

Attempts:

3 left

💡 Hint

Common Mistakes

Using a filename with wrong extension like '.txt' or '.json'.

Forgetting to include the '--junitxml' option.

The '--junitxml' option tells pytest to save the test results in JUnit XML format. The filename should be 'results.xml' to match the requirement.

2fill in blank

medium

Complete the pytest command to run tests in the 'integration' folder and output JUnit XML report to 'ci_report.xml'.

PyTest

pytest.main(['[1]', '--junitxml=ci_report.xml'])

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

Atests

Bunit

Ce2e

Dintegration

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong folder name like 'unit' or 'tests'.

Omitting the folder argument causing all tests to run.

The argument specifies the folder where tests are located. Here, 'integration' is the correct folder to run integration tests.

3fill in blank

hard

Fix the error in the pytest command to correctly generate a JUnit XML report named 'test-results.xml'.

PyTest

pytest.main(['tests', '--junitxml', '[1]'])

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

Atest-results.xml

Btest-results.txt

C--junitxml=test-results.xml

Dresults.xml

Attempts:

3 left

💡 Hint

Common Mistakes

Passing '--junitxml=test-results.xml' as a separate argument causes error.

Using wrong file extension like '.txt'.

When using '--junitxml' as a separate argument, the next argument must be the filename. So 'test-results.xml' is correct here.

4fill in blank

hard

Fill both blanks to create a pytest command that runs tests in 'api_tests' folder and saves JUnit XML report as 'api_report.xml'.

PyTest

pytest.main(['[1]', '[2]'])

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

Aapi_tests

B--junitxml=api_report.xml

Ctests

D--junitxml=report.xml

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up folder and option arguments.

Using wrong filenames or folder names.

The first argument is the folder 'api_tests' to run tests from. The second argument is the option '--junitxml=api_report.xml' to save the report.

5fill in blank

hard

Fill all three blanks to create a pytest command that runs tests in 'ui_tests', outputs JUnit XML report to 'ui_results.xml', and increases verbosity.

PyTest

pytest.main(['[1]', '[2]', '[3]'])

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

Aui_tests

B--junitxml=ui_results.xml

C-v

D--maxfail=1

Attempts:

3 left

💡 Hint

Common Mistakes

Using '--maxfail=1' instead of '-v' for verbosity.

Wrong order of arguments causing errors.

The command runs tests in 'ui_tests', saves the report to 'ui_results.xml', and uses '-v' for verbose output.

Practice

1. What is the main purpose of generating a JUnit XML report in pytest for CI pipelines?

easy

A. To provide a standard format for test results that CI tools can read

B. To speed up test execution time

C. To automatically fix failing tests

D. To generate HTML reports for manual review

Solution

1. Step 1: Understand JUnit XML report role

   JUnit XML reports provide a standard format for test results that many CI tools can parse and display.

2. Step 2: Compare options with purpose

   Speeding tests, fixing tests, or generating HTML are not the main goals of JUnit XML reporting.

3. Final Answer:

   To provide a standard format for test results that CI tools can read -> Option A

4. Quick Check:

   JUnit XML = standard test result format [OK]

Hint: JUnit XML = standard test results for CI tools [OK]

Common Mistakes:

• Thinking JUnit XML speeds up tests
• Confusing XML report with HTML report
• Assuming it fixes tests automatically

2. Which pytest command correctly generates a JUnit XML report named results.xml?

easy

A. pytest --xml=results.xml

B. pytest --output=results.xml

C. pytest --report=results.xml

D. pytest --junitxml=results.xml

Solution

1. Step 1: Recall pytest option for JUnit XML

   The correct option to generate JUnit XML report is --junitxml=filename.

2. Step 2: Match option with command

   Only pytest --junitxml=results.xml uses --junitxml=results.xml, which is correct syntax.

3. Final Answer:

   pytest --junitxml=results.xml -> Option D

4. Quick Check:

   --junitxml option = correct flag [OK]

Hint: Use --junitxml=filename.xml to generate report [OK]

Common Mistakes:

• Using --xml instead of --junitxml
• Using --report or --output which are invalid
• Missing the equals sign '='

3. Given this pytest command:
pytest tests/ --junitxml=report.xml
What will happen after running it?

medium

A. Tests run but no report file is created

B. Tests run and a file named report.xml is created with test results in JUnit XML format

C. Tests do not run; only the report.xml file is created

D. Tests run and results are printed only to console, no file created

Solution

1. Step 1: Understand pytest command behavior

   The command runs tests in the tests/ folder and generates a JUnit XML report file named report.xml.

2. Step 2: Check output expectations

   Since --junitxml=report.xml is specified, the file will be created with test results in XML format.

3. Final Answer:

   Tests run and a file named report.xml is created with test results in JUnit XML format -> Option B

4. Quick Check:

   --junitxml creates XML report file [OK]

Hint: --junitxml creates XML report file after tests run [OK]

Common Mistakes:

• Thinking tests don't run when report option is used
• Expecting report file without running tests
• Assuming output only prints to console

4. You ran pytest --junitxml=results.xml but the file results.xml is empty. What is the most likely cause?

medium

A. No tests were collected or run

B. The --junitxml option is misspelled

C. The file path is invalid and pytest failed silently

D. JUnit XML reporting is not supported by pytest

Solution

1. Step 1: Analyze empty report cause

   An empty JUnit XML file usually means no tests were found or executed.

2. Step 2: Check other options

   The option --junitxml is correct, pytest supports it, and invalid paths usually cause errors, not silent empty files.

3. Final Answer:

   No tests were collected or run -> Option A

4. Quick Check:

   Empty XML = no tests run [OK]

Hint: Empty XML means no tests ran or were found [OK]

Common Mistakes:

• Assuming option is misspelled without checking
• Ignoring that no tests might be collected
• Thinking pytest doesn't support JUnit XML

5. You want your CI system to fail the build on the first pytest test failure using --failfast and --maxfail=1 and also save a JUnit XML report named ci-report.xml. Which command should you use?

hard

A. pytest --junitxml=ci-report.xml --maxfail=1 --exitfirst

B. pytest --junitxml=ci-report.xml --exitfirst --maxfail=0

C. pytest --junitxml=ci-report.xml --failfast --maxfail=1

D. pytest --junitxml=ci-report.xml --failfast --maxfail=0

Solution

1. Step 1: Understand options for failing fast

   To stop on first failure and fail the build, use --failfast and limit failures with --maxfail=1.

2. Step 2: Confirm JUnit XML report option

   --junitxml=ci-report.xml saves the report file as required.

3. Step 3: Evaluate options

   pytest --junitxml=ci-report.xml --failfast --maxfail=1 correctly combines --junitxml=ci-report.xml, --failfast, and --maxfail=1. Others have wrong or conflicting flags.

4. Final Answer:

   pytest --junitxml=ci-report.xml --failfast --maxfail=1 -> Option C

5. Quick Check:

   Fail fast + maxfail=1 + junitxml = pytest --junitxml=ci-report.xml --failfast --maxfail=1 [OK]

Hint: Use --failfast and --maxfail=1 with --junitxml for CI fail [OK]

Common Mistakes:

• Confusing --exitfirst with --failfast
• Setting maxfail=0 disables failure limit
• Omitting --failfast causes tests to run fully