Why advanced skills handle complex scenarios in Selenium Java - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

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

Selenium Java

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

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

Aget

Bstart

Copen

Dnavigate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'navigate' instead of 'get' causes compilation errors.

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

2fill in blank

medium

Complete the code to find a button by its ID and click it.

Selenium Java

WebElement button = driver.findElement(By.[1]("submitBtn"));
button.click();

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

AtagName

Bname

CclassName

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'name' or 'className' when the element has an ID.

The By.id locator finds elements by their unique ID attribute.

3fill in blank

hard

Fix the error in the code to wait until an element is visible before clicking.

Selenium Java

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

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

AelementToBeClickable

BvisibilityOfElementLocated

CpresenceOfElementLocated

DelementToBeSelected

Attempts:

3 left

💡 Hint

Common Mistakes

Using presenceOfElementLocated may cause errors if element is hidden.

visibilityOfElementLocated waits until the element is visible on the page.

4fill in blank

hard

Fill the blank to create a test that asserts the page title contains a word.

Selenium Java

String title = driver.getTitle();
assertTrue(title.[1]("Example"));

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

Aequals

BstartsWith

Ccontains

DendsWith

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'equals' checks exact match, not containment.

The contains method checks if the title includes the given word.

5fill in blank

hard

Fill both blanks to create a map of element texts filtered by length.

Selenium Java

Map<String, Integer> lengths = elements.stream()
  .filter(e -> e.getText().length() [1] 3)
  .collect(Collectors.toMap(e -> e.getText(), e -> e.getText().[2]()));

lengths.forEach((k, v) -> System.out.println(k + ": " + v));

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

A>

Blength

Clength()

DtoUpperCase

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'length' without parentheses causes errors.

The filter keeps texts longer than 3 characters. The map stores text and its length.

Practice

1. Why are advanced Selenium skills important when testing complex web applications?

easy

A. They help handle dynamic elements and unexpected delays reliably.

B. They make tests run faster by skipping validations.

C. They allow tests to ignore errors and continue blindly.

D. They reduce the need for writing any assertions.

Solution

1. Step 1: Understand dynamic web elements

   Complex apps often have elements that load or change after some delay.

2. Step 2: Importance of handling delays and exceptions

   Advanced skills like waits and exception handling ensure tests wait for elements and handle errors gracefully.

3. Final Answer:

   They help handle dynamic elements and unexpected delays reliably. -> Option A

4. Quick Check:

   Advanced skills = handle dynamic elements [OK]

Hint: Think about handling delays and changes in web pages [OK]

Common Mistakes:

• Assuming tests should skip validations
• Ignoring errors instead of handling them
• Believing assertions are unnecessary

2. Which of the following is the correct way to wait for an element to be clickable in Selenium Java?

easy

A. new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit")));

B. driver.wait(10).until(ExpectedConditions.clickable(By.id("submit")));

C. WebDriverWait wait = new WebDriverWait(10); wait.until(clickable(By.id("submit")));

D. driver.findElement(By.id("submit")).waitUntilClickable(10);

Solution

1. Step 1: Recall correct WebDriverWait syntax

   WebDriverWait requires driver and timeout, then calls until with ExpectedConditions.

2. Step 2: Check each option's syntax

   new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit"))); matches correct syntax; others have wrong method calls or missing driver.

3. Final Answer:

   new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit"))); -> Option A

4. Quick Check:

   Correct WebDriverWait syntax = new WebDriverWait(driver, 10).until(ExpectedConditions.elementToBeClickable(By.id("submit"))); [OK]

Hint: Remember WebDriverWait needs driver and ExpectedConditions [OK]

Common Mistakes:

• Using driver.wait() which does not exist
• Missing driver parameter in WebDriverWait constructor
• Incorrect method names like waitUntilClickable

3. What will be the output of the following Selenium Java code snippet?

WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(5));
WebElement button = wait.until(ExpectedConditions.visibilityOfElementLocated(By.id("login")));
System.out.println(button.isDisplayed());

medium

A. false if element is not visible, else true

B. Always prints true regardless of element visibility

C. true if element with id 'login' is visible within 5 seconds, else TimeoutException

D. Compilation error due to wrong WebDriverWait usage

Solution

1. Step 1: Understand WebDriverWait with ExpectedConditions

   wait.until waits up to 5 seconds for element visibility or throws TimeoutException if not found.

2. Step 2: Analyze System.out.println output

   If element is visible, isDisplayed() returns true; if not found in time, exception occurs before print.

3. Final Answer:

   true if element with id 'login' is visible within 5 seconds, else TimeoutException -> Option C

4. Quick Check:

   Wait returns element or throws exception [OK]

Hint: Wait returns element or throws exception, no false return [OK]

Common Mistakes:

• Thinking wait returns false instead of exception
• Assuming isDisplayed() runs if element not found
• Confusing compilation errors with runtime exceptions

4. Identify the error in this Selenium Java code snippet that tries to click a button:

driver.findElement(By.id("submitBtn")).click();
Thread.sleep(5000);

medium

A. Missing import for By class causes compilation error.

B. Using Thread.sleep causes unnecessary fixed wait; better to use explicit wait.

C. click() method is not valid for WebElement.

D. findElement should be replaced with findElements for clicking.

Solution

1. Step 1: Analyze use of Thread.sleep

   Thread.sleep pauses test for fixed time, which is inefficient and unreliable for dynamic waits.

2. Step 2: Suggest better approach

   Explicit waits like WebDriverWait wait for conditions dynamically, improving test stability.

3. Final Answer:

   Using Thread.sleep causes unnecessary fixed wait; better to use explicit wait. -> Option B

4. Quick Check:

   Use explicit waits, not Thread.sleep [OK]

Hint: Avoid Thread.sleep; prefer explicit waits for stability [OK]

Common Mistakes:

• Thinking Thread.sleep is best for waiting
• Confusing findElement and findElements usage
• Believing click() is invalid method

5. You need to write a Selenium Java test that waits for a list of dynamic elements to appear, clicks each visible one, and logs failures without stopping the test. Which advanced skills should you combine?

hard

A. Use JavaScriptExecutor to click elements without waits or error handling.

B. Use Thread.sleep for fixed waits, no exception handling, and hard assertions to stop on failure.

C. Use implicit waits only, no exception handling, and no assertions.

D. Use explicit waits for visibility, try-catch blocks for exceptions, and soft assertions for logging failures.

Solution

1. Step 1: Handle dynamic elements with explicit waits

   Explicit waits ensure each element is visible before interacting, avoiding errors.

2. Step 2: Use try-catch to handle exceptions without stopping test

   Try-catch blocks catch errors per element, allowing test to continue and log issues.

3. Step 3: Apply soft assertions to log failures without halting

   Soft assertions record failures but let the test finish, improving test reporting.

4. Final Answer:

   Use explicit waits for visibility, try-catch blocks for exceptions, and soft assertions for logging failures. -> Option D

5. Quick Check:

   Combine waits, exception handling, soft assertions [OK]

Hint: Combine waits, try-catch, and soft assertions for robust tests [OK]

Common Mistakes:

• Using fixed waits causing flaky tests
• Not handling exceptions causing test stops
• Using hard assertions stopping tests early