GitHub Actions integration in Selenium Python - Test Execution Trace

Test Overview

This test automates a simple web login scenario using Selenium in Python. It verifies that the login button is clickable and that the user is redirected to the dashboard page after login. The test is designed to run in a GitHub Actions workflow to ensure continuous integration.

Test Code - Selenium

Selenium Python

import unittest
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

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

    def test_login(self):
        driver = self.driver
        driver.get('https://example.com/login')

        # Wait for username field and enter username
        WebDriverWait(driver, 10).until(
            EC.presence_of_element_located((By.ID, 'username'))
        )
        driver.find_element(By.ID, 'username').send_keys('testuser')

        # Wait for password field and enter password
        WebDriverWait(driver, 10).until(
            EC.presence_of_element_located((By.ID, 'password'))
        )
        driver.find_element(By.ID, 'password').send_keys('password123')

        # Wait for login button and click
        login_button = WebDriverWait(driver, 10).until(
            EC.element_to_be_clickable((By.ID, 'login-btn'))
        )
        login_button.click()

        # Verify redirection to dashboard
        WebDriverWait(driver, 10).until(
            EC.url_contains('/dashboard')
        )
        self.assertIn('/dashboard', driver.current_url)

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

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

Execution Trace - 7 Steps

Step	Action	System State	Assertion	Result
1	Test starts - unittest framework initializes and setUp method opens Chrome browser	Chrome browser window opens, ready to navigate	-	PASS
2	Browser navigates to 'https://example.com/login'	Login page loads with username, password fields and login button visible	-	PASS
3	Waits for username field presence and enters 'testuser'	Username input field is filled with 'testuser'	Presence of username field verified	PASS
4	Waits for password field presence and enters 'password123'	Password input field is filled with 'password123'	Presence of password field verified	PASS
5	Waits for login button to be clickable and clicks it	Login button clicked, form submitted	Login button is clickable	PASS
6	Waits for URL to contain '/dashboard' after login	Browser URL changes to dashboard page	Current URL contains '/dashboard'	PASS
7	Test ends - tearDown method closes browser	Browser window closes	-	PASS

Failure Scenario

Failing Condition: Login button is not found or not clickable within 10 seconds

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the login button?

A That the URL contains '/dashboard'

B That the username field is cleared

C That the login button disappears

D That an error message appears

Key Result

Always use explicit waits like WebDriverWait with expected conditions to handle dynamic page elements reliably in automated tests.