Test reporting in CI in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Understanding test report output in CI

Given the following pytest command with JUnit XML reporting enabled in a CI pipeline, what will be the main content of the generated report file?

Selenium Python

pytest --junitxml=report.xml tests/test_login.py

A An XML file containing test case names, statuses (pass/fail), and error messages if any

B A plain text log file with only console output of the tests

C A JSON file with detailed browser screenshots embedded

D A CSV file listing test names and execution times only

💡 Hint

JUnit XML format is a standard for test reports in CI systems.

The --junitxml option generates an XML report that includes test case names, their pass/fail status, and error details if tests fail. This format is widely used by CI tools to display test results.

❓ assertion

intermediate

Choosing the correct assertion for CI test failure reporting

In a Selenium test running in CI, which assertion will correctly fail the test and produce a clear failure message in the CI report if the page title is not as expected?

Selenium Python

driver.get('https://example.com')
actual_title = driver.title
expected_title = 'Example Domain'

A assert actual_title > expected_title

B assert actual_title != expected_title, f"Title should not be '{expected_title}'"

C assert actual_title == expected_title, f"Expected title '{expected_title}', but got '{actual_title}'"

D assert actual_title is expected_title

💡 Hint

Use equality check with a clear message for test failures.

Option C correctly asserts equality and provides a clear failure message. Option C asserts inequality which is incorrect here. Option C compares strings with > which is not meaningful for titles. Option C uses 'is' which checks identity, not equality.

🔧 Debug

advanced

Debugging missing test report in CI pipeline

A Selenium test suite runs in CI but the JUnit XML report file is missing after the run. Which is the most likely cause?

A The test cases have no assertions

B The pytest command was run without the --junitxml option

C The Selenium WebDriver was not initialized

D The test report file was deleted manually after the run

💡 Hint

Check the test command options for report generation.

Without the --junitxml option, pytest does not generate the XML report file. Missing assertions or WebDriver issues do not prevent report creation. Manual deletion is possible but less likely than missing the option.

❓ framework

advanced

Integrating Selenium tests with CI reporting tools

Which test framework feature best supports generating detailed test reports compatible with CI tools when running Selenium tests?

A Using pytest with the --junitxml option to produce XML reports

B Using unittest without any reporting plugins

C Running Selenium tests manually without automation

D Using print statements to log test results

💡 Hint

Look for automated report generation features.

Pytest's --junitxml option automatically creates XML reports that CI tools can parse. Unittest alone does not generate such reports without plugins. Manual runs and print statements do not produce structured reports.

🧠 Conceptual

expert

Best practice for test report artifacts in CI pipelines

In a CI pipeline running Selenium tests, what is the best practice for handling test report files to ensure reliable test result tracking?

A Delete test report files immediately after test execution to save space

B Manually email test reports after each pipeline run

C Print test results only to console without saving files

D Store test report files as pipeline artifacts and upload them to the CI server after each run

💡 Hint

Think about preserving test results for later review and CI integration.

Storing test reports as artifacts allows CI tools to display and archive test results. Deleting reports or only printing to console loses valuable data. Manual emailing is error-prone and not scalable.

Practice

1. What is the main purpose of test reporting in Continuous Integration (CI)?

easy

A. To provide quick feedback on test results automatically

B. To write test cases manually

C. To deploy the application to production

D. To create user documentation

Solution

1. Step 1: Understand CI test reporting role

   Test reporting in CI is designed to give fast feedback on whether tests pass or fail after code changes.

2. Step 2: Identify the correct purpose

   Among the options, only providing quick automatic feedback matches the main purpose of test reporting in CI.

3. Final Answer:

   To provide quick feedback on test results automatically -> Option A

4. Quick Check:

   Test reporting = quick feedback [OK]

Hint: Test reporting = fast feedback on tests [OK]

Common Mistakes:

• Confusing test reporting with deployment
• Thinking test reporting is about writing tests
• Mixing test reporting with documentation

2. Which pytest command option generates a test report in XML format suitable for CI tools?

easy

A. --html=report.html

B. --junitxml=report.xml

C. --json=report.json

D. --output=report.txt

Solution

1. Step 1: Recall pytest report options

   Pytest uses --junitxml to create XML reports compatible with many CI tools.

2. Step 2: Match option to XML report

   Among the options, only --junitxml=report.xml generates the correct XML format for CI.

3. Final Answer:

   --junitxml=report.xml -> Option B

4. Quick Check:

   Pytest XML report = --junitxml [OK]

Hint: Use --junitxml for CI XML reports in pytest [OK]

Common Mistakes:

• Using --html instead of --junitxml
• Confusing JSON or text output with XML
• Missing the file name after the option

3. Given this pytest command:
pytest tests/ --junitxml=results.xml
What will happen after the tests run?

medium

A. Tests will run but no report file will be created

B. Tests will fail due to syntax error in command

C. A file named results.xml will be created with test results in XML format

D. A HTML report named results.xml will be generated

Solution

1. Step 1: Understand the command effect

   The --junitxml=results.xml option tells pytest to save test results in XML format to the file named results.xml.

2. Step 2: Identify the output file type

   The file created is XML, not HTML, and the command syntax is correct, so tests run and report is saved.

3. Final Answer:

   A file named results.xml will be created with test results in XML format -> Option C

4. Quick Check:

   --junitxml creates XML report file [OK]

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

Common Mistakes:

• Thinking no report is created
• Confusing XML with HTML report
• Assuming command syntax error

4. You added --junitxml=report.xml to your pytest command, but the CI tool shows no test report. What is the most likely cause?

medium

A. The tests did not run due to errors in test code

B. The pytest command syntax is incorrect

C. The CI tool does not support XML reports

D. The report.xml file is not saved in the CI workspace directory

Solution

1. Step 1: Check report file location

   CI tools need the report file in the workspace folder to read it. If saved elsewhere, the tool won't find it.

2. Step 2: Verify other causes

   The command syntax is correct, tests likely ran, and most CI tools support XML reports, so the missing file location is the main issue.

3. Final Answer:

   The report.xml file is not saved in the CI workspace directory -> Option D

4. Quick Check:

   Report file location matters in CI [OK]

Hint: Ensure report file is in CI workspace folder [OK]

Common Mistakes:

• Assuming command syntax error without checking
• Ignoring file save location
• Thinking CI tools don't support XML reports

5. In a CI pipeline, you want to fail the build if any Selenium tests fail and generate a detailed report. Which approach is best?

hard

A. Run pytest with --junitxml=report.xml and configure CI to fail on test failures using this report

B. Run tests without report and manually check logs after build

C. Use --html=report.html and ignore test failures in CI

D. Run tests locally and upload screenshots only

Solution

1. Step 1: Generate machine-readable test report

   Using --junitxml=report.xml creates a detailed XML report that CI tools can parse.

2. Step 2: Configure CI to fail build on test failures

   CI tools can read the XML report and mark the build as failed if tests fail, automating quality checks.

3. Final Answer:

   Run pytest with --junitxml=report.xml and configure CI to fail on test failures using this report -> Option A

4. Quick Check:

   Use XML report + CI fail on test fail [OK]

Hint: Use --junitxml and CI fail on test failure [OK]

Common Mistakes:

• Ignoring test failures in CI
• Not generating machine-readable reports
• Relying on manual log checks