First Selenium Java test - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Selenium Java test?

Consider this Selenium Java test code snippet. What will be the test result after execution?

Selenium Java

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.junit.Assert;
import org.junit.Test;

public class SimpleTest {
    @Test
    public void testTitle() {
        WebDriver driver = new ChromeDriver();
        driver.get("https://example.com");
        String title = driver.getTitle();
        Assert.assertEquals("Example Domain", title);
        driver.quit();
    }
}

A Test passes because the page title matches "Example Domain".

B Test fails because the driver is not closed properly.

C Test fails because the URL is incorrect.

D Test fails due to a NoSuchElementException.

💡 Hint

Think about what the getTitle() method returns for https://example.com.

The test opens the URL https://example.com, which has the title "Example Domain". The assertion checks if the title matches exactly, so the test passes. The driver is closed properly with driver.quit(). No element lookup is done, so no NoSuchElementException occurs.

❓ locator

intermediate

Which locator is best to find the login button?

Given a login button with HTML: , which locator is the best practice to find it in Selenium Java?

A By.id("loginBtn")

B By.className("btn")

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

D By.cssSelector("button[aria-label='Login']")

💡 Hint

Use the most specific and stable locator.

Using By.id("loginBtn") is best because IDs are unique and stable. Class names may be shared by multiple elements. XPath and CSS selectors are more complex and less efficient here.

❓ assertion

advanced

Which assertion correctly verifies the presence of a success message?

You want to check if the element with id "successMsg" contains the text "Login successful". Which assertion is correct in Selenium Java with JUnit?

Selenium Java

WebElement message = driver.findElement(By.id("successMsg"));
String text = message.getText();

A Assert.assertEquals("Login successful", text);

B Assert.assertNotNull(text);

C Assert.assertTrue(text.contains("Login successful"));

D Assert.assertFalse(text.isEmpty());

💡 Hint

The message might contain extra spaces or other text.

Using assertTrue with text.contains ensures the message includes the expected text even if there is extra content. assertEquals would fail if the text is not exactly the same.

🔧 Debug

advanced

Why does this Selenium test throw NoSuchElementException?

This test fails with NoSuchElementException: WebDriver driver = new ChromeDriver(); driver.get("https://example.com/login"); WebElement input = driver.findElement(By.id("username")); input.sendKeys("user1"); What is the most likely cause?

A The driver was not initialized before calling findElement.

B The sendKeys method is called before findElement.

C The URL is incorrect and page did not load.

D The element with id "username" is inside an iframe and not switched to.

💡 Hint

Check if the element is inside a frame or iframe.

If the element is inside an iframe, Selenium cannot find it until you switch the driver's context to that iframe. This causes NoSuchElementException.

❓ framework

expert

What is the correct order of JUnit annotations for Selenium test lifecycle?

Arrange these JUnit annotations in the order they execute during a Selenium test run: 1. @BeforeClass 2. @Before 3. @Test 4. @After 5. @AfterClass

A 2,1,3,4,5

B 1,2,3,4,5

C 1,3,2,4,5

D 1,2,4,3,5

💡 Hint

Think about setup and teardown phases at class and test method levels.

@BeforeClass runs once before all tests, @Before runs before each test, @Test is the test method, @After runs after each test, and @AfterClass runs once after all tests.

Practice

1. What is the main purpose of a Selenium Java test?

easy

A. To write Java programs unrelated to browsers

B. To automate browser actions like opening a page and checking content

C. To manually test software without code

D. To design user interfaces

Solution

1. Step 1: Understand Selenium's role

   Selenium is used to automate browser actions such as opening pages and clicking buttons.

2. Step 2: Identify the test goal

   The main goal of a Selenium Java test is to automate browser tasks and verify web page behavior.

3. Final Answer:

   To automate browser actions like opening a page and checking content -> Option B

4. Quick Check:

   Selenium test = automate browser [OK]

Hint: Selenium automates browsers, not manual or UI design tasks [OK]

Common Mistakes:

• Confusing Selenium with manual testing
• Thinking Selenium is for UI design
• Assuming Selenium runs non-browser Java code

2. Which of the following is the correct way to start a Chrome browser in Selenium Java?

easy

A. WebDriver driver = new ChromeDriver();

