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.