Docker images for running Selenium Grid with Chrome, Firefox, and Edge, enabling scalable browser automation.
Docker Selenium is a collection of Docker images that package Selenium Grid components, allowing users to run browser automation tests in scalable, containerized environments. It provides pre-configured images for major browsers like Chrome, Firefox, and Edge, simplifying the setup and management of Selenium Grid for testing and CI/CD pipelines.
QA engineers, DevOps teams, and developers who need to run automated browser tests at scale, particularly in containerized or cloud-native environments.
It eliminates the complexity of manually configuring Selenium Grid by offering production-ready Docker images, supports dynamic resource allocation, and integrates seamlessly with orchestration tools like Kubernetes and Docker Compose.
Provides a simple way to run Selenium Grid with Chrome, Firefox, and Edge using Container Platform, making it easier to perform browser automation at scale
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports standalone, hub-node, and fully distributed modes for parallel test execution, with detailed Docker Compose examples for easy setup.
Provides images for amd64 and arm64 platforms, enabling cross-platform testing, though browser availability varies by architecture.
Automatically spins up Docker containers on-demand for each test session via configurable TOML files, optimizing resource usage.
Includes sidecar containers with ffmpeg for recording test sessions, with metadata-based naming and cloud upload capabilities via Rclone.
Offers deployment guides and Helm charts for running Selenium Grid in Kubernetes clusters, simplifying cloud-native orchestration.
Chrome and Edge are not available for ARM64 due to vendor constraints, forcing users to rely on Chromium or Firefox, which may not match production environments.
Video recording and all-in-one browser images are CPU-intensive, requiring significant shared memory and additional containers, as noted in the troubleshooting section.
Configuring Dynamic Grid involves mounting Docker sockets, managing TOML files, and handling network settings, which can be error-prone and requires Docker expertise.
Relies on upstream browser vendors for updates and multi-arch support, leading to inconsistencies like Chrome's absence on ARM64, as admitted in the README.