Implicit waits in Selenium Python - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium implicit wait code?

Consider the following Selenium Python code snippet. What will be the output printed?

Selenium Python

from selenium import webdriver
from selenium.common.exceptions import NoSuchElementException
import time

options = webdriver.ChromeOptions()
options.add_argument('--headless')
driver = webdriver.Chrome(options=options)
driver.implicitly_wait(5)
start = time.time()
try:
    driver.find_element('id', 'nonexistent')
except NoSuchElementException:
    print('Element not found')
end = time.time()
print(f'Time waited: {round(end - start, 1)} seconds')
driver.quit()

A Element not found\nTime waited: 5.0 seconds

B Element not found\nTime waited: 10.0 seconds

C No output, script hangs

D Element not found\nTime waited: 0.0 seconds

💡 Hint

Implicit wait makes Selenium poll the DOM for a certain time before throwing an exception.

The implicit wait of 5 seconds causes Selenium to wait up to 5 seconds for the element before raising NoSuchElementException. The printed time waited will be about 5 seconds.

❓ assertion

intermediate

Which assertion correctly verifies implicit wait behavior?

You want to assert that your Selenium test waits at least 3 seconds when an element is missing, given an implicit wait of 3 seconds. Which assertion is correct?

Selenium Python

from selenium import webdriver
import time

options = webdriver.ChromeOptions()
options.add_argument('--headless')
driver = webdriver.Chrome(options=options)
driver.implicitly_wait(3)
start = time.time()
try:
    driver.find_element('id', 'missing')
except Exception:
    pass
end = time.time()
waited = end - start

# Which assertion below is correct?

A assert waited == 0

B assert waited >= 3

C assert waited < 3

D assert waited <= 1

💡 Hint

Implicit wait causes Selenium to wait up to the specified time before failing.

Since implicit wait is 3 seconds, Selenium waits up to 3 seconds before throwing an exception. So the elapsed time should be at least 3 seconds.

🔧 Debug

advanced

Why does this implicit wait not work as expected?

This Selenium Python code sets an implicit wait but still fails immediately when searching for a missing element. What is the likely cause?

Selenium Python

from selenium import webdriver
options = webdriver.ChromeOptions()
options.add_argument('--headless')
driver = webdriver.Chrome(options=options)

# Missing parentheses in method call
# driver.implicitly_wait

try:
    driver.find_element('id', 'missing')
except Exception as e:
    print(f'Error: {e}')
driver.quit()

A Implicit wait method is not called due to missing parentheses, so no wait is set

B Implicit wait is set but overridden by explicit wait

C The element locator is invalid causing immediate failure

D Headless mode disables implicit waits

💡 Hint

Check if the implicit wait method is actually executed.

The code has 'driver.implicitly_wait' without parentheses, so the method is not called. No implicit wait is set, causing immediate failure.

🧠 Conceptual

advanced

What is a limitation of Selenium implicit waits?

Which of the following is a known limitation of using implicit waits in Selenium tests?

A Implicit waits only work for elements found by CSS selectors

B Implicit waits guarantee element visibility before interaction

C Implicit waits automatically retry failed assertions

D Implicit waits apply globally and can cause unpredictable delays when combined with explicit waits

💡 Hint

Think about how implicit waits interact with other wait types.

Implicit waits apply globally and can cause unexpected delays or conflicts when used with explicit waits, leading to unpredictable test timing.

❓ framework

expert

How to correctly implement implicit wait in a Selenium test framework?

You are designing a Selenium test framework in Python. Where and how should you set the implicit wait to ensure consistent behavior across all tests?

A Set implicit wait inside each test case separately for flexibility

B Set implicit wait before every element search to customize wait times

C Set implicit wait once during WebDriver initialization and avoid changing it later

D Do not use implicit wait; rely only on explicit waits

💡 Hint

Implicit wait is a global setting on the WebDriver instance.

Implicit wait should be set once when the WebDriver is created to apply consistently across all element searches. Changing it repeatedly can cause confusion.

Practice

1. What is the main purpose of using implicit waits in Selenium WebDriver?

easy

A. To take screenshots automatically when a test fails

B. To tell the driver to wait for elements to appear before throwing an error

C. To speed up the test by skipping element checks

D. To pause the test execution for a fixed amount of time

Solution

1. Step 1: Understand implicit wait behavior

   Implicit waits tell the WebDriver to wait for a certain time when trying to find elements before failing.

