Why browser control drives test flow in Selenium Java - Automation Benefits in Action

Verify login flow controls test execution by browser state

Preconditions (2)

Step 1: Open browser and navigate to login page URL

Step 2: Enter '[e-mail]' in the email input field

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

Step 4: Click the login button

Step 5: Wait for the dashboard page to load

Step 6: Verify the URL is the dashboard URL

Step 7: Verify the welcome message is displayed

✅ Expected Result: Test should proceed step-by-step controlled by browser state. After login button click, test waits for dashboard page load before verifying URL and welcome message. If page does not load, test should fail.

Automation Requirements - Selenium WebDriver with Java and TestNG

Assertions Needed:

Verify current URL matches expected dashboard URL

Verify welcome message element is visible and contains expected text

Best Practices:

Use explicit waits to wait for page elements or URL changes

Use By locators with IDs or stable attributes

Structure test steps sequentially to reflect browser state changes

Use TestNG assertions for validation

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.testng.Assert;
import org.testng.annotations.AfterClass;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import java.time.Duration;

public class LoginFlowTest {
    WebDriver driver;
    WebDriverWait wait;
    String loginUrl = "https://example.com/login";
    String dashboardUrl = "https://example.com/dashboard";

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

    @Test
    public void testLoginFlowControlsTestExecution() {
        // Step 1: Open login page
        driver.get(loginUrl);

        // Step 2: Enter email
        WebElement emailInput = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("email")));
        emailInput.sendKeys("[e-mail]");

        // Step 3: Enter password
        WebElement passwordInput = driver.findElement(By.id("password"));
        passwordInput.sendKeys("Password123");

        // Step 4: Click login button
        WebElement loginButton = driver.findElement(By.id("loginBtn"));
        loginButton.click();

        // Step 5: Wait for dashboard page to load by URL
        wait.until(ExpectedConditions.urlToBe(dashboardUrl));

        // Step 6: Verify URL
        String currentUrl = driver.getCurrentUrl();
        Assert.assertEquals(currentUrl, dashboardUrl, "URL after login should be dashboard URL");

        // Step 7: Verify welcome message
        WebElement welcomeMsg = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("welcomeMessage")));
        Assert.assertTrue(welcomeMsg.getText().contains("Welcome"), "Welcome message should be displayed");
    }

    @AfterClass
    public void teardown() {
        if (driver != null) {
            driver.quit();
        }
    }
}

This test script uses Selenium WebDriver with Java and TestNG to automate the login flow.

We start by opening the login page URL. Then we locate the email and password fields by their IDs and enter the test credentials.

After clicking the login button, the test uses an explicit wait to pause execution until the browser URL changes to the dashboard URL. This shows how controlling the browser state drives the test flow step-by-step.

Once the dashboard page loads, the test asserts the URL is correct and that a welcome message is visible with expected text.

Explicit waits ensure the test does not proceed until the browser is ready, preventing flaky failures.

The @BeforeClass and @AfterClass methods setup and close the browser cleanly.

Common Mistakes - 3 Pitfalls

Using Thread.sleep() instead of explicit waits

Using brittle XPath locators that break easily

Not waiting for page load before asserting URL or elements

Bonus Challenge

Now add data-driven testing with 3 different sets of login credentials (valid and invalid).

Show Hint

Practice

1. Why is controlling the browser important in Selenium test automation?

easy

A. It automatically fixes bugs in the web application.

B. It speeds up the test execution by skipping page loads.

C. It ensures test steps run in the correct order and interact with the page properly.

D. It allows tests to run without opening a browser window.

Solution

1. Step 1: Understand browser control role

   Browser control directs how tests interact with web pages, ensuring actions happen in the right sequence.

2. Step 2: Recognize importance for test reliability

   Without proper control, tests may fail or behave unpredictably because they don't wait for pages or elements.

3. Final Answer:

   It ensures test steps run in the correct order and interact with the page properly. -> Option C

4. Quick Check:

   Browser control = correct test flow [OK]

