Docker execution environment in Selenium Java - Framework Patterns

Framework Mode - Docker execution environment

Folder Structure

selenium-java-docker-framework/
├── src/
│   └── test/
│       └── java/
│           ├── pages/           # Page Object classes
│           ├── tests/           # Test classes
│           └── utils/           # Utility classes (e.g., Docker helpers)
├── docker/                    # Docker related files
│   ├── Dockerfile             # Docker image build instructions
│   ├── docker-compose.yml     # Compose file to run Selenium Grid and tests
│   └── entrypoint.sh          # Script to start tests inside container
├── config/
│   └── test.properties        # Test configuration (URLs, credentials)
├── pom.xml                   # Maven build file
└── README.md                 # Project overview and Docker usage instructions
  

Test Framework Layers

• Docker Layer: Contains Dockerfile and docker-compose.yml to build and run containers including Selenium Grid and test execution environment.
• Driver Layer: Selenium WebDriver setup configured to connect to remote Selenium Grid inside Docker.
• Page Object Layer: Java classes representing web pages with locators and actions.
• Test Layer: Test classes using TestNG or JUnit to run test scenarios.
• Utilities Layer: Helper classes for Docker commands, environment handling, and reusable functions.
• Configuration Layer: Properties files for environment variables, browser types, URLs, and credentials.

Configuration Patterns

• Environment Variables: Use Docker environment variables to pass browser type, Selenium Grid URL, and test environment URLs.
• Properties Files: Store test data and credentials in config/test.properties and load them in tests.
• Docker Compose: Define services for Selenium Hub, browser nodes, and test runner container with shared network.
• Profiles: Use Maven profiles to build and run tests locally or inside Docker containers.

Test Reporting and CI/CD Integration

• Test Reports: Generate HTML and XML reports (e.g., TestNG reports) inside the container and mount volume to host for access.
• Logging: Capture Selenium logs and Docker container logs for debugging.
• CI/CD Integration: Use Jenkins, GitHub Actions, or GitLab CI to build Docker images, start Selenium Grid containers, run tests inside containers, and archive reports.
• Fail Fast: Configure tests to fail fast on critical errors to save CI time.

Framework Design Principles

1. Isolate Tests in Containers: Run tests inside Docker containers to ensure consistent environment and avoid local machine dependencies.
2. Use Selenium Grid in Docker: Deploy Selenium Hub and browser nodes as containers for scalable parallel testing.
3. Externalize Configuration: Pass environment-specific data via environment variables or properties files to keep tests flexible.
4. Keep Docker Images Lightweight: Use minimal base images and clean up after builds to reduce image size and speed up CI pipelines.
5. Mount Volumes for Reports: Share test reports and logs from containers to host for easy access and analysis.

Self Check

Where in this folder structure would you add a new Page Object class for the Login page?

Key Result

Use Docker containers to run Selenium Grid and tests for a consistent, scalable, and isolated test execution environment.

Practice

1. What is the main benefit of using Docker for Selenium test execution?

easy

A. It provides a clean, consistent browser environment for tests.

B. It automatically writes test scripts for you.

C. It replaces the need for assertions in tests.

D. It runs tests only on local machines.

Solution

1. Step 1: Understand Docker's role in Selenium testing

   Docker creates isolated containers that have clean browser setups, avoiding environment conflicts.

2. Step 2: Compare options

   Only It provides a clean, consistent browser environment for tests. correctly states Docker provides a clean, consistent browser environment. Other options describe unrelated or incorrect features.

3. Final Answer:

   It provides a clean, consistent browser environment for tests. -> Option A

4. Quick Check:

   Docker environment = clean browser setup [OK]

Hint: Docker isolates browsers for consistent tests [OK]

Common Mistakes:

• Thinking Docker writes test scripts automatically
• Believing Docker removes need for assertions
• Assuming Docker only runs tests locally

2. Which Java class is used to connect Selenium tests to a browser running inside a Docker container?

easy

A. DockerClient

B. ChromeDriver

C. FirefoxDriver

