Verify synchronization eliminates timing failures on login page

Preconditions (2)

Step 1: Open the login page URL

Step 2: Wait until the email input field is visible

Step 3: Enter 'user@example.com' in the email input field

Step 4: Wait until the password input field is visible

Step 5: Enter 'Password123' in the password input field

Step 6: Wait until the login button is clickable

Step 7: Click the login button

Step 8: Wait until the dashboard page URL is loaded

Step 9: Verify the dashboard page contains the welcome message 'Welcome, User!'

✅ Expected Result: User successfully logs in without timing failures and sees the welcome message on the dashboard page

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Verify email input field is visible before typing

Verify password input field is visible before typing

Verify login button is clickable before clicking

Verify dashboard URL is loaded after login

Verify welcome message text is present on dashboard

Best Practices:

Use explicit waits (WebDriverWait) for synchronization

Avoid Thread.sleep() for waiting

Use By locators with IDs or names for stable element identification

Use Page Object Model to separate page actions and locators

Automated Solution

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.assertEquals;
import java.time.Duration;

public class LoginTest {
    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeEach
    public void setUp() {
        driver = new ChromeDriver();
        wait = new WebDriverWait(driver, Duration.ofSeconds(10));
    }

    @Test
    public void testLoginWithSynchronization() {
        driver.get("https://example.com/login");

        // Wait for email input to be visible
        WebElement emailInput = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("email")));
        emailInput.sendKeys("user@example.com");

        // Wait for password input to be visible
        WebElement passwordInput = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("password")));
        passwordInput.sendKeys("Password123");

        // Wait for login button to be clickable
        WebElement loginButton = wait.until(ExpectedConditions.elementToBeClickable(By.id("loginBtn")));
        loginButton.click();

        // Wait for dashboard URL
        wait.until(ExpectedConditions.urlContains("/dashboard"));

        // Verify welcome message
        WebElement welcomeMessage = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("welcomeMsg")));
        assertEquals("Welcome, User!", welcomeMessage.getText());
    }

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

This test script uses Selenium WebDriver with Java to automate the login process.

We use explicit waits (WebDriverWait) before interacting with elements. This ensures the elements are ready (visible or clickable) before we act on them, which prevents timing failures.

First, we wait for the email input field to be visible, then enter the email. Next, we wait for the password input field to be visible, then enter the password. Then, we wait for the login button to be clickable before clicking it.

After clicking login, we wait until the URL contains '/dashboard' to confirm navigation. Finally, we wait for the welcome message to be visible and verify its text.

Using explicit waits synchronizes the test steps with the web page's state, eliminating timing failures caused by elements not being ready.

The setup and teardown methods initialize and close the browser cleanly.

Common Mistakes - 3 Pitfalls

Using Thread.sleep() instead of explicit waits

Using brittle locators like absolute XPath

Not waiting for elements before interacting

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials to verify login success or failure.

Show Hint