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 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, 'login-btn')
def enter_email(self, email):
WebDriverWait(self.driver, 10).until(
EC.visibility_of_element_located(self.email_input)
).send_keys(email)
def enter_password(self, password):
WebDriverWait(self.driver, 10).until(
EC.visibility_of_element_located(self.password_input)
).send_keys(password)
def click_login(self):
WebDriverWait(self.driver, 10).until(
EC.element_to_be_clickable(self.login_button)
).click()
class DashboardPage:
def __init__(self, driver):
self.driver = driver
self.welcome_message = (By.ID, 'welcome-msg')
def get_welcome_text(self):
return WebDriverWait(self.driver, 10).until(
EC.visibility_of_element_located(self.welcome_message)
).text
class TestLogin(unittest.TestCase):
def setUp(self):
self.driver = webdriver.Chrome()
self.driver.get('https://example.com/login')
def test_login_success(self):
login_page = LoginPage(self.driver)
login_page.enter_email('testuser@example.com')
login_page.enter_password('TestPass123!')
login_page.click_login()
WebDriverWait(self.driver, 10).until(
EC.url_contains('/dashboard')
)
self.assertIn('/dashboard', self.driver.current_url)
dashboard_page = DashboardPage(self.driver)
welcome_text = dashboard_page.get_welcome_text()
self.assertEqual(welcome_text, 'Welcome, Test User!')
def tearDown(self):
self.driver.quit()
if __name__ == '__main__':
unittest.main()This script uses Selenium with Python's unittest framework to automate the login test.
Page Object Model: We created LoginPage and DashboardPage classes to keep locators and actions organized. This makes maintenance easier.
Explicit waits: We wait for elements to be visible or clickable before interacting. This avoids flaky tests.
Assertions: We check that the URL contains '/dashboard' and the welcome message text matches exactly.
Setup and teardown: The browser opens before each test and closes after to keep tests isolated.
This test can be integrated into a CI pipeline to run automatically on every code push, enabling continuous testing by catching issues early.