2. Step 2: Compare with other options

   Options A, B, and C describe different actions not related to implicit waits.

3. Final Answer:

   To tell the driver to wait for elements to appear before throwing an error -> Option B

4. Quick Check:

   Implicit wait = wait for element presence [OK]

Hint: Implicit wait pauses only when element is missing [OK]

Common Mistakes:

• Confusing implicit wait with fixed sleep
• Thinking implicit wait speeds up tests
• Believing implicit wait takes screenshots

2. Which of the following is the correct syntax to set an implicit wait of 10 seconds in Selenium Python?

easy

A. driver.implicitly_wait(10)

B. driver.wait(10)

C. driver.set_implicit(10)

D. driver.implicitWait = 10

Solution

1. Step 1: Recall Selenium Python implicit wait syntax

   The correct method to set implicit wait is driver.implicitly_wait(seconds).

2. Step 2: Check other options for correctness

   Options A, C, and D are not valid Selenium Python methods or attributes.

3. Final Answer:

   driver.implicitly_wait(10) -> Option A

4. Quick Check:

   Use driver.implicitly_wait(seconds) [OK]

Hint: Use driver.implicitly_wait(seconds) to set implicit wait [OK]

Common Mistakes:

• Using wrong method names like wait() or set_implicit()
• Trying to assign implicitWait as a property
• Confusing implicit wait with explicit wait syntax

3. Consider this code snippet:

from selenium import webdriver
from selenium.webdriver.common.by import By
import time

driver = webdriver.Chrome()
driver.implicitly_wait(5)

start = time.time()
try:
    element = driver.find_element(By.ID, 'nonexistent')
except:
    pass
end = time.time()
print(round(end - start))

What is the expected printed output?

medium

A. Approximately 10

B. 0

C. An exception is raised and no output

D. Approximately 5

Solution

1. Step 1: Understand implicit wait effect on find_element

   Implicit wait makes find_element retry for up to 5 seconds before failing.

2. Step 2: Analyze timing code

   The code measures time taken to find a nonexistent element, which will be about 5 seconds due to implicit wait.

3. Final Answer:

   Approximately 5 -> Option D

4. Quick Check:

   Implicit wait delays failure ~5 seconds [OK]

Hint: Implicit wait delays find_element failure by set seconds [OK]

Common Mistakes:

• Expecting immediate failure with no wait
• Thinking implicit wait adds fixed sleep regardless
• Assuming exception stops timing before print

4. What is wrong with this Selenium Python code snippet?

driver = webdriver.Chrome()
driver.implicitly_wait = 10
button = driver.find_element(By.ID, 'submit')

medium

A. Implicit wait is set incorrectly as an attribute, not a method call

B. The locator By.ID is invalid

C. driver.find_element should be driver.find_elements

D. No error, code is correct

Solution

1. Step 1: Check how implicit wait is set

   Implicit wait must be set by calling driver.implicitly_wait(10), not by assigning to driver.implicitly_wait.

2. Step 2: Verify locator and method usage

   By.ID is valid and find_element is correct for single element.

3. Final Answer:

   Implicit wait is set incorrectly as an attribute, not a method call -> Option A

4. Quick Check:

   Set implicit wait by calling method, not assigning [OK]

Hint: Use parentheses to call implicitly_wait method [OK]

Common Mistakes:

• Assigning implicitly_wait instead of calling it
• Confusing find_element with find_elements
• Misusing locator constants

5. You have set an implicit wait of 10 seconds. Your test needs to click a button that appears only after 8 seconds. However, sometimes the button appears in 3 seconds. How does implicit wait affect your test execution time?

hard

A. The test fails if the button appears before 10 seconds

B. The test always waits the full 10 seconds before clicking

C. The test waits up to 10 seconds but proceeds immediately once the button appears

D. The test ignores implicit wait and clicks immediately

Solution

1. Step 1: Understand implicit wait dynamic behavior

   Implicit wait waits up to the set time but proceeds as soon as the element is found.

2. Step 2: Apply to button appearance timing

   If the button appears in 3 seconds, the test clicks immediately without waiting full 10 seconds.

3. Final Answer:

   The test waits up to 10 seconds but proceeds immediately once the button appears -> Option C

4. Quick Check:

   Implicit wait = max wait, not fixed delay [OK]

Hint: Implicit wait stops waiting once element appears [OK]

Common Mistakes:

• Thinking implicit wait always delays full time
• Believing implicit wait causes test failure if early
• Ignoring implicit wait effect on dynamic elements