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.