Yes. The roadmap targets browser automation through an Idelium DSL executed by a W3C WebDriver backend, using a local browser or a reachable Selenium Grid.

Yes. Upload a Postman collection and add it to a test cycle. Use the safe built-in runner for deterministic requests or Newman when you need pm.test assertions, scripts, environment files and iteration data.

Idelium CLI supports Appium-based mobile tests. When a standard runner is not enough, plugin steps let you connect custom protocols, services and company-specific test logic to the same execution cycle.

Define the target environments in Idelium Web and reuse the same test cycle with the appropriate configuration. Idelium CLI receives the selected project, cycle and environment when execution starts.

Yes. Jenkins, GitLab, Bamboo or another pipeline can call Idelium CLI with the project, cycle and environment identifiers. The tests run close to your systems and the results return to Idelium automatically.

Idelium records the cycle outcome and step-level details. You can identify passed, failed or running tests and inspect request data, timings, assertions and execution errors provided by the selected runner.

Yes. The Docker stack provides a self-hosted Web, API and database platform, while CLI agents and optional Selenium, Appium or Newman runners can remain on isolated hosts inside your network.

Use the Idelium Docker quickstart for a local demo, configure a project and import a sample Selenium or Postman test. Then install Idelium CLI from PyPI and launch your first cycle.