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.

Practice

1. What is the main purpose of adding Selenium dependencies to a Java project using Maven or Gradle?

easy

A. To include Selenium libraries so you can write automated browser tests

B. To make the Java project run faster

C. To create user interfaces for the application

D. To compile Java code into executable files

Solution

1. Step 1: Understand Selenium dependencies

   Selenium dependencies provide the necessary libraries to control browsers automatically in Java projects.

2. Step 2: Purpose of adding dependencies

   Adding these dependencies allows your project to use Selenium features for automated testing.

3. Final Answer:

   To include Selenium libraries so you can write automated browser tests -> Option A

4. Quick Check:

   Selenium dependencies = automated browser tests [OK]

Hint: Dependencies add libraries needed for automation [OK]

Common Mistakes:

• Thinking dependencies improve runtime speed
• Confusing dependencies with UI design tools
• Assuming dependencies compile code

2. Which of the following is the correct Maven dependency snippet to add Selenium Java bindings in your pom.xml?

easy

A.
org.seleniumhq.selenium
selenium-server
3.141.59

B.
org.seleniumhq.selenium
selenium-java
4.10.0

C.
org.seleniumhq.selenium
selenium-webdriver
2.53.1

D.
org.seleniumhq.selenium
selenium-java
2.0

Solution

1. Step 1: Identify the latest stable Selenium Java dependency

   The latest stable Selenium Java binding is version 4.10.0 with artifactId 'selenium-java'.

2. Step 2: Check the correct groupId and artifactId

   The groupId must be 'org.seleniumhq.selenium' and artifactId 'selenium-java' for Java bindings.

3. Final Answer:

   Correct Maven dependency with version 4.10.0 and artifactId selenium-java -> Option B

4. Quick Check:

   Maven dependency for Selenium Java = org.seleniumhq.selenium selenium-java 4.10.0 [OK]

Hint: Use latest version and correct artifactId selenium-java [OK]

Common Mistakes:

• Using old Selenium versions
• Wrong artifactId like selenium-server or selenium-webdriver
• Incorrect version numbers

3. Given the following Gradle snippet, what will happen when you run your Java Selenium tests?

dependencies {
  testImplementation 'org.seleniumhq.selenium:selenium-java:4.10.0'
}

medium

A. Selenium libraries will be ignored during test runs

B. Selenium libraries will be included in the main application runtime

C. The project will fail to build due to missing dependencies

D. The Selenium Java libraries will be available only for test code compilation and execution

Solution

1. Step 1: Understand Gradle configuration scope

   Using 'testImplementation' means dependencies are available only for compiling and running test code, not main code.

2. Step 2: Effect on Selenium libraries

   Selenium Java libraries will be accessible during test execution but not included in the main application runtime.

3. Final Answer:

   Selenium Java libraries available only for test code compilation and execution -> Option D

4. Quick Check:

   testImplementation = test-only Selenium libs [OK]

Hint: 'testImplementation' means test-only dependency [OK]

Common Mistakes:

• Assuming Selenium is included in main runtime
• Thinking project build will fail
• Believing Selenium is ignored during tests

4. You added Selenium dependency in your Maven pom.xml but your test code shows errors like package org.openqa.selenium does not exist. What is the most likely cause?

medium

A. Selenium does not support Maven projects

B. Your Java version is too new for Selenium

C. You forgot to run mvn clean install or refresh dependencies

D. You wrote test code in the wrong package

Solution

1. Step 1: Check dependency installation process

   After adding dependencies, Maven needs to download and link them by running 'mvn clean install' or refreshing the project.

2. Step 2: Understand error cause

   The error means Selenium classes are not found because dependencies are not downloaded or linked yet.

3. Final Answer:

   Forgot to run Maven build or refresh dependencies -> Option C

4. Quick Check:

   Missing package error = missing dependency download [OK]

Hint: Run Maven build to download dependencies [OK]

Common Mistakes:

• Blaming Java version without checking dependencies
• Assuming package location causes error
• Thinking Selenium can't be used with Maven

5. You want to configure a Java project with Gradle to use Selenium 4.10.0 and also include WebDriverManager to manage browser drivers automatically. Which Gradle dependencies block is correct?

hard

A. dependencies {
implementation 'org.seleniumhq.selenium:selenium-java:4.10.0'
implementation 'io.github.bonigarcia:webdrivermanager:5.3.2'
}

B. dependencies {
implementation 'org.seleniumhq.selenium:selenium-java:3.141.59'
implementation 'io.github.bonigarcia:webdrivermanager:4.0.0'
}

C. dependencies {
testImplementation 'org.seleniumhq.selenium:selenium-java:4.10.0'
testImplementation 'io.github.bonigarcia:webdrivermanager:5.3.2'
}

D. dependencies {
compileOnly 'org.seleniumhq.selenium:selenium-java:4.10.0'
compileOnly 'io.github.bonigarcia:webdrivermanager:5.3.2'
}

Solution

1. Step 1: Identify correct versions and scopes

   Selenium 4.10.0 and WebDriverManager 5.3.2 are latest stable versions. Use 'implementation' to include these libraries in the main runtime since WebDriverManager manages drivers at runtime.

2. Step 2: Understand dependency scopes

   'implementation' includes dependencies in both main runtime and test code, which is necessary for WebDriverManager to function properly.

3. Final Answer:

   implementation 'org.seleniumhq.selenium:selenium-java:4.10.0' and implementation 'io.github.bonigarcia:webdrivermanager:5.3.2' -> Option A

4. Quick Check:

   Gradle implementation deps = selenium-java + webdrivermanager included in runtime [OK]

Hint: Use implementation scope for Selenium and WebDriverManager to include in runtime [OK]

Common Mistakes:

• Using old versions
• Using testImplementation which excludes runtime usage
• Using compileOnly which excludes runtime