Expected conditions in Selenium Python - Build an Automation Script
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 # Initialize the Chrome driver with webdriver.Chrome() as driver: driver.get('https://example.com/login') wait = WebDriverWait(driver, 10) # wait up to 10 seconds # Wait until the login button is clickable login_button = wait.until(EC.element_to_be_clickable((By.ID, 'login-btn'))) # Click the login button login_button.click() # Wait until the URL changes to dashboard wait.until(EC.url_to_be('https://example.com/dashboard')) # Assert the URL is correct assert driver.current_url == 'https://example.com/dashboard', f"Expected URL to be 'https://example.com/dashboard' but got {driver.current_url}"
This script uses Selenium WebDriver with Python to automate the manual test case.
First, it opens the login page URL.
Then, it uses WebDriverWait with the expected condition element_to_be_clickable to wait until the login button is ready to be clicked. This avoids errors from clicking too early.
After the button is clickable, it clicks the button.
Next, it waits until the URL changes to the dashboard page using url_to_be expected condition.
Finally, it asserts that the current URL matches the expected dashboard URL to confirm navigation succeeded.
This approach uses explicit waits instead of fixed delays, making the test more reliable and faster.
Now add data-driven testing with 3 different login button IDs to verify the expected conditions work for each.
Practice
ExpectedConditions in Selenium WebDriver?Solution
Step 1: Understand ExpectedConditions role
ExpectedConditions help Selenium wait for specific states like element visibility or clickability before proceeding.Step 2: Identify the main purpose
This waiting avoids errors caused by trying to interact with elements not yet ready on the page.Final Answer:
To wait for certain conditions before interacting with elements -> Option AQuick Check:
ExpectedConditions = Wait for conditions [OK]
- Thinking ExpectedConditions speed up tests by skipping waits
- Confusing ExpectedConditions with data generation
- Assuming ExpectedConditions take screenshots
Solution
Step 1: Check correct ExpectedCondition usage
element_to_be_clickable requires a locator tuple like (By.ID, 'submit').Step 2: Verify syntax correctness
WebDriverWait(driver, 10).until(EC.element_to_be_clickable((By.ID, 'submit'))) correctly uses a tuple inside the condition and waits properly.Final Answer:
WebDriverWait(driver, 10).until(EC.element_to_be_clickable((By.ID, 'submit'))) -> Option BQuick Check:
Use tuple locator with element_to_be_clickable [OK]
- Passing string instead of locator tuple
- Using visibility_of_element_located instead of clickable
- Missing parentheses around locator tuple
from selenium.webdriver.common.by import By from selenium.webdriver.support.ui import WebDriverWait from selenium.webdriver.support import expected_conditions as EC wait = WebDriverWait(driver, 10) element = wait.until(EC.visibility_of_element_located((By.ID, 'login'))) print(element.is_displayed())
Solution
Step 1: Analyze wait duration and element visibility
The wait is 10 seconds, and the element appears after 5 seconds, so wait.until succeeds.Step 2: Understand is_displayed() output
Since the element is visible, element.is_displayed() returns True, which is printed.Final Answer:
True -> Option CQuick Check:
Element visible within wait = True output [OK]
- Expecting TimeoutException though element appears in time
- Confusing is_displayed() with presence only
- Assuming False if element appears late but within wait
wait = WebDriverWait(driver, 5) wait.until(EC.element_to_be_clickable(By.CLASS_NAME, 'btn'))
Solution
Step 1: Check element_to_be_clickable parameter
It requires a single locator tuple like (By.CLASS_NAME, 'btn'), not two separate arguments.Step 2: Identify syntax error
Code passes two arguments instead of one tuple, causing a TypeError.Final Answer:
Missing tuple around locator in element_to_be_clickable -> Option DQuick Check:
Locator must be a tuple inside ExpectedConditions [OK]
- Passing locator arguments separately instead of tuple
- Assuming timeout value causes error here
- Confusing locator types (CLASS_NAME vs CSS_SELECTOR)
Solution
Step 1: Identify correct ExpectedCondition for URL substring
EC.url_contains waits until the URL contains the given substring.Step 2: Verify other options
url_matches requires a regex pattern to match the entire URL, url_to_be checks for exact URL equality, and url_is is not a valid ExpectedCondition.Final Answer:
WebDriverWait(driver, 15).until(EC.url_contains('dashboard')) -> Option AQuick Check:
Use url_contains for substring in URL [OK]
- Using non-existent ExpectedConditions like url_is
- Confusing url_contains with exact match conditions like url_to_be
- Using url_matches without proper regex for substring
Ready to prove it?
Pass the test and this pattern moves unknown
