Implicit wait in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java code snippet with implicit wait?

Consider the following Selenium Java code snippet. What will be the output if the element with id 'submitBtn' appears after 3 seconds?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(5));
long start = System.currentTimeMillis();
driver.findElement(By.id("submitBtn"));
long end = System.currentTimeMillis();
System.out.println("Waited for: " + (end - start) + " ms");

A Waited for: approximately 3000 ms

B Waited for: approximately 5000 ms

C Waited for: approximately 0 ms

D Throws NoSuchElementException immediately

💡 Hint

Implicit wait tells Selenium how long to keep trying to find an element before throwing an exception.

The implicit wait is set to 5 seconds, but since the element appears after 3 seconds, Selenium waits about 3 seconds before finding it. So the printed wait time is approximately 3000 ms.

❓ assertion

intermediate

Which assertion correctly verifies implicit wait is set to 10 seconds?

You want to check if the implicit wait timeout is set to 10 seconds in Selenium Java. Which assertion is correct?

A assertEquals(Duration.ofSeconds(10), driver.manage().timeouts().getImplicitWaitTimeout());

B assertEquals(Duration.ofMillis(10000), driver.manage().timeouts().getImplicitWaitTimeout());

C assertEquals(10, driver.manage().timeouts().implicitlyWait());

D assertTrue(driver.manage().timeouts().getImplicitWaitTimeout().toSeconds() == 10);

💡 Hint

Check the method to get implicit wait timeout and compare durations properly.

Option D correctly compares the implicit wait timeout in seconds using getImplicitWaitTimeout() and toSeconds(). Option D is invalid because getImplicitWaitTimeout() returns a Duration, but assertEquals expects exact object equality which may fail. Option D uses a non-existent method. Option D compares Duration.ofMillis(10000) which is correct duration but the method call is invalid.

🔧 Debug

advanced

Why does this Selenium Java test fail despite implicit wait set?

Given this code snippet, the test fails with NoSuchElementException immediately. Why?

Selenium Java

driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));
driver.findElement(By.xpath("//div[@class='dynamic']"));

A The element locator is incorrect or element never appears, so implicit wait cannot find it.

B Implicit wait only works for CSS selectors, not XPath.

C Implicit wait must be set after findElement call, not before.

D Implicit wait only applies to visible elements, not hidden ones.

💡 Hint

Implicit wait retries finding the element until timeout or element found.

If the element locator is wrong or the element never appears, implicit wait will retry until timeout but eventually throw NoSuchElementException. It does not fail immediately unless timeout is zero.

🧠 Conceptual

advanced

What is a limitation of implicit wait in Selenium?

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

A Implicit wait only works for buttons, not input fields or links.

B Implicit wait applies globally and can cause unexpected delays when combined with explicit waits.

C Implicit wait automatically retries failed assertions during tests.

D Implicit wait can only be set once per WebDriver instance and cannot be changed.

💡 Hint

Think about how implicit wait affects all element searches and interacts with explicit waits.

Implicit wait applies globally to all findElement calls and can cause unexpected delays or conflicts when used with explicit waits. It does not discriminate element types, does not retry assertions, and can be changed anytime.

❓ framework

expert

How to correctly combine implicit and explicit waits in Selenium Java?

You want to use both implicit and explicit waits in your Selenium Java tests. Which approach is best to avoid timing issues?

A Use implicit wait for all elements and explicit waits only for alerts.

B Set implicit wait to 10 seconds and explicit waits to 5 seconds for faster tests.

C Set implicit wait to zero and use explicit waits only for specific elements.

D Set implicit wait and explicit waits to the same timeout value to synchronize them.

💡 Hint

Implicit and explicit waits can interfere if both are set with non-zero values.

Best practice is to set implicit wait to zero when using explicit waits to avoid unexpected delays and conflicts. Using explicit waits only where needed gives precise control.

Practice

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

easy

A. To set a global wait time for all element searches

B. To wait for a specific element only once

C. To pause the test execution for a fixed time always

D. To speed up the test execution by skipping waits

Solution

1. Step 1: Understand implicit wait behavior

   Implicit wait tells WebDriver to wait a set time when searching for elements before throwing an error.