Hint: Browser control keeps test steps in order and reliable [OK]

Common Mistakes:

• Thinking browser control speeds tests by skipping loads
• Believing it fixes application bugs automatically
• Assuming tests run without a browser window

2. Which Selenium Java command correctly opens a Chrome browser window?

easy

A. WebDriver driver = new ChromeDriver();

B. WebDriver driver = new FirefoxDriver();

C. WebDriver driver = new SafariDriver();

D. WebDriver driver = new EdgeDriver();

Solution

1. Step 1: Identify browser driver for Chrome

   ChromeDriver is the Selenium class used to control Chrome browser.

2. Step 2: Match correct syntax

   Creating a new ChromeDriver instance opens a Chrome browser window.

3. Final Answer:

   WebDriver driver = new ChromeDriver(); -> Option A

4. Quick Check:

   ChromeDriver opens Chrome browser [OK]

Hint: Use ChromeDriver class to open Chrome browser [OK]

Common Mistakes:

• Using FirefoxDriver to open Chrome
• Confusing SafariDriver or EdgeDriver for Chrome
• Missing 'new' keyword in driver creation

3. What will happen when this Selenium Java code runs?

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
String title = driver.getTitle();
System.out.println(title);

medium

A. It prints an empty string because title is not set.

B. It throws a syntax error because getTitle() is invalid.

C. It opens the browser but does not load the page.

D. It prints the page title of https://example.com.

Solution

1. Step 1: Analyze browser opening and navigation

   driver.get() opens the URL in the browser controlled by ChromeDriver.

2. Step 2: Understand getTitle() usage

   getTitle() returns the current page's title as a string, which is printed.

3. Final Answer:

   It prints the page title of https://example.com. -> Option D

4. Quick Check:

   driver.getTitle() returns page title [OK]

Hint: driver.get() loads page; getTitle() returns its title [OK]

Common Mistakes:

• Thinking getTitle() causes syntax error
• Assuming page does not load after driver.get()
• Believing title variable is empty without assignment

4. Identify the error in this Selenium Java snippet controlling browser flow:

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
driver.findElement(By.id("submit")).click();
driver.quit();
driver.get("https://another.com");

medium

A. Calling driver.get() after driver.quit() causes an error.

B. Missing wait before clicking the submit button.

C. Using By.id() is incorrect syntax.

D. driver.quit() should be called before driver.get() initially.

Solution

1. Step 1: Understand driver.quit() effect

   driver.quit() closes the browser and ends the WebDriver session.

2. Step 2: Analyze subsequent driver.get() call

   Calling driver.get() after quit() tries to use a closed session, causing an error.

3. Final Answer:

   Calling driver.get() after driver.quit() causes an error. -> Option A

4. Quick Check:

   driver.quit() ends session; no further commands allowed [OK]

Hint: Don't use driver after quit() closes browser [OK]

Common Mistakes:

• Ignoring that driver.quit() ends the session
• Thinking missing wait causes immediate error here
• Believing By.id() syntax is wrong

5. In Selenium Java, why must browser control commands be sequenced carefully when testing a login page?

hard

A. Because Selenium automatically retries failed commands out of order.

B. Because actions like entering username, password, and clicking login must happen in order to simulate a real user.

C. Because browser control commands run in parallel threads by default.

D. Because the browser ignores commands if they are not in alphabetical order.

Solution

1. Step 1: Understand test flow for login

   Login requires entering username, password, then clicking login button in sequence.

2. Step 2: Recognize browser control enforces order

   Selenium sends commands to browser in order to mimic user actions correctly and avoid errors.

3. Final Answer:

   Because actions like entering username, password, and clicking login must happen in order to simulate a real user. -> Option B

4. Quick Check:

   Browser control enforces user action order [OK]

Hint: Test steps must follow user action order for success [OK]

Common Mistakes:

• Thinking Selenium retries commands out of order automatically
• Believing commands run in parallel threads by default
• Assuming browser ignores command order