DEV Community: master_blaster

The Wait Strategy (Interview Gold)

master_blaster — Thu, 28 May 2026 10:58:49 +0000

Stop Using Thread.sleep(): The Right Way to Handle Synchronization in Selenium

When you run an automation script, your Java code executes at lightning speed. However, web elements take time to render due to network latency, server response times, or heavy JavaScript execution.

If your script tries to click a button before the browser loads it, you get the infamous NoSuchElementException.

The easiest fix seems to be adding Thread.sleep(5000). But hardcoding pauses is an anti-pattern that slows down your test suites. Here is how to handle synchronization like a pro.

❌ The Problem with Thread.sleep()

Thread.sleep() forces the execution thread to stop entirely for a fixed duration.

If an element takes 1 second to load, but you set a sleep of 5 seconds, you waste 4 seconds.
Over a suite of 100 tests, these wasted seconds compound into hours of idle execution time.

The Solution: Explicit Waits

Instead of blindly sleeping, use Explicit Waits via WebDriverWait. This tells Selenium to poll the browser dynamically. If the element loads in 0.5 seconds, the script interacts with it instantly and moves on.

# Quick Tip: How to Handle Dynamic Dropdowns in Selenium Java Cleanly When automating web applications, handling dropdowns is one of the first tasks you'll encounter. While standard dropdowns use the HTML `` tag, modern web apps frequently use

master_blaster — Thu, 28 May 2026 10:50:32 +0000

How to Set Up a Clean Page Object Model (POM) in Selenium with Java

master_blaster — Wed, 27 May 2026 17:48:40 +0000

How to Structure a Clean Selenium-Java Automation Framework Using Page Object Model

When you first start with automation testing, it’s easy to write all your test scripts in a single, massive file. But as your project grows, web elements change, and maintenance becomes a nightmare.

That is where the Page Object Model (POM) comes to the rescue. In this quick guide, we’ll look at how to cleanly separate your test logic from your page layout using Java and Selenium.

🚀 Why Page Object Model?

POM is a design pattern where every web page in your application has a corresponding Page Class. This class holds the element locators and the actions that can be performed on that page.

The main benefits:

Reusability: Write a locator once, use it across multiple tests.
Easy Maintenance: If a button ID changes, you only fix it in one place, not in twenty different test scripts.
Readability: Your actual test files look like plain English steps.

💻 The Code Structure

Let’s look at a practical example: automating a simple login flow.

1. The Page Object Class

This class maps out the login page. It contains the web elements (locators) and the methods to interact with them.


java
package pages;

import org.openqa.selenium.By;
import org.openqa.git.WebDriver;

public class LoginPage {
    private WebDriver driver;

    // 1. Locate the Web Elements using private variables
    private By usernameField = By.id("username");
    private By passwordField = By.id("password");
    private By loginButton = By.id("submit-btn");

    // Constructor to initialize the driver
    public LoginPage(WebDriver driver) {
        this.driver = driver;
    }

    // 2. Action Methods
    public void enterUsername(String username) {
        driver.findElement(usernameField).sendKeys(username);
    }

    public void enterPassword(String password) {
        driver.findElement(passwordField).sendKeys(password);
    }

    public void clickLogin() {
        driver.findElement(loginButton).click();
    }
}