2. Step 2: Identify the scope of implicit wait

   It applies globally to all element searches, not just one element or fixed pauses.

3. Final Answer:

   To set a global wait time for all element searches -> Option A

4. Quick Check:

   Implicit wait = global element search wait [OK]

Hint: Implicit wait applies to all element searches globally [OK]

Common Mistakes:

• Thinking implicit wait pauses test always
• Confusing implicit wait with explicit wait
• Assuming it waits for only one element

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

easy

A. driver.manage().timeouts().implicitlyWait(10);

B. driver.setImplicitWait(10);

C. driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));

D. driver.wait(10, TimeUnit.SECONDS);

Solution

1. Step 1: Recall correct method signature

   Since Selenium 4, implicit wait requires a Duration object, e.g., Duration.ofSeconds(10).

2. Step 2: Check each option's correctness

   driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10)); uses the correct method with Duration. driver.manage().timeouts().implicitlyWait(10); misses Duration, C and D are invalid methods.

3. Final Answer:

   driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10)); -> Option C

4. Quick Check:

   Implicit wait needs Duration parameter [OK]

Hint: Use Duration.ofSeconds() for implicit wait time [OK]

Common Mistakes:

• Passing int directly instead of Duration
• Using non-existent methods like setImplicitWait
• Confusing implicit wait with explicit wait syntax

3. What will happen if you set an implicit wait of 5 seconds and try to find an element that appears after 3 seconds?

medium

A. The driver will wait up to 5 seconds and find the element after 3 seconds

B. The element will be found immediately without waiting

C. The driver will throw NoSuchElementException immediately

D. The driver will wait exactly 5 seconds before finding the element

Solution

1. Step 1: Understand implicit wait timing

   Implicit wait waits up to the specified time for an element to appear before failing.

2. Step 2: Apply to the scenario

   The element appears after 3 seconds, which is less than 5 seconds, so the driver finds it after waiting 3 seconds.

3. Final Answer:

   The driver will wait up to 5 seconds and find the element after 3 seconds -> Option A

4. Quick Check:

   Implicit wait waits max time, stops early if found [OK]

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

Common Mistakes:

• Assuming immediate find without wait
• Thinking it always waits full time
• Expecting immediate exception if element delayed

4. You wrote this code snippet to set implicit wait:

driver.manage().timeouts().implicitlyWait(10);

But your test throws a compilation error. What is the likely cause?

medium

A. You must import java.util.concurrent.TimeUnit for implicit wait

B. Implicit wait requires a Duration parameter, not an int

C. The method implicitlyWait() does not exist in WebDriver

D. Implicit wait cannot be set after driver initialization

Solution

1. Step 1: Check method signature in Selenium 4+

   Implicit wait expects a Duration object, not a plain int.

2. Step 2: Identify cause of compilation error

   Passing int causes compilation failure because no matching method exists.

3. Final Answer:

   Implicit wait requires a Duration parameter, not an int -> Option B

4. Quick Check:

   Implicit wait needs Duration, not int [OK]

Hint: Use Duration.ofSeconds() to avoid compilation errors [OK]

Common Mistakes:

• Passing int instead of Duration
• Missing import for Duration class
• Assuming TimeUnit import fixes implicit wait

5. You set an implicit wait of 8 seconds in your test. Later, you add an explicit wait of 5 seconds for a specific element. What is the effective wait time when locating that element?

hard

A. 0 seconds, because waits cancel each other out

B. 8 seconds, because implicit wait always overrides explicit wait

C. 13 seconds, sum of implicit and explicit waits

D. 5 seconds, because explicit wait overrides implicit wait for that element

Solution

1. Step 1: Understand interaction of implicit and explicit waits

   Explicit wait applies to specific elements and overrides implicit wait for that action.

2. Step 2: Determine effective wait time

   Explicit wait of 5 seconds is used for that element, ignoring the 8-second implicit wait.

3. Final Answer:

   5 seconds, because explicit wait overrides implicit wait for that element -> Option D

4. Quick Check:

   Explicit wait overrides implicit wait [OK]

Hint: Explicit wait overrides implicit wait for targeted elements [OK]

Common Mistakes:

• Adding implicit and explicit wait times together
• Assuming implicit wait always dominates
• Thinking waits cancel each other