Multi-page navigation flow in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java code snippet?

Consider the following Selenium Java code that navigates through two pages and checks the title of the second page. What will be printed to the console?

Selenium Java

WebDriver driver = new ChromeDriver();
driver.get("https://example.com/page1");
String title1 = driver.getTitle();
driver.findElement(By.id("nextPageLink")).click();
new WebDriverWait(driver, Duration.ofSeconds(5))
    .until(ExpectedConditions.titleContains("Page 2"));
String title2 = driver.getTitle();
System.out.println(title2);
driver.quit();

A TimeoutException

B Page 1 - Example Domain

C Page 2 - Example Domain

D NoSuchElementException

💡 Hint

Think about what happens after clicking the link and waiting for the new page title.

The code navigates to page1, clicks a link to page2, waits until the title contains 'Page 2', then prints the title. So the output is the title of page 2.

❓ assertion

intermediate

Which assertion correctly verifies the URL after navigation?

After clicking a link that navigates to "https://example.com/dashboard", which assertion correctly verifies the current URL in Selenium Java?

Selenium Java

driver.findElement(By.linkText("Dashboard")).click();
// Wait for navigation to complete
new WebDriverWait(driver, Duration.ofSeconds(5))
    .until(ExpectedConditions.urlToBe("https://example.com/dashboard"));

A assertNotNull(driver.getCurrentUrl());

B assertTrue(driver.getCurrentUrl().contains("dashboard"));

C assertFalse(driver.getCurrentUrl().equals("https://example.com/home"));

D assertEquals(driver.getCurrentUrl(), "https://example.com/dashboard");

💡 Hint

Check which assertion exactly matches the expected URL.

assertEquals compares the current URL exactly to the expected URL, ensuring precise verification after navigation.

🔧 Debug

advanced

Why does this multi-page navigation test fail intermittently?

This Selenium Java test clicks a link to navigate to a new page and then asserts the page title. Sometimes it fails with an AssertionError. What is the most likely cause?

Selenium Java

driver.findElement(By.id("profileLink")).click();
assertEquals(driver.getTitle(), "User Profile");

A The locator By.id("profileLink") is incorrect and throws NoSuchElementException.

B The test does not wait for the new page to load before checking the title.

C The assertion syntax is wrong and causes a compilation error.

D The driver.quit() is called before the assertion.

💡 Hint

Think about page load timing and synchronization.

Without waiting, the test may check the title before the new page loads, causing intermittent failures.

❓ locator

advanced

Which locator is best for clicking a 'Next' button in a multi-page flow?

You want to click the 'Next' button to go to the next page in a multi-page form. The button has the text 'Next' and a class 'btn-next'. Which locator is the best practice in Selenium Java?

A By.cssSelector("button.btn-next")

B By.className("btn-next")

C By.xpath("//button[text()='Next']")

D By.linkText("Next")

💡 Hint

Consider specificity and stability of locators.

By.cssSelector("button.btn-next") is specific, stable, and less brittle than XPath or linkText for buttons.

❓ framework

expert

How to design a robust multi-page navigation test framework in Selenium Java?

Which approach best supports maintainability and reliability for multi-page navigation tests in Selenium Java?

A Use Page Object Model with explicit waits and separate methods for navigation actions.

B Write all navigation steps inline in test methods without abstraction.

C Use Thread.sleep() after each click to wait for page loads.

D Avoid waits and rely on implicit waits only.

💡 Hint

Think about code reuse, readability, and synchronization.

Page Object Model with explicit waits improves code reuse, readability, and handles timing issues robustly.