Multi-page navigation flow in Selenium Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a multi-page navigation flow in software testing?

It is a test scenario where the user moves through several web pages in sequence to complete a task, verifying each page loads and behaves correctly.

beginner

Why is it important to verify URLs during multi-page navigation?

Checking URLs ensures the browser is on the correct page after navigation, confirming the flow is working as expected.

beginner

In Selenium Java, which method is used to navigate to a new page?

The method driver.get("url") is used to open a new page, and driver.navigate().to("url") can also be used for navigation.

intermediate

How can you wait for a page to load before interacting with elements in Selenium?

Use explicit waits like WebDriverWait with ExpectedConditions to wait for specific elements to be visible or clickable before proceeding.

beginner

What is a common assertion to verify successful navigation in a multi-page flow?

Asserting the page title or a unique element on the page confirms the navigation was successful.

Which Selenium method is best to open a new web page?

A driver.switchTo()

B driver.findElement()

C driver.close()

D driver.get("url")

driver.get("url") opens the specified URL in the browser.

What should you check after clicking a link in a multi-page flow?

A Page URL or title

B Browser console logs

C Screen resolution

D Operating system version

Verifying the page URL or title confirms correct navigation.

Which Selenium feature helps wait for a page element before continuing?

A WebDriverWait with ExpectedConditions

B Thread.sleep()

C driver.quit()

D driver.navigate().back()

WebDriverWait waits dynamically for conditions like element visibility.

What is a good practice when writing multi-page navigation tests?

A Skip verification to save time

B Only check the first page

C Verify each page loads correctly before moving on

D Use random URLs

Verifying each page ensures the flow works end-to-end.

Which assertion can confirm you are on the right page?

A Assert browser window size

B Assert page title or unique element presence

C Assert system time

D Assert network speed

Page title or unique elements identify the correct page.

Describe the steps to test a multi-page navigation flow using Selenium Java.

Think about how a user clicks through pages and how you check each page.

Explain why waiting for elements is important in multi-page navigation tests.

Consider what happens if you try to click before a page finishes loading.

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