Test reporting in CI in Selenium Python - Test Execution Trace

Test Overview

This test opens a web page, clicks a button, and verifies the result. It demonstrates how test results are reported in a Continuous Integration (CI) environment.

Test Code - Selenium with unittest

Selenium Python

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class TestButtonClick(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.driver.implicitly_wait(5)

    def test_button_click(self):
        self.driver.get('https://example.com/buttonpage')
        button = WebDriverWait(self.driver, 10).until(
            EC.element_to_be_clickable((By.ID, 'click-me'))
        )
        button.click()
        message = WebDriverWait(self.driver, 10).until(
            EC.visibility_of_element_located((By.ID, 'message'))
        )
        self.assertEqual(message.text, 'Button clicked!')

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

Execution Trace - 9 Steps

Step	Action	System State	Assertion	Result
1	Test starts	Test runner initializes and prepares to run tests	—	PASS
2	Browser opens Chrome	Chrome browser window opens, ready for navigation	—	PASS
3	Navigates to 'https://example.com/buttonpage'	Page loads with a button having ID 'click-me'	—	PASS
4	Waits until button with ID 'click-me' is clickable	Button is visible and enabled	Button is clickable	PASS
5	Clicks the button	Button click triggers message display	—	PASS
6	Waits until message with ID 'message' is visible	Message element appears with text 'Button clicked!'	Message is visible	PASS
7	Checks that message text equals 'Button clicked!'	Message text is exactly 'Button clicked!'	Assert message.text == 'Button clicked!'	PASS
8	Test ends and browser closes	Browser window closes, test runner collects results	—	PASS
9	Test report generated in CI environment	CI system shows test passed with details	Test status is PASS in report	PASS

Failure Scenario

Failing Condition: Message text does not match expected 'Button clicked!'

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the button?

A That the page URL changes

B That the message text is 'Button clicked!'

C That the button disappears

D That the browser closes automatically

Key Result

Always include clear assertions and wait conditions to ensure reliable test results in CI environments.

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