Auto-complete field handling in Selenium Java - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to locate the auto-complete input field by its ID.

Selenium Java

WebElement input = driver.findElement(By.[1]("searchBox"));

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

AclassName

BtagName

Cid

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using By.name or By.className when the element has a unique ID.

Using By.tagName which is too broad and may select multiple elements.

The id locator is used to find the element with the exact ID 'searchBox'. This is the most direct and reliable way to locate the input field.

2fill in blank

medium

Complete the code to send the text 'Selenium' to the auto-complete input field.

Selenium Java

input.[1]("Selenium");

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

AsendKeys

Bclear

Cclick

Dsubmit

Attempts:

3 left

💡 Hint

Common Mistakes

Using click() instead of sendKeys() to enter text.

Using clear() which only clears the field but does not enter text.

The sendKeys method types the given text into the input field, simulating user input.

3fill in blank

hard

Fix the error in the code to wait until the auto-complete suggestions are visible.

Selenium Java

new WebDriverWait(driver, Duration.ofSeconds(10)).until(ExpectedConditions.[1](By.className("suggestions")));

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

AinvisibilityOfElementLocated

BpresenceOfElementLocated

CelementToBeClickable

DvisibilityOfElementLocated

Attempts:

3 left

💡 Hint

Common Mistakes

Using invisibilityOfElementLocated which waits for element to disappear.

Using presenceOfElementLocated which may not guarantee visibility.

The visibilityOfElementLocated condition waits until the element is present and visible on the page, which is needed to interact with the suggestions.

4fill in blank

hard

Fill both blanks to select the first suggestion from the auto-complete list.

Selenium Java

List<WebElement> suggestions = driver.findElements(By.[1]("suggestion-item"));
suggestions.get([2]).click();

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

AclassName

Bid

C0

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using id instead of className when suggestions have a class.

Using index 1 which selects the second suggestion instead of the first.

The suggestions are located by their class name 'suggestion-item'. The first suggestion is at index 0 in the list, so clicking it selects the first option.

5fill in blank

hard

Fill all three blanks to verify the selected suggestion text matches 'Selenium WebDriver'.

Selenium Java

String selectedText = suggestions.get([1]).getText();
assertEquals([2], selectedText, "Suggestion text should be correct");
System.out.println("Selected: " + [3]);

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

A0

B"Selenium WebDriver"

CselectedText

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 1 which selects the wrong suggestion.

Mixing up expected and actual parameters in assertEquals.

Printing the expected string instead of the selected text variable.

The first suggestion is at index 0. We compare its text to the expected string 'Selenium WebDriver' using assertEquals. Then we print the selected text variable.

Practice

1. What is the main purpose of handling an auto-complete field in Selenium testing?

easy

A. To disable the auto-complete feature in the browser

B. To refresh the page automatically after typing

C. To submit the form without entering any data

D. To select the correct suggestion from the dynamic list based on user input

Solution

1. Step 1: Understand auto-complete behavior

   Auto-complete fields show suggestions dynamically as the user types.

2. Step 2: Purpose of handling in Selenium

   We need to select the correct suggestion from the list to simulate user interaction accurately.

3. Final Answer:

   To select the correct suggestion from the dynamic list based on user input -> Option D

4. Quick Check:

   Auto-complete handling = selecting suggestion [OK]

Hint: Focus on selecting suggestions, not disabling features [OK]

Common Mistakes:

• Trying to disable auto-complete instead of selecting
• Ignoring dynamic suggestion list
• Submitting form without input

2. Which Selenium Java code snippet correctly waits for the auto-complete suggestion list to appear before selecting an option?

easy

A. new WebDriverWait(driver, Duration.ofSeconds(10)).until(ExpectedConditions.visibilityOfElementLocated(By.id("suggestions")));

B. driver.findElement(By.id("suggestions")).click();

C. Thread.sleep(10000); driver.findElement(By.id("suggestions")).click();

D. driver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10)); driver.findElement(By.id("suggestions")).click();

Solution

1. Step 1: Identify correct wait usage

   Explicit wait with WebDriverWait and ExpectedConditions waits for element visibility properly.

2. Step 2: Compare with other options

   driver.findElement(By.id("suggestions")).click(); clicks without waiting, C uses Thread.sleep which is not best practice, D uses implicit wait which is less reliable for dynamic elements.

3. Final Answer:

   new WebDriverWait(driver, Duration.ofSeconds(10)).until(ExpectedConditions.visibilityOfElementLocated(By.id("suggestions"))); -> Option A

