Multi-page navigation flow in Selenium Java - Framework Patterns

Framework Mode - Multi-page navigation flow

Folder Structure

src/
└── test/
    └── java/
        └── com/
            └── example/
                ├── pages/
                │   ├── LoginPage.java
                │   ├── DashboardPage.java
                │   └── ProfilePage.java
                ├── tests/
                │   └── NavigationFlowTest.java
                ├── utils/
                │   ├── WebDriverFactory.java
                │   └── WaitUtils.java
                └── config/
                    └── TestConfig.java

Test Framework Layers

• Driver Layer: Manages browser setup and teardown (e.g., WebDriverFactory).
• Page Objects: Classes representing each page (e.g., LoginPage, DashboardPage, ProfilePage) with methods to interact and navigate.
• Tests: Test classes that use page objects to perform multi-page navigation flows and assertions.
• Utilities: Helper classes for waits, common actions, and reusable code.
• Configuration: Central place for environment settings, URLs, credentials.

Configuration Patterns

• Use a TestConfig class or properties file to store environment URLs, browser types, and credentials.
• Allow switching environments (e.g., dev, staging, prod) via system properties or config files.
• Configure browser type (Chrome, Firefox) in WebDriverFactory based on config.
• Keep sensitive data like passwords outside source code, use environment variables or encrypted files.

Test Reporting and CI/CD Integration

• Use TestNG or JUnit built-in reports for test execution results.
• Integrate with reporting tools like Allure for detailed HTML reports showing navigation steps and screenshots.
• Configure CI/CD pipelines (Jenkins, GitHub Actions) to run tests on code commits and merge requests.
• Fail builds if navigation flow tests fail to catch regressions early.

Best Practices

1. Page Object Model: Encapsulate page elements and navigation methods in page classes to keep tests clean.
2. Explicit Waits: Use waits to handle page load and element visibility before navigation actions.
3. Clear Navigation Methods: Each page object should have methods that return the next page object after navigation.
4. Data-Driven Tests: Use test data to cover different navigation scenarios without duplicating code.
5. Keep Tests Independent: Avoid dependencies between tests; each test should start from a known state.

Self Check

Where in this folder structure would you add a new page object class for a "Settings" page that is part of the navigation flow?

Key Result

Use Page Object Model with clear navigation methods and configuration to manage multi-page navigation flows in Selenium Java.

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