Multi-page navigation flow in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to open the browser and navigate to the homepage URL.

Selenium Java

WebDriver driver = new ChromeDriver();
driver.[1]("https://example.com");

Drag options to blanks, or click blank then click option'

Aopen

Bnavigate

Cload

Dget

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'navigate' instead of 'get' causes a compile error.

Using 'open' or 'load' are not valid WebDriver methods.

The get method loads a new web page in the current browser window.

2fill in blank

medium

Complete the code to click a link that navigates to the next page.

Selenium Java

WebElement nextPageLink = driver.findElement(By.id("nextPage"));
nextPageLink.[1]();

Drag options to blanks, or click blank then click option'

Asubmit

BsendKeys

Cclick

Dselect

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'submit' only works on forms, not links.

Using 'sendKeys' is for typing text, not clicking.

The click method simulates a mouse click on the element, triggering navigation.

3fill in blank

hard

Fix the error in waiting for the next page to load by completing the wait condition.

Selenium Java

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));
wait.until(ExpectedConditions.[1](By.id("pageTitle")));

Drag options to blanks, or click blank then click option'

AelementToBeClickable

BvisibilityOfElementLocated

CpresenceOfElementLocated

DalertIsPresent

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'presenceOfElementLocated' may pass if element is hidden.

Using 'alertIsPresent' is unrelated to page elements.

Waiting for visibility ensures the element is present and visible before continuing.

4fill in blank

hard

Fill both blanks to navigate back to the previous page and verify the title.

Selenium Java

driver.[1]();
String title = driver.[2]();
assertEquals("Home Page", title);

Drag options to blanks, or click blank then click option'

Anavigate().back

BgetTitle

CgetTitle()

Dnavigate().forward

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'navigate().forward' goes forward, not back.

Using 'getTitle' without parentheses is a syntax error.

navigate().back() goes back one page. getTitle() returns the page title string.

5fill in blank

hard

Fill all three blanks to extract text from an element, verify it, and then close the browser.

Selenium Java

WebElement message = driver.findElement(By.cssSelector(".alert-success"));
String text = message.[1]();
assertTrue(text.[2]("Success"));
driver.[3]();

Drag options to blanks, or click blank then click option'

AgetText

Bcontains

Cquit

DisDisplayed

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'isDisplayed' instead of 'getText' returns a boolean, not text.

Using 'close' instead of 'quit' leaves the browser running.

getText() gets the element's text. contains("Success") checks if text includes 'Success'. quit() closes the browser.

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