4. Quick Check:

   Explicit wait for visibility = new WebDriverWait(driver, Duration.ofSeconds(10)).until(ExpectedConditions.visibilityOfElementLocated(By.id("suggestions"))); [OK]

Hint: Use explicit waits with ExpectedConditions for dynamic elements [OK]

Common Mistakes:

• Using Thread.sleep instead of explicit wait
• Relying only on implicit waits
• Clicking before element is visible

3. Given the following code snippet, what will be the value of the input field after execution?

driver.findElement(By.id("searchBox")).sendKeys("App");
new WebDriverWait(driver, Duration.ofSeconds(5))
  .until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector("ul.suggestions li")));
List<WebElement> options = driver.findElements(By.cssSelector("ul.suggestions li"));
for (WebElement option : options) {
  if (option.getText().equals("Apple")) {
    option.click();
    break;
  }
}
String value = driver.findElement(By.id("searchBox")).getAttribute("value");

medium

A. "App"

B. "Apple"

C. "" (empty string)

D. Throws NoSuchElementException

Solution

1. Step 1: Analyze input and wait

   The code types "App" and waits for suggestions to appear.

2. Step 2: Select matching suggestion

   It loops through suggestions and clicks the one with text "Apple".

3. Step 3: Check input value after click

   Clicking "Apple" updates the input field value to "Apple".

4. Final Answer:

   "Apple" -> Option B

5. Quick Check:

   Selected suggestion text = input value [OK]

Hint: Click matching suggestion updates input value [OK]

Common Mistakes:

• Assuming input stays as typed text
• Ignoring wait for suggestions
• Expecting empty input after click

4. Identify the error in the following Selenium Java code for selecting an auto-complete option:

driver.findElement(By.id("searchBox")).sendKeys("Ban");
List<WebElement> options = driver.findElements(By.cssSelector("ul.suggestions li"));
for (WebElement option : options) {
  if (option.getText().equals("Banana")) {
    option.click();
  }
}

medium

A. Missing explicit wait for suggestions to appear before finding elements

B. Using sendKeys instead of setText method

C. Incorrect CSS selector syntax for suggestions list

D. Not clearing the input field before typing

Solution

1. Step 1: Check for wait usage

   The code finds suggestions immediately after typing without waiting for them to appear.

2. Step 2: Consequence of missing wait

   Without explicit wait, options list may be empty causing no click action.

3. Final Answer:

   Missing explicit wait for suggestions to appear before finding elements -> Option A

4. Quick Check:

   Wait before findElements = Missing explicit wait for suggestions to appear before finding elements [OK]

Hint: Always wait for suggestions before accessing them [OK]

Common Mistakes:

• Skipping explicit wait causing empty list
• Assuming suggestions load instantly
• Not breaking loop after click

5. You need to write a Selenium Java test to select the suggestion "Cherry" from an auto-complete field with id "fruitInput". The suggestions appear in a ul with class "autocomplete-list" and each suggestion is a li. Which approach correctly handles this scenario including waiting and verification?

hard

A. Send keys "Che", use implicit wait, find li with text "Cherry" and click, no assertion needed

B. Send keys "Cherry" to input, immediately click first li in ul.autocomplete-list, no wait needed

C. Send keys "Che" to input, wait explicitly for visibility of ul.autocomplete-list, find all li, click the one with text "Cherry", then assert input value equals "Cherry"

D. Clear input, send keys "Ch", use Thread.sleep(5000), click last li in ul.autocomplete-list, assert input value contains "Ch"

Solution

1. Step 1: Send partial keys and wait explicitly

   Typing "Che" triggers suggestions; explicit wait ensures suggestions are visible before interaction.

2. Step 2: Find and click correct suggestion, then verify

   Find all li elements, click the one with text "Cherry", then assert input value matches to confirm selection.

3. Final Answer:

   Send keys "Che" to input, wait explicitly for visibility of ul.autocomplete-list, find all li, click the one with text "Cherry", then assert input value equals "Cherry" -> Option C

4. Quick Check:

   Explicit wait + correct click + assert input value = Send keys "Che" to input, wait explicitly for visibility of ul.autocomplete-list, find all li, click the one with text "Cherry", then assert input value equals "Cherry" [OK]

Hint: Wait explicitly, click matching text, then verify input value [OK]

Common Mistakes:

• Not waiting explicitly for suggestions
• Clicking wrong suggestion or without verification
• Using Thread.sleep instead of explicit wait