D. RemoteWebDriver

Solution

1. Step 1: Identify the correct Selenium class for remote connections

   RemoteWebDriver is designed to connect to browsers running on remote servers or containers like Docker.

2. Step 2: Eliminate other options

   ChromeDriver and FirefoxDriver are for local browsers. DockerClient is unrelated to Selenium.

3. Final Answer:

   RemoteWebDriver -> Option D

4. Quick Check:

   RemoteWebDriver connects to remote browsers [OK]

Hint: Use RemoteWebDriver for Docker browser connections [OK]

Common Mistakes:

• Using ChromeDriver for Docker browsers
• Confusing DockerClient with Selenium classes
• Using FirefoxDriver for remote Docker sessions

3. Given this Java code snippet connecting to a Docker Selenium container:

URL url = new URL("http://localhost:4444/wd/hub");
ChromeOptions options = new ChromeOptions();
RemoteWebDriver driver = new RemoteWebDriver(url, options);
driver.get("https://example.com");
String title = driver.getTitle();
System.out.println(title);

What will be printed if the page title is "Example Domain"?

medium

A. http://localhost:4444/wd/hub

B. Example Domain

C. ChromeOptions

D. RemoteWebDriver

Solution

1. Step 1: Understand the code flow

   The code opens the URL "https://example.com" in a remote Chrome browser inside Docker and retrieves the page title.

2. Step 2: Identify the output of getTitle()

   The getTitle() method returns the page title, which is "Example Domain" for that URL.

3. Final Answer:

   Example Domain -> Option B

4. Quick Check:

   driver.getTitle() = "Example Domain" [OK]

Hint: getTitle() returns the page title string [OK]

Common Mistakes:

• Printing the URL instead of the title
• Confusing options object with title
• Printing class names instead of values

4. You run Selenium tests inside Docker but get a connection refused error at "http://localhost:4444/wd/hub". What is the most likely cause?

medium

A. The URL "http://localhost:4444/wd/hub" is misspelled.

B. The test code uses ChromeDriver instead of RemoteWebDriver.

C. Docker container is not running or Selenium Grid is not started.

D. The test script lacks assertions.

Solution

1. Step 1: Analyze connection refused error

   This error means the test code cannot reach the Selenium server at the given URL.

2. Step 2: Identify common Docker causes

   If the Docker container running Selenium Grid is stopped or not started, the connection will fail.

3. Final Answer:

   Docker container is not running or Selenium Grid is not started. -> Option C

4. Quick Check:

   Connection refused = server not running [OK]

Hint: Check Docker container status if connection refused [OK]

Common Mistakes:

• Blaming ChromeDriver usage for connection errors
• Ignoring container running status
• Assuming URL typos without verification

5. You want to run parallel Selenium tests in Docker using RemoteWebDriver with ChromeOptions. Which approach best ensures tests run independently without interference?

hard

A. Start multiple Docker containers each running a Selenium node and connect each test to a different container URL.

B. Run all tests sequentially in a single Docker container using the same RemoteWebDriver instance.

C. Use ChromeDriver locally and ignore Docker for parallel tests.

D. Run tests in one container but share the same RemoteWebDriver instance across threads.

Solution

1. Step 1: Understand parallel test isolation needs

   Parallel tests require isolated browser sessions to avoid state conflicts.

2. Step 2: Evaluate Docker container usage

   Starting multiple containers with separate Selenium nodes allows independent browser sessions for each test.

3. Step 3: Eliminate unsafe options

   Sharing RemoteWebDriver instances or running sequentially defeats parallelism. Using local ChromeDriver ignores Docker benefits.

4. Final Answer:

   Start multiple Docker containers each running a Selenium node and connect each test to a different container URL. -> Option A

5. Quick Check:

   Parallel tests need isolated containers [OK]

Hint: Use separate containers for parallel Selenium tests [OK]

Common Mistakes:

• Sharing RemoteWebDriver instance across threads
• Running tests sequentially to avoid conflicts
• Ignoring Docker and using local drivers