Thread.sleep vs proper waits in Selenium Java - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to pause the test execution for 3 seconds using Thread.sleep.

Selenium Java

Thread.sleep([1]);

Drag options to blanks, or click blank then click option'

A300

B3

C3000

D30

Attempts:

3 left

💡 Hint

Common Mistakes

Using 3 instead of 3000 causes the sleep to be too short.

Using 30 or 300 is not the correct duration for 3 seconds.

Thread.sleep expects time in milliseconds. 3000 ms equals 3 seconds.

2fill in blank

medium

Complete the code to create an explicit wait that waits up to 10 seconds.

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds([1]));

Drag options to blanks, or click blank then click option'

A10

B20

C5

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Using 5 or 15 seconds when the requirement is 10 seconds.

Confusing milliseconds with seconds.

The explicit wait is set to 10 seconds using Duration.ofSeconds(10).

3fill in blank

hard

Fix the error in the code to wait until the element with id 'submit' is clickable.

Selenium Java

wait.until(ExpectedConditions.[1](By.id("submit")));

Drag options to blanks, or click blank then click option'

AalertIsPresent

BvisibilityOfElementLocated

CpresenceOfElementLocated

DelementToBeClickable

Attempts:

3 left

💡 Hint

Common Mistakes

Using visibilityOfElementLocated waits only for visibility, not clickability.

Using presenceOfElementLocated waits only for presence in DOM.

To wait until an element is clickable, use ExpectedConditions.elementToBeClickable.

4fill in blank

hard

Fill both blanks to create a fluent wait that polls every 2 seconds and ignores NoSuchElementException.

Selenium Java

Wait<WebDriver> wait = new FluentWait<>(driver)
    .withTimeout(Duration.ofSeconds([1]))
    .pollingEvery(Duration.ofSeconds([2]))
    .ignoring(NoSuchElementException.class);

Drag options to blanks, or click blank then click option'

A30

B2

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping timeout and polling interval values.

Using too short or too long polling intervals.

The fluent wait waits up to 30 seconds and polls every 2 seconds, ignoring NoSuchElementException.

5fill in blank

hard

Fill all three blanks to create a stream collector that maps element IDs to their text if text length is greater than 3.

Selenium Java

Map<String, String> texts = elements.stream()
    .filter(e -> e.getText().length() [1] 3)
    .collect(Collectors.toMap(e -> e.getAttribute([2]), e -> e.[3]()));

Drag options to blanks, or click blank then click option'

A>

B"id"

CgetText

D<

Attempts:

3 left

💡 Hint

Common Mistakes

Using '<' instead of '>' in the filter.

Using wrong attribute name instead of 'id'.

Calling wrong method instead of getText().

The filter checks if text length is greater than 3, keys are element IDs, and values are element texts.

Practice

1. What is the main disadvantage of using Thread.sleep() in Selenium tests?

easy

A. It improves test speed by skipping unnecessary waits.

B. It automatically waits until an element is visible.

C. It retries the action multiple times until success.

D. It pauses the test for a fixed time, which can slow down or cause flaky tests.

Solution

1. Step 1: Understand Thread.sleep() behavior

   Thread.sleep() pauses the test for a fixed amount of time regardless of page state.

2. Step 2: Identify the impact on tests

   This fixed wait can slow tests or cause failures if the wait is too short or unnecessarily long.

3. Final Answer:

   It pauses the test for a fixed time, which can slow down or cause flaky tests. -> Option D

4. Quick Check:

   Fixed wait = slow or flaky tests [OK]

Hint: Fixed waits waste time or cause failures, avoid them [OK]

Common Mistakes:

• Thinking Thread.sleep waits only until element appears
• Assuming Thread.sleep retries actions automatically
• Believing Thread.sleep speeds up tests

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

easy

A. driver.wait(10);

B. Thread.sleep(10);

C. WebDriverWait wait = new WebDriverWait(driver, 10);

D. Wait wait = new Wait(driver, 10);

Solution

