Why form testing validates user workflows in Selenium Java - Test Execution Impact

Test Overview

This test checks if a user can successfully fill out and submit a login form. It verifies that the form accepts valid input and leads to the expected page, ensuring the user workflow works correctly.

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.assertEquals;

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

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

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

        WebElement usernameInput = wait.until(ExpectedConditions.presenceOfElementLocated(By.id("username")));
        WebElement passwordInput = driver.findElement(By.id("password"));
        WebElement submitButton = driver.findElement(By.id("submit-btn"));

        usernameInput.sendKeys("validUser");
        passwordInput.sendKeys("validPass123");
        submitButton.click();

        wait.until(ExpectedConditions.urlContains("/dashboard"));
        String currentUrl = driver.getCurrentUrl();
        assertEquals("https://example.com/dashboard", currentUrl, "User should be redirected to dashboard after login");
    }

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

Execution Trace - 8 Steps

Step	Action	System State	Assertion	Result
1	Test starts and Chrome browser opens	Browser window is open and ready	—	PASS
2	Navigates to https://example.com/login	Login page is loaded with username, password fields and submit button visible	Waits until username input is present	PASS
3	Finds username, password input fields and submit button	All form elements are located and interactable	—	PASS
4	Enters 'validUser' into username field	Username field contains 'validUser'	—	PASS
5	Enters 'validPass123' into password field	Password field contains 'validPass123'	—	PASS
6	Clicks the submit button	Form is submitted, page starts loading	—	PASS
7	Waits until URL contains '/dashboard'	Browser navigates to dashboard page	Checks current URL equals 'https://example.com/dashboard'	PASS
8	Test ends and browser closes	Browser window is closed	—	PASS

Failure Scenario

Failing Condition: If the submit button is not found or clicking it does not redirect to the dashboard page

Execution Trace Quiz - 3 Questions

What does the test verify after clicking the submit button?

A That an error message appears on the login page

B That the username field is cleared

C That the browser URL changes to the dashboard page

D That the submit button becomes disabled

Key Result

Testing form submission validates the entire user workflow from input to navigation, ensuring the app behaves as a user expects.

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