WebDriverManager for automatic driver management in Selenium Java - Build an Automation Script

Automate browser launch using WebDriverManager

Preconditions (2)

Step 1: Use WebDriverManager to setup ChromeDriver automatically

Step 2: Launch a new Chrome browser instance

Step 3: Navigate to 'https://example.com'

Step 4: Verify the page title is 'Example Domain'

Step 5: Close the browser

✅ Expected Result: Chrome browser opens, navigates to 'https://example.com', page title matches 'Example Domain', and browser closes without errors

Automation Requirements - Selenium WebDriver with WebDriverManager

Assertions Needed:

Assert that the page title equals 'Example Domain'

Best Practices:

Use WebDriverManager to manage driver binaries automatically

Use explicit waits if needed (not required here as page loads quickly)

Close the browser in a finally block or use try-with-resources

Use By locators only when interacting with page elements (not needed here)

Automated Solution

Selenium Java

import io.github.bonigarcia.wdm.WebDriverManager;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.chrome.ChromeDriver;
import static org.junit.jupiter.api.Assertions.assertEquals;

public class WebDriverManagerTest {
    public static void main(String[] args) {
        WebDriver driver = null;
        try {
            // Setup ChromeDriver automatically
            WebDriverManager.chromedriver().setup();

            // Launch Chrome browser
            driver = new ChromeDriver();

            // Navigate to example.com
            driver.get("https://example.com");

            // Verify page title
            String title = driver.getTitle();
            assertEquals("Example Domain", title);

            System.out.println("Test Passed: Page title is 'Example Domain'");
        } catch (AssertionError e) {
            System.out.println("Test Failed: " + e.getMessage());
        } finally {
            if (driver != null) {
                driver.quit();
            }
        }
    }
}

This code uses WebDriverManager to automatically download and setup the correct ChromeDriver binary for the current system. This removes the need to manually download or set system properties for the driver.

We create a ChromeDriver instance to launch the browser, then navigate to 'https://example.com'. We get the page title and assert it equals 'Example Domain' using JUnit's assertEquals method.

The try-finally block ensures the browser closes even if the assertion fails, preventing leftover browser processes.

This simple example shows how WebDriverManager simplifies driver management and how to verify page title with Selenium.

Common Mistakes - 4 Pitfalls

Manually downloading and setting driver path instead of using WebDriverManager

Not closing the browser after test execution

Using Thread.sleep() to wait for page load

Catching generic Exception instead of AssertionError for test assertions

Bonus Challenge

Now add data-driven testing to open multiple URLs and verify their titles

Show Hint

Practice

1. What is the main purpose of using WebDriverManager in Selenium Java tests?

easy

A. To automatically download and manage browser drivers

B. To write test assertions easily

C. To create test reports

D. To locate web elements on a page

Solution

1. Step 1: Understand WebDriverManager's role

   WebDriverManager automates the setup of browser drivers needed for Selenium tests.

2. Step 2: Compare with other options

   Options A, B, and C relate to other Selenium tasks, not driver management.

3. Final Answer:

   To automatically download and manage browser drivers -> Option A

4. Quick Check:

   WebDriverManager = automatic driver setup [OK]

Hint: WebDriverManager handles drivers, not test logic or reports [OK]

Common Mistakes:

• Confusing driver management with test assertions
• Thinking it creates test reports
• Assuming it locates web elements

2. Which of the following is the correct syntax to setup ChromeDriver using WebDriverManager in Java?

easy

A. WebDriverManager.setup.chromedriver();

B. WebDriverManager().chromedriver.setup();

C. WebDriverManager.chromeDriver.setup();

D. WebDriverManager.chromedriver().setup();

Solution

1. Step 1: Recall WebDriverManager syntax

   The correct method call is WebDriverManager.chromedriver().setup(); to setup ChromeDriver.

2. Step 2: Identify syntax errors in other options

   Options A, C, and D have incorrect method chaining or casing.

3. Final Answer:

   WebDriverManager.chromedriver().setup(); -> Option D

4. Quick Check:

   Correct method chaining = WebDriverManager.chromedriver().setup(); [OK]

Hint: Remember: WebDriverManager.browsername().setup() [OK]

Common Mistakes:

• Incorrect method chaining order
• Wrong capitalization of 'chromedriver'
• Using parentheses incorrectly

3. What will happen when the following code runs?

WebDriverManager.firefoxdriver().setup();
WebDriver driver = new FirefoxDriver();
driver.get("https://example.com");
System.out.println(driver.getTitle());

medium

A. It opens Firefox, navigates to example.com, and prints the page title

B. It throws a runtime error due to missing driver setup

C. It opens Chrome instead of Firefox

D. It compiles but does not open any browser

Solution

1. Step 1: Analyze WebDriverManager usage

   The code calls WebDriverManager.firefoxdriver().setup(); which downloads and sets up FirefoxDriver automatically.

2. Step 2: Check driver creation and navigation

   Then it creates a FirefoxDriver instance, opens the URL, and prints the page title.

3. Final Answer:

   It opens Firefox, navigates to example.com, and prints the page title -> Option A

4. Quick Check:

   Setup + FirefoxDriver + getTitle() = It opens Firefox, navigates to example.com, and prints the page title [OK]

Hint: Setup driver first, then create driver instance [OK]

Common Mistakes:

• Assuming driver setup is manual and missing
• Confusing FirefoxDriver with ChromeDriver
• Expecting no browser to open

4. Identify the error in this code snippet using WebDriverManager:

WebDriverManager.chromedriver.setup();
WebDriver driver = new ChromeDriver();

medium

A. WebDriverManager cannot setup ChromeDriver

B. Missing parentheses after chromedriver() method

C. ChromeDriver class is not imported

D. No error, code is correct

Solution

1. Step 1: Check WebDriverManager method call

   The method chromedriver must be called with parentheses: chromedriver().

2. Step 2: Verify other options

   ChromeDriver class is not imported might be true but is not shown in snippet; WebDriverManager cannot setup ChromeDriver is false because WebDriverManager supports ChromeDriver; No error, code is correct is incorrect due to syntax error.

3. Final Answer:

   Missing parentheses after chromedriver() method -> Option B

4. Quick Check:

   Method calls need parentheses [OK]

Hint: Method calls always need () in Java [OK]

Common Mistakes:

• Omitting parentheses on method calls
• Assuming WebDriverManager can't setup ChromeDriver
• Ignoring import statements

5. You want to run Selenium tests on multiple browsers without manually downloading drivers. Which WebDriverManager feature helps achieve this efficiently?

hard

A. Writing custom driver download scripts

B. Manual driver path configuration in system properties

C. Automatic detection and download of required driver versions

D. Using deprecated driver executables

Solution

1. Step 1: Understand the problem

   Running tests on multiple browsers requires managing different drivers automatically.

2. Step 2: Identify WebDriverManager feature

   WebDriverManager automatically detects browser version and downloads matching drivers, avoiding manual setup.

3. Final Answer:

   Automatic detection and download of required driver versions -> Option C

4. Quick Check:

   Auto driver management = Automatic detection and download of required driver versions [OK]

Hint: Auto-download drivers for all browsers with WebDriverManager [OK]

Common Mistakes:

• Thinking manual config is needed
• Trying to write custom scripts unnecessarily
• Using outdated driver files