Selenium dependency configuration in Selenium Java - Framework Patterns

Framework Mode - Selenium dependency configuration

Folder Structure

selenium-java-project/
├── pom.xml
├── src/
│   ├── main/
│   │   └── java/
│   │       └── com/example/app/  
│   └── test/
│       └── java/
│           └── com/example/tests/
│               ├── pages/
│               ├── tests/
│               └── utils/
└── README.md
  

Test Framework Layers

• Dependency Management Layer: Managed by Maven through pom.xml to include Selenium and other libraries.
• Page Object Layer: Java classes under src/test/java/com/example/tests/pages representing web pages.
• Test Layer: Test classes under src/test/java/com/example/tests/tests containing test methods using TestNG or JUnit.
• Utility Layer: Helper classes under src/test/java/com/example/tests/utils for reusable code like waits or driver setup.
• Configuration Layer: Maven pom.xml and optionally property files for environment and browser settings.

Configuration Patterns

Use Maven pom.xml to declare Selenium dependencies with specific versions.

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

Use Maven profiles or property files to manage different environments or browsers.

Example: src/test/resources/config.properties to store URLs and credentials.

Test Reporting and CI/CD Integration

• Integrate TestNG or JUnit reports generated during test runs.
• Use Maven Surefire Plugin to run tests and generate reports.
• Configure CI/CD pipelines (e.g., Jenkins, GitHub Actions) to run tests on code commits.
• Publish reports as build artifacts or use plugins for HTML reports.

Best Practices

• Pin Selenium dependency versions in pom.xml to avoid unexpected breaks.
• Use Maven dependency management to handle transitive dependencies cleanly.
• Keep configuration (URLs, credentials) outside code in property files.
• Use profiles in Maven for different environments (dev, test, prod).
• Regularly update dependencies but test compatibility before upgrading.

Self Check

Where in this folder structure would you add a new utility class for custom waits?

Key Result

Manage Selenium dependencies via Maven pom.xml with clear versioning and separate configuration files.

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