Why synchronization prevents flaky tests in Selenium Python - Automation Benefits in Action

Verify login button becomes clickable after page load

Preconditions (2)

Step 1: Open the login page URL in browser

Step 2: Wait for the login button to become clickable

Step 3: Click the login button

Step 4: Verify that the next page URL contains '/dashboard'

✅ Expected Result: Login button is clicked only after it is clickable, and user is navigated to dashboard page

Automation Requirements - Selenium with Python

Assertions Needed:

Assert login button is clickable before clicking

Assert current URL contains '/dashboard' after click

Best Practices:

Use explicit waits (WebDriverWait) for synchronization

Avoid hardcoded sleeps

Use By locators for element identification

Automated Solution

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

# Setup WebDriver
with webdriver.Chrome() as driver:
    driver.get('https://example.com/login')

    wait = WebDriverWait(driver, 10)  # Wait up to 10 seconds

    # Wait until 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 URL contains '/dashboard'
    wait.until(EC.url_contains('/dashboard'))

    # Assert current URL contains '/dashboard'
    assert '/dashboard' in driver.current_url, f"Expected '/dashboard' in URL but got {driver.current_url}"

This script uses Selenium WebDriver with Python to automate the test case.

First, it opens the login page URL.

Then, it uses WebDriverWait with element_to_be_clickable to wait explicitly until the login button is ready to be clicked. This prevents clicking too early, which can cause flaky tests.

After the button is clickable, it clicks the button.

Next, it waits until the URL contains '/dashboard' to confirm navigation.

Finally, it asserts the URL contains '/dashboard' to verify the expected result.

This approach avoids using fixed sleeps and relies on synchronization to make the test stable and reliable.

Common Mistakes - 3 Pitfalls

Using time.sleep() instead of explicit waits

Clicking elements immediately after page load without waiting

Using incorrect or brittle locators like absolute XPath

Bonus Challenge

Now add data-driven testing with 3 different login URLs to verify synchronization works on all.

Show Hint

Practice

1. Why is synchronization important in Selenium tests?

easy

A. It changes the website's code to make testing easier.

B. It waits for elements to be ready before interacting, preventing timing issues.

C. It speeds up the test execution by skipping waits.

D. It automatically fixes bugs in the application.

Solution

1. Step 1: Understand synchronization role

   Synchronization ensures the test waits until the page or elements are ready before performing actions.

2. Step 2: Identify why this matters

   This prevents random failures caused by elements not being ready, which are common timing issues in tests.

3. Final Answer:

   It waits for elements to be ready before interacting, preventing timing issues. -> Option B

4. Quick Check:

   Synchronization = waits for readiness [OK]

Hint: Synchronization means waiting for elements before action [OK]

Common Mistakes:

• Thinking synchronization speeds up tests
• Believing synchronization changes app code
• Assuming synchronization fixes bugs automatically

2. Which of the following is the correct way to use an explicit wait in Selenium Python?

easy

A. wait = WebDriverWait(driver, 10)
wait.until(EC.element_to_be_clickable((By.ID, 'submit')))

B. wait = WebDriverWait(driver, '10')
wait.until(EC.element_to_be_clickable('submit'))

C. wait = WebDriverWait(driver)
wait.until(EC.element_to_be_clickable((By.ID, 'submit')))

D. wait = WebDriverWait(driver, 10)
wait.until(EC.element_to_be_clickable('submit'))

Solution

1. Step 1: Check WebDriverWait syntax

   WebDriverWait requires driver and timeout as integer seconds, so 10 is correct.

2. Step 2: Verify locator usage

   Locator must be a tuple like (By.ID, 'submit'), not just a string.

3. Final Answer:

   wait = WebDriverWait(driver, 10)\nwait.until(EC.element_to_be_clickable((By.ID, 'submit'))) -> Option A

4. Quick Check:

   Correct wait syntax = wait = WebDriverWait(driver, 10) wait.until(EC.element_to_be_clickable((By.ID, 'submit'))) [OK]

Hint: Use integer timeout and tuple locator in explicit wait [OK]

Common Mistakes:

• Passing timeout as string instead of integer
• Using string locator instead of tuple
• Omitting timeout parameter

3. What will happen if you run this Selenium Python code without synchronization?

driver.get('https://example.com')
element = driver.find_element(By.ID, 'dynamic-button')
element.click()

medium

A. The test will always pass because the element is found immediately.

B. The test will throw a syntax error.

C. The test will wait automatically until the element is clickable.

D. The test may fail sometimes if the element is not yet loaded when searched.

Solution

1. Step 1: Understand element loading timing

   Without synchronization, Selenium tries to find the element immediately after page load.

2. Step 2: Identify possible failure cause

   If the element loads slowly, find_element may fail because the element is not present yet, causing flaky failures.

3. Final Answer:

   The test may fail sometimes if the element is not yet loaded when searched. -> Option D

4. Quick Check:

   No wait = possible failure [OK]

Hint: No wait means element might not be ready, causing failure [OK]

Common Mistakes:

• Assuming element is always ready immediately
• Thinking Selenium waits automatically without explicit code
• Confusing syntax error with runtime failure

4. You wrote this code but sometimes it fails with NoSuchElementException:

driver.get('https://example.com')
button = driver.find_element(By.ID, 'submit')
button.click()

How can you fix it?

medium

A. Add an explicit wait to wait until the button is clickable before clicking.

B. Remove the click() method to avoid errors.

C. Change the locator to By.CLASS_NAME without checking the element.

D. Add a sleep(10) before driver.get() call.

Solution

1. Step 1: Identify cause of NoSuchElementException

   The element may not be present immediately after page load, causing the exception.

2. Step 2: Apply explicit wait for element readiness

   Using explicit wait waits until the button is clickable, preventing the error.

3. Final Answer:

   Add an explicit wait to wait until the button is clickable before clicking. -> Option A

4. Quick Check:

   Use explicit wait to fix element not found [OK]

Hint: Use explicit wait before clicking to avoid element not found [OK]

Common Mistakes:

• Removing click() disables test action
• Changing locator blindly may not fix timing
• Using sleep before page load is ineffective

5. You have a test that clicks a button which appears only after a loading spinner disappears. Which synchronization approach best prevents flaky failures?

hard

A. Click the button immediately after page load without waiting.

B. Use time.sleep(5) to wait a fixed time before clicking the button.

C. Use an explicit wait to wait until the spinner element is invisible before clicking the button.

D. Use an implicit wait to wait for the button to be present.

Solution

1. Step 1: Understand the problem with spinner

   The button appears only after the spinner disappears, so waiting for spinner invisibility is key.

2. Step 2: Choose best synchronization method

   Explicit wait for spinner to be invisible is precise and reliable, preventing flaky tests.

3. Step 3: Compare other options

   Fixed sleep is unreliable; implicit wait waits for presence but not invisibility; clicking immediately causes failure.

4. Final Answer:

   Use an explicit wait to wait until the spinner element is invisible before clicking the button. -> Option C

5. Quick Check:

   Wait for spinner invisibility = stable test [OK]

Hint: Wait explicitly for spinner to disappear before clicking [OK]

Common Mistakes:

• Using fixed sleep causes flaky timing
• Relying on implicit wait for invisibility
• Clicking without waiting causes failure