Selenium automation
Selenium test automation managed from your infrastructure
Idelium gives QA and engineering teams a self-hosted control plane for WebDriver-based browser tests: definitions stay centralized, execution stays close to the browser grid, and results return to one auditable workspace.
Execution workflow
How Selenium execution works
- 01
Model
Create projects, environments, reusable steps and test cycles in Idelium Web.
- 02
Retrieve
Idelium CLI downloads the selected cycle with its environment configuration.
- 03
Execute
The CLI runs WebDriver steps close to the application or forwards execution to Selenium Grid.
- 04
Review
Statuses and step-level details return to Idelium for quality analysis.
Use case FAQ
Common questions
Start from the Docker quickstart and model your first browser cycle with the Idelium DSL.
What is the browser automation direction?
The roadmap focuses on an Idelium DSL, canonical AST and W3C WebDriver execution backend.
Can I use my own Selenium Grid?
Yes. Execution can stay inside your infrastructure and use a reachable browser grid or local browser runtime.