B. ChromeDriver driver = WebDriver();

C. driver = new WebDriver.Chrome();

D. WebDriver driver = ChromeDriver();

Solution

1. Step 1: Recall Selenium WebDriver syntax

   The correct way is to declare WebDriver interface and instantiate ChromeDriver class.

2. Step 2: Check each option's syntax

   WebDriver driver = new ChromeDriver(); uses correct Java syntax: WebDriver driver = new ChromeDriver(); others have syntax errors or wrong order.

3. Final Answer:

   WebDriver driver = new ChromeDriver(); -> Option A

4. Quick Check:

   Use interface = new implementation() [OK]

Hint: Use WebDriver driver = new ChromeDriver(); to start Chrome [OK]

Common Mistakes:

• Missing 'new' keyword
• Wrong constructor call syntax
• Assigning without type declaration

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

WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
String title = driver.getTitle();
System.out.println(title);
driver.quit();

Assuming the page title is "Example Domain".

medium

A. Example Domain

B. https://example.com

C. null

D. No output, code throws error

Solution

1. Step 1: Understand driver.getTitle()

   driver.getTitle() returns the title of the current page, which is "Example Domain" here.

2. Step 2: Check the print statement

   System.out.println(title) prints the page title to the console.

3. Final Answer:

   Example Domain -> Option A

4. Quick Check:

   getTitle() prints page title [OK]

Hint: getTitle() returns page title string [OK]

Common Mistakes:

• Confusing URL with title
• Expecting no output
• Assuming getTitle() returns null

4. Identify the error in this Selenium Java code snippet:

import org.openqa.selenium.By;
WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
WebElement button = driver.findElement(By.id("submit"));
button.click();
driver.close();

medium

A. Missing import for By class

B. findElement should use By.name instead of By.id

C. driver.close() should be driver.quit() to close browser fully

D. button.click() is not valid for WebElement

Solution

1. Step 1: Understand driver.close() vs driver.quit()

   driver.close() closes current tab, driver.quit() closes entire browser session.

2. Step 2: Check best practice for test cleanup

   To fully close browser and end session, driver.quit() is preferred after test.

3. Final Answer:

   driver.close() should be driver.quit() to close browser fully -> Option C

4. Quick Check:

   Use quit() to close browser fully [OK]

Hint: Use driver.quit() to close browser fully after test [OK]

Common Mistakes:

• Using driver.close() only closes one tab
• Confusing By.id and By.name without context
• Assuming button.click() is invalid

5. You want to write a Selenium Java test that opens a browser, navigates to "https://example.com", verifies the page title is "Example Domain", and then closes the browser. Which code snippet correctly performs this test with assertion?

hard

A. WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
assert driver.getTitle().equals("Example Domain");
driver.quit();

B. WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
if(driver.getTitle() == "Example Domain") {
System.out.println("Title matches");
}
driver.close();

C. WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
assert driver.getTitle() == "Example Domain";
driver.quit();

D. WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
assertEquals("Example Domain", driver.getTitle());
driver.quit();

Solution

1. Step 1: Check assertion method correctness

   assertEquals(expected, actual) is the correct JUnit assertion method to compare strings.

2. Step 2: Verify browser close method

   driver.quit() properly closes the browser after test.

3. Step 3: Identify errors in other options

   WebDriver driver = new ChromeDriver(); driver.get("https://example.com"); assert driver.getTitle().equals("Example Domain"); driver.quit(); uses plain assert with equals() but is less clear; WebDriver driver = new ChromeDriver(); driver.get("https://example.com"); if(driver.getTitle() == "Example Domain") { System.out.println("Title matches"); } driver.close(); uses == for string comparison (wrong); WebDriver driver = new ChromeDriver(); driver.get("https://example.com"); assert driver.getTitle() == "Example Domain"; driver.quit(); uses == in assert (wrong).

4. Final Answer:

   assertEquals("Example Domain", driver.getTitle()); with driver.quit() -> Option D

5. Quick Check:

   Use assertEquals for string check, quit() to close browser [OK]

Hint: Use assertEquals(expected, actual) and driver.quit() [OK]

Common Mistakes:

• Using == to compare strings
• Using driver.close() instead of quit()
• Missing proper assertion method