Multi-page navigation flow in Selenium Java

Introduction

Multi-page navigation flow helps test if a user can move through different pages on a website smoothly.

When testing an online shopping site from homepage to product page to checkout.

When verifying a user can log in, go to their profile, and then log out.

When checking a multi-step form that spans several pages.

When ensuring links between pages work correctly.

When testing navigation menus that lead to different sections.

Syntax

Selenium Java

driver.get("https://example.com/page1");
driver.findElement(By.id("nextPageButton")).click();
String currentUrl = driver.getCurrentUrl();

Use driver.get() to open a page.

Use findElement and click() to move to the next page.

Examples

Navigate from home page to About Us page by clicking a link.

Selenium Java

driver.get("https://example.com/home");
driver.findElement(By.linkText("About Us")).click();

Navigate to login page and submit login form to go to user dashboard.

Selenium Java

driver.get("https://example.com/login");
driver.findElement(By.name("username")).sendKeys("user1");
driver.findElement(By.name("password")).sendKeys("pass123");
driver.findElement(By.cssSelector("button[type='submit']")).click();

Sample Program

This test opens the homepage, clicks to go to the products page, then clicks a product to see details. It checks URLs and page titles to confirm navigation worked.

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;

public class MultiPageNavigationTest {
    public static void main(String[] args) {
        System.setProperty("webdriver.chrome.driver", "path/to/chromedriver");
        WebDriver driver = new ChromeDriver();
        try {
            // Open homepage
            driver.get("https://example.com/home");
            // Click link to go to products page
            driver.findElement(By.linkText("Products")).click();
            // Verify URL contains 'products'
            String url = driver.getCurrentUrl();
            if (!url.contains("products")) {
                System.out.println("Test Failed: Not on products page");
                return;
            }
            // Click first product to go to product details
            driver.findElement(By.cssSelector(".product-item:first-child a")).click();
            // Verify product details page loaded
            String title = driver.getTitle();
            if (!title.contains("Product Details")) {
                System.out.println("Test Failed: Product details page not loaded");
                return;
            }
            System.out.println("Test Passed: Multi-page navigation flow works");
        } finally {
            driver.quit();
        }
    }
}

Important Notes

Always wait for page elements to load before interacting to avoid errors.

Use clear locators like By.id or By.cssSelector for stable tests.

Close the browser with driver.quit() to free resources.

Summary

Multi-page navigation tests check if users can move through pages correctly.

Use Selenium commands to open pages and click links or buttons.

Verify navigation by checking URLs or page titles.

Practice

1. What is the main purpose of multi-page navigation testing in Selenium?

easy

A. To check database connections

B. To verify users can move through pages correctly

C. To test API responses

D. To validate CSS styles on a page

Solution

1. Step 1: Understand multi-page navigation testing

   It focuses on checking if users can move from one page to another as expected.

2. Step 2: Identify the correct purpose

   Among the options, only verifying page navigation matches this goal.

3. Final Answer:

   To verify users can move through pages correctly -> Option B

4. Quick Check:

   Multi-page navigation = verify page moves [OK]

Hint: Focus on user movement between pages [OK]

Common Mistakes:

• Confusing navigation testing with API or database testing
• Thinking CSS validation is part of navigation
• Ignoring the user flow aspect

2. Which Selenium Java command is used to navigate to a new URL in a multi-page test?

easy

A. driver.get("https://example.com")

B. driver.click("https://example.com")

C. driver.navigateTo("https://example.com")

D. driver.openPage("https://example.com")

Solution

1. Step 1: Recall Selenium command to open URL

   The correct method is driver.get(url) to load a page.

2. Step 2: Check options for correct syntax

   Only driver.get("https://example.com") is valid Selenium Java syntax.

3. Final Answer:

   driver.get("https://example.com") -> Option A

4. Quick Check:

   Open URL = driver.get() [OK]

Hint: Use driver.get() to open URLs [OK]

Common Mistakes:

• Using non-existent methods like navigateTo or openPage
• Trying to click URLs directly
• Confusing navigation commands with click actions

3. Given the code snippet:

driver.get("https://example.com/page1");
driver.findElement(By.id("nextBtn")).click();
String currentUrl = driver.getCurrentUrl();

What will currentUrl contain after execution if clicking the button navigates to page2?

medium

A. "https://example.com/page1"

B. null

C. Throws NoSuchElementException

D. "https://example.com/page2"

Solution

1. Step 1: Understand navigation flow in code

   The driver opens page1, then clicks a button that navigates to page2.

2. Step 2: Check what getCurrentUrl() returns after navigation

   It returns the URL of the current page, which should be page2 after clicking.

3. Final Answer:

   "https://example.com/page2" -> Option D

4. Quick Check:

   After click, URL updates to new page [OK]

Hint: getCurrentUrl() shows current page URL [OK]

Common Mistakes:

• Assuming URL stays the same after navigation
• Confusing getCurrentUrl() with getPageSource()
• Thinking click throws exception without checking element presence

4. Identify the error in this Selenium Java code for multi-page navigation:

driver.get("https://example.com/home");
WebElement link = driver.findElement(By.className("nav-link"));
link.click();
String title = driver.getTitle();
assert title.equals("Home Page");

medium

A. Missing driver.quit() after test

B. Incorrect assertion method syntax

C. Using className locator without checking multiple matches

D. Using getTitle() instead of getCurrentUrl()

Solution

1. Step 1: Analyze locator usage

   Using By.className("nav-link") may find multiple elements, causing ambiguity.

2. Step 2: Check other code parts

   Assertion syntax is correct, driver.quit() is optional, and getTitle() is valid for title check.

3. Final Answer:

   Using className locator without checking multiple matches -> Option C

4. Quick Check:

   className may match many elements [OK]

Hint: Ensure locators uniquely identify elements [OK]

Common Mistakes:

• Ignoring that className can match multiple elements
• Thinking getTitle() is wrong for title checks
• Believing driver.quit() is mandatory in every snippet

5. You want to test a multi-page flow where after login, the user clicks a menu to open a settings page, then clicks a logout button. Which Selenium Java approach correctly verifies the flow?

hard

A. Use driver.get() for login page, findElement().sendKeys() for login, click menu link, verify settings URL, click logout, verify login URL

B. Use driver.navigate().refresh() after each click to ensure page loads

C. Use driver.get() only once at login, then use JavaScript to change URLs for other pages

D. Use driver.findElement(By.tagName("button")).click() for all clicks without verifying page changes

Solution

1. Step 1: Outline correct multi-page test steps

   Start at login page, perform login, navigate via clicks, verify URLs after each step.

2. Step 2: Evaluate options for best practice

   Use driver.get() for login page, findElement().sendKeys() for login, click menu link, verify settings URL, click logout, verify login URL follows proper navigation and verification. Others misuse refresh, JavaScript URL changes, or skip verification.

3. Final Answer:

   Use driver.get() for login page, findElement().sendKeys() for login, click menu link, verify settings URL, click logout, verify login URL -> Option A

4. Quick Check:

   Navigate and verify URLs step-by-step [OK]

Hint: Navigate and verify each page URL after clicks [OK]

Common Mistakes:

• Refreshing unnecessarily after clicks
• Changing URLs via JavaScript instead of real navigation
• Clicking without verifying page changes