Why form testing validates user workflows in Selenium Java - Automation Benefits in Action

Validate user workflow by testing the login form

Preconditions (2)

Step 1: Enter 'testuser' in the username input field with id 'username'

Step 2: Enter 'Test@1234' in the password input field with id 'password'

Step 3: Click the login button with id 'loginBtn'

Step 4: Wait for the dashboard page to load

Step 5: Verify that the URL is 'https://example.com/dashboard'

Step 6: Verify that the welcome message with id 'welcomeMsg' contains text 'Welcome, testuser!'

✅ Expected Result: User is successfully logged in and redirected to the dashboard page with a welcome message displayed

Automation Requirements - Selenium WebDriver with Java

Assertions Needed:

Verify URL after login matches expected dashboard URL

Verify welcome message text is correct

Best Practices:

Use explicit waits to wait for elements or page load

Use By.id locators for stable element identification

Use assertions from TestNG or JUnit for validation

Structure code with setup and teardown methods

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 LoginFormTest {
    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeClass
    public void setUp() {
        // Set path to chromedriver executable if needed
        driver = new ChromeDriver();
        wait = new WebDriverWait(driver, Duration.ofSeconds(10));
        driver.manage().window().maximize();
    }

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

        WebElement usernameInput = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("username")));
        usernameInput.sendKeys("testuser");

        WebElement passwordInput = driver.findElement(By.id("password"));
        passwordInput.sendKeys("Test@1234");

        WebElement loginButton = driver.findElement(By.id("loginBtn"));
        loginButton.click();

        // Wait for dashboard URL
        wait.until(ExpectedConditions.urlToBe("https://example.com/dashboard"));

        String currentUrl = driver.getCurrentUrl();
        Assert.assertEquals(currentUrl, "https://example.com/dashboard", "URL after login should be dashboard URL");

        WebElement welcomeMsg = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("welcomeMsg")));
        String welcomeText = welcomeMsg.getText();
        Assert.assertTrue(welcomeText.contains("Welcome, testuser!"), "Welcome message should greet the user");
    }

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

This test script uses Selenium WebDriver with Java and TestNG framework.

Setup: We create a ChromeDriver instance and a WebDriverWait for explicit waits. The browser window is maximized for better visibility.

Test steps: The test navigates to the login page URL. It waits until the username input is visible, then enters the username. It finds the password input and enters the password. Then it clicks the login button.

After clicking login, it waits explicitly until the URL changes to the dashboard URL. This confirms the page navigation happened.

It asserts the current URL matches the expected dashboard URL.

Then it waits for the welcome message element to appear and asserts that the text contains the expected greeting.

Teardown: The browser is closed after the test to clean up.

This structure ensures the test follows the user workflow precisely and validates the form's effect on navigation and UI changes.

Common Mistakes - 4 Pitfalls

Using Thread.sleep() instead of explicit waits

Using brittle XPath locators instead of stable IDs

Not verifying the URL after login

Not closing the browser after test

Bonus Challenge

Now add data-driven testing with 3 different sets of valid username and password inputs

Show Hint

Practice

1. Why is form testing important in validating user workflows?

easy

A. It ensures users can complete tasks step-by-step without errors.

B. It only checks if the form looks good visually.

C. It tests the speed of the website loading.

D. It verifies the server hardware performance.

Solution

1. Step 1: Understand the purpose of form testing

   Form testing focuses on checking if users can fill out forms correctly and complete workflows without issues.

2. Step 2: Identify what form testing validates

   It validates input fields, buttons, error messages, and the overall flow to ensure smooth user experience.

3. Final Answer:

   It ensures users can complete tasks step-by-step without errors. -> Option A

4. Quick Check:

   Form testing = Validate user workflow [OK]

Hint: Form testing checks user steps, not just appearance [OK]

Common Mistakes:

• Confusing form testing with UI design testing
• Thinking form testing checks server speed
• Ignoring error message validation

2. Which Selenium Java code snippet correctly submits a form after filling an input field with id username?

easy

A. driver.findElement(By.name("username")).sendKeys(); driver.submit();

B. driver.findElement(By.id("username")).click(); driver.submit();

C. driver.findElement(By.id("username")).sendKeys("user1"); driver.findElement(By.id("submit")).click();

D. driver.findElement(By.className("username")).sendKeys("user1"); driver.findElement(By.id("submit")).submit();

Solution

1. Step 1: Fill input field correctly

   Use sendKeys("user1") on element found by By.id("username").

2. Step 2: Submit form by clicking submit button

   Click the submit button found by By.id("submit") using click().

3. Final Answer:

   driver.findElement(By.id("username")).sendKeys("user1"); driver.findElement(By.id("submit")).click(); -> Option C

4. Quick Check:

   Correct locator and actions = driver.findElement(By.id("username")).sendKeys("user1"); driver.findElement(By.id("submit")).click(); [OK]

Hint: Use sendKeys then click submit button [OK]

Common Mistakes:

• Calling sendKeys without arguments
• Using submit() on wrong element
• Using incorrect locators like className for id

3. Given this Selenium Java code, what will be the output if the form submission shows a success message with id successMsg?

driver.findElement(By.id("email")).sendKeys("[e-mail]");
driver.findElement(By.id("submitBtn")).click();
String message = driver.findElement(By.id("successMsg")).getText();
System.out.println(message);

medium

A. [e-mail]

B. Empty string

C. NoSuchElementException error

D. Success! Your form has been submitted.

Solution

1. Step 1: Understand the code flow

   The code fills the email field, clicks submit, then reads the success message text.

2. Step 2: Identify expected output

   The success message element with id successMsg contains the text "Success! Your form has been submitted." which is printed.

3. Final Answer:

   Success! Your form has been submitted. -> Option D

4. Quick Check:

   getText() returns success message [OK]

Hint: getText() prints visible message after submit [OK]

Common Mistakes:

• Confusing input value with message text
• Expecting element not present error
• Assuming empty string if message missing

4. What is wrong with this Selenium Java code snippet for form testing?

driver.findElement(By.id("password")).sendKeys();
driver.findElement(By.id("loginBtn")).click();

medium

A. sendKeys() is called without input text, causing an error.

B. Using id locator is incorrect for password field.

C. click() should be called before sendKeys().

D. No error, code works fine.

Solution

1. Step 1: Check sendKeys usage

   sendKeys() requires a string argument to input text; calling it empty causes an error.

2. Step 2: Verify order and locators

   Using id locator is correct and click() after sendKeys() is proper order.

3. Final Answer:

   sendKeys() is called without input text, causing an error. -> Option A

4. Quick Check:

   sendKeys needs argument [OK]

Hint: Always pass text to sendKeys() [OK]

Common Mistakes:

• Calling sendKeys() with no arguments
• Clicking before entering text
• Using wrong locator types

5. In a multi-step form workflow, why is it important to validate each step's form before moving to the next?

hard

A. Because Selenium cannot test multiple steps at once.

B. To catch errors early and prevent invalid data from progressing.

C. To reduce the number of test cases needed overall.

D. Because users prefer to fill all steps at once.

Solution

1. Step 1: Understand multi-step form workflow

   Each step collects data that builds on the previous; errors early can block progress.

2. Step 2: Importance of validating each step

   Validating each step ensures errors are caught early, improving user experience and data quality.

3. Final Answer:

   To catch errors early and prevent invalid data from progressing. -> Option B

4. Quick Check:

   Stepwise validation = catch errors early [OK]

Hint: Validate each step to stop errors early [OK]

Common Mistakes:

• Thinking Selenium limits multi-step testing
• Assuming fewer test cases is better here
• Believing users want all steps at once