The Problem
Automating browsers for testing, scraping, or evading bot‑detection often requires stitching together Selenium, proxy handling, device emulation, and CI integration. Teams spend time writing repetitive boiler‑plate, managing driver binaries, and keeping scripts stable across OSes and cloud providers.
What This Does
SeleniumBase ships a Python‑centric wrapper around Selenium WebDriver that adds a rich set‑of‑the‑box features: automatic driver download, built‑in stealth options, cross‑platform Docker support, and a declarative test syntax. The core library lives under the unrevealed seleniumbase/ package (referenced from README.md and the console‑script docs).
Example scaffolding is provided in examples/: examples/basictest.py shows a minimal test using BaseCase and the self.open() helper. examples/boilerplates/pageobjects.py demonstrates the Page‑Object pattern with BaseCase. examples/cdpmode/ contains raw Playwright/Chrome‑DevTools‑Protocol scripts (e.g., rawcdplogin.py) that illustrate how SeleniumBase can hand off to CDP for stealth or network interception.
The repository also includes CI pipelines (azure-pipelines.yml and several GitHub Actions) and a ready‑to‑run Dockerfile that installs the package and runs the test suite, enabling reproducible environments.
How To Use It
Setup – Install the published package (the repo does not expose a requirements.txt or setup.py, but the PyPI release is the canonical source):
python -m pip install seleniumbase
Alternatively, build the Docker image to work in an isolated container:
docker build -t seleniumbase:latest . docker run --rm -v $(pwd):/work seleniumbase:latest pytest examples/basictest.py
Configuration – No explicit config files are required for a default run. For advanced options (proxy, headless, stealth), the library reads command‑line flags (e.g., --proxy, --headless) documented in helpdocs/customizingtestruns.md. Environment variables such as SELENIUMBASEBROWSER can be set, but the repo does not ship a sample .env; users should follow the online docs.
Running it – Tests are ordinary pytest files that inherit from BaseCase. Execute a single example with:
pytest examples/basictest.py
For CDP‑mode scripts, run the raw Python file directly:
python examples/cdpmode/rawcdplogin.py
The console‑script entry point (seleniumbase run) is described in seleniumbase/consolescripts/ReadMe.md (linked from the main README) and can be used to launch tests with additional reporting flags.
Real‑World Use
A QA team can embed SeleniumBase in their CI pipeline to run cross‑browser regression suites. A typical Azure Pipelines step might look like: script: | python -m pip install seleniumbase pytest tests/ --html=report.html --self-contained-html displayName: "Run SeleniumBase tests"
The generated HTML report integrates with the built‑in dashboard (examples/examplelogs/ReadMe.md) for traceability.
Code Health & Issues
Low – Missing explicit dependency list – No requirements.txt or pyproject.toml in the repo; users must rely on PyPI metadata. Low – Absence of in‑repo setup.py – The source package is not present, making local development or contribution harder. Medium – Large example set – 180 files in examples/ increase repo size and may cause slower CI checkout; consider moving them to a separate examples repo. Low – Secret leakage risk – No obvious credential files, but the CDP scripts include placeholders for API keys; ensure they are never committed. Low – Test coverage – Only 17 test files are present despite a large feature surface; additional unit tests for internal utilities would improve confidence. Low – CI visibility – Azure Pipelines and GitHub Actions are configured, indicating automated testing; however, the pipeline scripts reference pytest without explicit install steps, relying on the Docker image.
Overall, the repository follows a conventional layout, includes CI, and provides extensive documentation links. No license issues are apparent (LICENSE file present).
The Bottom Line
SeleniumBase offers a mature, feature‑rich wrapper for Selenium that reduces boiler‑plate and supports stealth automation, with solid Docker and CI support. The main drawbacks are the lack of a local source package and a relatively thin test suite. It is well‑suited for teams that need quick, cross‑platform browser automation and are comfortable pulling the library from PyPI rather than building from source.