import pytest
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 LoginPage:
def __init__(self, driver):
self.driver = driver
self.email_input = (By.ID, 'email')
self.password_input = (By.ID, 'password')
self.login_button = (By.ID, 'loginBtn')
def open(self):
self.driver.get('https://example.com/login')
def login(self, email, password):
self.driver.find_element(*self.email_input).send_keys(email)
self.driver.find_element(*self.password_input).send_keys(password)
self.driver.find_element(*self.login_button).click()
class DashboardPage:
def __init__(self, driver):
self.driver = driver
self.heading = (By.TAG_NAME, 'h1')
def get_heading_text(self):
return self.driver.find_element(*self.heading).text
@pytest.mark.smoke
@pytest.mark.login
def test_login_success():
driver = webdriver.Chrome()
wait = WebDriverWait(driver, 10)
login_page = LoginPage(driver)
dashboard_page = DashboardPage(driver)
try:
login_page.open()
login_page.login('validuser@example.com', 'ValidPass123!')
wait.until(EC.url_to_be('https://example.com/dashboard'))
assert driver.current_url == 'https://example.com/dashboard', 'URL after login should be dashboard URL'
wait.until(EC.visibility_of_element_located(dashboard_page.heading))
heading_text = dashboard_page.get_heading_text()
assert heading_text == 'Welcome to your dashboard', f'Expected heading text but got "{heading_text}"'
finally:
driver.quit()This test uses pytest markers @pytest.mark.smoke and @pytest.mark.login to categorize it as a smoke test and login test. This helps to run specific groups of tests easily.
The Page Object Model separates page details from the test logic. LoginPage handles login page actions, and DashboardPage handles dashboard page elements.
We use explicit waits with WebDriverWait and expected_conditions to wait for the URL to change and the dashboard heading to appear. This avoids flaky tests caused by timing issues.
Assertions check the URL and heading text with clear messages to help understand failures.
The finally block ensures the browser closes even if the test fails.
