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.