Bird
Raised Fist0
Selenium Javatesting~10 mins

WebDriver setup (ChromeDriver) in Selenium Java - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to create a new ChromeDriver instance.

Selenium Java
WebDriver driver = new [1]();
Drag options to blanks, or click blank then click option'
ASafariDriver
BEdgeDriver
CFirefoxDriver
DChromeDriver
Attempts:
3 left
💡 Hint
Common Mistakes
Using FirefoxDriver instead of ChromeDriver.
Forgetting to import the ChromeDriver class.
2fill in blank
medium

Complete the code to set the system property for ChromeDriver executable path.

Selenium Java
System.setProperty("webdriver.chrome.driver", [1]);
Drag options to blanks, or click blank then click option'
A"path/to/edgedriver.exe"
B"path/to/geckodriver.exe"
C"path/to/chromedriver.exe"
D"path/to/safaridriver.exe"
Attempts:
3 left
💡 Hint
Common Mistakes
Setting the path to the wrong driver executable.
Not using quotes around the path string.
3fill in blank
hard

Fix the error in the code to properly import the ChromeDriver class.

Selenium Java
import org.openqa.selenium.[1];
Drag options to blanks, or click blank then click option'
Achrome.ChromeDriver
Bfirefox.FirefoxDriver
Cedge.EdgeDriver
Dsafari.SafariDriver
Attempts:
3 left
💡 Hint
Common Mistakes
Importing FirefoxDriver instead of ChromeDriver.
Missing the import statement entirely.
4fill in blank
hard

Fill both blanks to initialize ChromeDriver and open the URL "https://example.com".

Selenium Java
WebDriver driver = new [1]();
driver.[2]("https://example.com");
Drag options to blanks, or click blank then click option'
AChromeDriver
Bget
Cnavigate
DFirefoxDriver
Attempts:
3 left
💡 Hint
Common Mistakes
Using FirefoxDriver instead of ChromeDriver.
Using navigate without to method.
5fill in blank
hard

Fill all three blanks to properly quit the ChromeDriver session after opening a page.

Selenium Java
WebDriver driver = new [1]();
driver.[2]("https://example.com");
driver.[3]();
Drag options to blanks, or click blank then click option'
AChromeDriver
Bget
Cquit
Dclose
Attempts:
3 left
💡 Hint
Common Mistakes
Using close instead of quit which only closes one window.
Not quitting the driver at all.

Practice

(1/5)
1. What is the main purpose of setting up ChromeDriver in Selenium WebDriver tests?
easy
A. To control the Chrome browser automatically during tests
B. To write test cases in Java
C. To create HTML reports for test results
D. To manage database connections

Solution

  1. Step 1: Understand WebDriver role

    WebDriver controls browsers to simulate user actions in tests.
  2. Step 2: Identify ChromeDriver's function

    ChromeDriver is the specific driver that controls the Chrome browser.
  3. Final Answer:

    To control the Chrome browser automatically during tests -> Option A
  4. Quick Check:

    ChromeDriver controls Chrome browser [OK]
Hint: ChromeDriver lets Selenium talk to Chrome browser [OK]
Common Mistakes:
  • Confusing ChromeDriver with test case writing
  • Thinking ChromeDriver creates reports
  • Mixing browser control with database tasks
2. Which of the following is the correct way to set the ChromeDriver path in Java before creating a ChromeDriver instance?
easy
A. System.setProperty("webdriver.chrome.driver", "path/to/chromedriver.exe");
B. ChromeDriver.setPath("path/to/chromedriver.exe");
C. WebDriver.chromeDriverPath = "path/to/chromedriver.exe";
D. driver.setChromeDriver("path/to/chromedriver.exe");

Solution

  1. Step 1: Recall Java system property syntax

    Setting ChromeDriver path uses System.setProperty with key "webdriver.chrome.driver".
  2. Step 2: Match correct method and parameters

    System.setProperty("webdriver.chrome.driver", "path/to/chromedriver.exe"); correctly uses System.setProperty with the driver path string.
  3. Final Answer:

    System.setProperty("webdriver.chrome.driver", "path/to/chromedriver.exe"); -> Option A
  4. Quick Check:

    Use System.setProperty for driver path [OK]
Hint: Use System.setProperty with key "webdriver.chrome.driver" [OK]
Common Mistakes:
  • Using non-existent methods like setPath or setChromeDriver
  • Assigning path directly to WebDriver variable
  • Missing quotes or wrong method names
3. What will happen if you run the following Java Selenium code snippet?
System.setProperty("webdriver.chrome.driver", "/drivers/chromedriver");
WebDriver driver = new ChromeDriver();
driver.get("https://example.com");
driver.quit();
medium
A. The browser opens but does not navigate to example.com
B. The code throws a syntax error at System.setProperty
C. The Chrome browser opens example.com and then closes
D. The ChromeDriver fails to start due to missing driver path

Solution

  1. Step 1: Analyze driver setup and navigation

    System.setProperty sets the driver path correctly, ChromeDriver instance is created, and driver.get opens the URL.
  2. Step 2: Check browser closing command

    driver.quit() closes the browser after navigation.
  3. Final Answer:

    The Chrome browser opens example.com and then closes -> Option C
  4. Quick Check:

    Correct setup opens and closes browser [OK]
Hint: Correct setup opens URL then quits browser [OK]
Common Mistakes:
  • Assuming syntax error without checking code
  • Thinking driver.get does not open URL
  • Forgetting driver.quit closes browser
4. Identify the error in this Selenium WebDriver setup code snippet:
WebDriver driver = new ChromeDriver();
System.setProperty("webdriver.chrome.driver", "/drivers/chromedriver");
driver.get("https://example.com");
medium
A. driver.get() should be called before setting system property
B. System.setProperty must be called before creating ChromeDriver instance
C. ChromeDriver path should be set using driver.setPath()
D. No error, code will run fine

Solution

  1. Step 1: Check order of setting driver path

    System.setProperty must be called before creating ChromeDriver to locate the driver executable.
  2. Step 2: Identify consequence of wrong order

    Creating ChromeDriver before setting path causes runtime error as driver is not found.
  3. Final Answer:

    System.setProperty must be called before creating ChromeDriver instance -> Option B
  4. Quick Check:

    Set driver path before ChromeDriver creation [OK]
Hint: Always set driver path before new ChromeDriver() [OK]
Common Mistakes:
  • Calling driver.get before setting driver path
  • Using non-existent driver.setPath method
  • Ignoring order of setup steps
5. You want to run multiple Selenium tests in parallel using ChromeDriver. Which setup practice helps avoid conflicts and resource leaks?
hard
A. Manually kill Chrome processes after all tests finish instead of driver.quit()
B. Use a single ChromeDriver instance shared by all tests without quitting
C. Set the ChromeDriver path only once at the start of all tests and never again
D. Create a new ChromeDriver instance for each test and call driver.quit() after each test

Solution

  1. Step 1: Understand parallel test isolation

    Each test should have its own ChromeDriver instance to avoid interference.
  2. Step 2: Importance of quitting driver

    Calling driver.quit() after each test frees resources and closes browser properly.
  3. Final Answer:

    Create a new ChromeDriver instance for each test and call driver.quit() after each test -> Option D
  4. Quick Check:

    Separate driver per test + quit to avoid conflicts [OK]
Hint: New driver per test + quit after test avoids conflicts [OK]
Common Mistakes:
  • Sharing one driver instance across tests
  • Not quitting driver causing resource leaks
  • Relying on manual process killing
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard