Selenium dependency configuration in Selenium Java - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Maven Dependency Scope for Selenium

In a Maven project, which dependency scope should you use for Selenium WebDriver to ensure it is available during test compilation and execution but not included in the final build artifact?

A compile

B test

C provided

D runtime

💡 Hint

Think about when Selenium is needed: only during testing, not in production.

The test scope in Maven means the dependency is available only during test compilation and execution. It is not packaged in the final artifact, which is ideal for Selenium WebDriver.

❓ Predict Output

intermediate

Result of Missing Selenium Dependency

What error will occur if you try to run Selenium WebDriver tests in a Java project without adding the Selenium dependency in your build configuration?

Selenium Java

import org.openqa.selenium.WebDriver;

public class Test {
    public static void main(String[] args) {
        WebDriver driver = null;
    }
}

A Runtime error: NullPointerException

B Compilation error: cannot find symbol WebDriver

C Compilation error: package org.openqa.selenium does not exist

D No error, code runs successfully

💡 Hint

If the Selenium library is missing, the compiler cannot find its classes.

Without the Selenium dependency, the compiler cannot find the org.openqa.selenium package, causing a compilation error.

❓ locator

advanced

Correct Maven Dependency for Selenium Java 4.10.0

Which of the following Maven dependency snippets correctly adds Selenium Java version 4.10.0 to your project?

A

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>4.10.0</version>
</dependency>

B

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-server</artifactId>
  <version>4.10.0</version>
</dependency>

C

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>3.141.59</version>
</dependency>

D

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-webdriver</artifactId>
  <version>4.10.0</version>
</dependency>

💡 Hint

Check the artifactId and version carefully.

The official Selenium Java client library artifact is selenium-java. Version 4.10.0 is the latest stable release. Other artifactIds or versions are incorrect for this purpose.

❓ framework

advanced

Configuring Selenium WebDriver with Gradle

Which Gradle dependency declaration correctly adds Selenium Java 4.10.0 for testing purposes only?

A compileOnly 'org.seleniumhq.selenium:selenium-java:4.10.0'

B implementation 'org.seleniumhq.selenium:selenium-java:4.10.0'

C runtimeOnly 'org.seleniumhq.selenium:selenium-java:4.10.0'

D testImplementation 'org.seleniumhq.selenium:selenium-java:4.10.0'

💡 Hint

Consider when Selenium is needed during the build lifecycle.

testImplementation ensures the dependency is available only during test compilation and execution, which is appropriate for Selenium WebDriver.

🔧 Debug

expert

Diagnosing Selenium Driver Not Found Error

You have added Selenium Java 4.10.0 dependency correctly, but when running tests, you get the error: "The path to the driver executable must be set by the webdriver.chrome.driver system property". What is the most likely cause?

A WebDriver executable (e.g., chromedriver) path is not set or not found

B Test class is missing @Test annotation

C Incorrect version of Selenium Java dependency

D Selenium dependency is missing from the project

💡 Hint

Selenium needs a browser driver executable to control the browser.

This error means Selenium cannot find the browser driver executable like chromedriver. You must set the system property webdriver.chrome.driver to the correct path.