1. Step 1: Recall explicit wait syntax in Selenium Java

   The correct way is to create a WebDriverWait object with driver and timeout in seconds.

2. Step 2: Check each option

   WebDriverWait wait = new WebDriverWait(driver, 10); uses correct class and constructor. The remaining options use incorrect syntax or classes.

3. Final Answer:

   WebDriverWait wait = new WebDriverWait(driver, 10); -> Option C

4. Quick Check:

   Explicit wait syntax = WebDriverWait wait = new WebDriverWait(driver, 10); [OK]

Hint: Use WebDriverWait(driver, seconds) for explicit waits [OK]

Common Mistakes:

• Using Thread.sleep instead of WebDriverWait
• Calling driver.wait() which doesn't exist
• Using incorrect class names like Wait

3. What will happen when the following code runs?

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("submitBtn")));
System.out.println("Button is visible");

medium

A. The code waits up to 5 seconds for the button to be visible, then prints the message.

B. The code waits exactly 5 seconds, then prints the message regardless of button visibility.

C. The code immediately prints the message without waiting.

D. The code throws a syntax error due to wrong wait syntax.

Solution

1. Step 1: Analyze the explicit wait usage

   The code creates a WebDriverWait with 5 seconds timeout and waits until the element with id "submitBtn" is visible.

2. Step 2: Understand wait behavior

   The wait stops as soon as the element is visible (up to 5 seconds). If the condition is met, it prints the message.

3. Final Answer:

   The code waits up to 5 seconds for the button to be visible, then prints the message. -> Option A

4. Quick Check:

   Explicit wait waits until condition or timeout [OK]

Hint: Explicit wait stops early when condition met [OK]

Common Mistakes:

• Thinking wait always waits full timeout
• Confusing explicit wait with Thread.sleep
• Assuming syntax error in correct code

4. Identify the problem in this Selenium Java code snippet:

Thread.sleep(5000);
driver.findElement(By.id("loginBtn")).click();

medium

A. Using Thread.sleep causes fixed wait; better to use explicit wait for element clickability.

B. The click() method is incorrect syntax.

C. The locator By.id("loginBtn") is invalid.

D. Thread.sleep should be replaced with implicit wait only.

Solution

1. Step 1: Review use of Thread.sleep before clicking

   The code waits a fixed 5 seconds before clicking, which can slow tests or fail if element appears later.

2. Step 2: Suggest better approach

   Using explicit wait to wait until the button is clickable is more reliable and efficient.

3. Final Answer:

   Using Thread.sleep causes fixed wait; better to use explicit wait for element clickability. -> Option A

4. Quick Check:

   Fixed wait replaced by explicit wait [OK]

Hint: Replace Thread.sleep with explicit wait for clickable element [OK]

Common Mistakes:

• Thinking click() syntax is wrong
• Believing locator is invalid without evidence
• Confusing implicit wait as better than explicit wait here

5. You want to wait for a dynamic element to appear but avoid unnecessary delays. Which approach is best in Selenium Java?

hard

A. Use Thread.sleep(10000); to wait 10 seconds always.

B. Use explicit wait with WebDriverWait until element is visible, timeout 10 seconds.

C. Use implicit wait set to 10 seconds once at driver setup.

D. Use a loop with Thread.sleep(1000) checking element presence manually.

Solution

1. Step 1: Compare waiting strategies for dynamic elements

   Thread.sleep always waits fixed time, implicit wait applies globally but may not be precise, looping with sleep is manual and error-prone.

2. Step 2: Identify best practice

   Explicit wait with WebDriverWait waits only as long as needed until element is visible or timeout, making tests faster and stable.

3. Final Answer:

   Use explicit wait with WebDriverWait until element is visible, timeout 10 seconds. -> Option B

4. Quick Check:

   Explicit wait = best for dynamic elements [OK]

Hint: Explicit wait waits only as long as needed [OK]

Common Mistakes:

• Using fixed Thread.sleep causing slow tests
• Relying only on implicit wait for dynamic elements
• Manually looping with sleep instead of explicit wait