Thread.sleep vs proper waits in Selenium Java - Test Execution Compared

Test Overview

This test demonstrates the difference between using Thread.sleep and proper Selenium waits (WebDriverWait) to wait for an element to appear before clicking it. It verifies that the element is clickable and the click action succeeds.

Test Code - JUnit with Selenium WebDriver

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.support.ui.ExpectedConditions;
import org.openqa.selenium.support.ui.WebDriverWait;
import org.junit.jupiter.api.AfterEach;
import org.junit.jupiter.api.BeforeEach;
import org.junit.jupiter.api.Test;
import static org.junit.jupiter.api.Assertions.assertTrue;
import java.time.Duration;

public class WaitComparisonTest {
    private WebDriver driver;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        driver.get("https://example.com/delayed-button");
    }

    @Test
    public void testUsingThreadSleep() throws InterruptedException {
        // Wait fixed 5 seconds
        Thread.sleep(5000);
        WebElement button = driver.findElement(By.id("delayedButton"));
        button.click();
        WebElement message = driver.findElement(By.id("message"));
        assertTrue(message.isDisplayed(), "Message should be displayed after click");
    }

    @Test
    public void testUsingWebDriverWait() {
        WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
        WebElement button = wait.until(ExpectedConditions.elementToBeClickable(By.id("delayedButton")));
        button.click();
        WebElement message = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("message")));
        assertTrue(message.isDisplayed(), "Message should be displayed after click");
    }

    @AfterEach
    public void tearDown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

Execution Trace - 11 Steps

Step	Action	System State	Assertion	Result
1	Test starts - Chrome browser opens and navigates to https://example.com/delayed-button	Browser shows page with a button that appears after delay	—	PASS
2	testUsingThreadSleep: Thread.sleep(5000) pauses test for 5 seconds	Browser waits with page loaded, button expected to appear after delay	—	PASS
3	Find element with id 'delayedButton' using driver.findElement	Button is present and visible after sleep	Element found successfully	PASS
4	Click the 'delayedButton'	Button clicked, page updates to show message	—	PASS
5	Find element with id 'message' and check if displayed	Message element visible on page	assertTrue(message.isDisplayed()) verifies message is visible	PASS
6	TestUsingWebDriverWait: Create WebDriverWait with 10 seconds timeout	Browser ready on same page	—	PASS
7	Wait until 'delayedButton' is clickable using ExpectedConditions	Waits dynamically until button appears and is clickable	Wait confirms button is clickable before proceeding	PASS
8	Click the 'delayedButton'	Button clicked, page updates to show message	—	PASS
9	Wait until 'message' element is visible	Waits dynamically until message appears	Wait confirms message is visible before assertion	PASS
10	Assert message is displayed	Message visible on page	assertTrue(message.isDisplayed()) verifies message is visible	PASS
11	Test ends - Browser closes	Browser closed, resources freed	—	PASS

Failure Scenario

Failing Condition: Using Thread.sleep with insufficient wait time causes element not to be found

Execution Trace Quiz - 3 Questions

Why is using WebDriverWait better than Thread.sleep in Selenium tests?

A Thread.sleep is faster because it waits a fixed time

B WebDriverWait waits only as long as needed for a condition, making tests faster and more reliable

C WebDriverWait does not wait at all

D Thread.sleep automatically retries finding elements

Key Result

Always prefer explicit waits like WebDriverWait over fixed waits like Thread.sleep to make tests more reliable and faster by waiting only as long as needed.

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