Home

Idelium Docker wiki

Welcome to the Idelium Docker wiki. This documentation explains how to run the Idelium test automation platform from the Docker stack, how the services fit together, and how to execute native Idelium JSON, Idelium DSL, Selenium, Appium, or Postman/Newman-based cycles.

What Idelium does

Idelium is an enterprise test automation platform for designing, organizing, and executing end-to-end quality checks across web, mobile, and API channels. From a product perspective, it provides a central workspace where teams can define projects, environments, reusable steps, test cases, and execution cycles, then run them through Selenium, Appium, Postman/Newman, or custom plugins. Execution agents report structured results back to Idelium so users can inspect outcomes, diagnostics, screenshots, API responses, and historical runs from the web console.

The platform is designed to make test automation repeatable across local developer machines, CI pipelines, and managed execution hosts while keeping configuration, credentials, tenant data, and execution results under a governed administration layer.

Idelium DSL

Idelium also supports a versioned domain-specific language (DSL) for browser automation. DSL source expresses test intent with a small, deterministic command set such as open, click, write, wait, assert, bounded repeat blocks, reusable step definitions, and screenshots.

The DSL complements the native Idelium JSON action format:

• it is easier to read and review than deeply nested action payloads;
• it separates test intent from Selenium/WebDriver implementation details;
• it can be parsed, linted, validated, and converted to a stable AST before a browser is started;
• its explicit language version provides a compatibility boundary for future migrations;
• bounded control flow and the absence of arbitrary runtime commands make test execution more deterministic and safer for CI;
• declared secrets and runtime parameters can be redacted consistently from diagnostics and reports.

DSL v1 is deliberately browser-focused. Native Idelium JSON remains the right format for wizard-authored Selenium and Appium action sequences and for mixed runtime tests, while Postman collections remain the authoritative source for Postman/Newman execution.

DSL standards and contracts

The canonical DSL v1 standards are maintained in the Idelium CLI repository:

• DSL v1 specification defines normative syntax and runtime semantics.
• EBNF grammar defines the machine-readable grammar.
• AST contract and JSON Schema define the portable parsed representation.
• Getting started documents authoring, linting, and runtime parameters.
• Migration policy defines compatibility and upgrade expectations.

See Quick Start Idelium JSON Import for the equivalent native-action and DSL import examples.

Idelium is composed of:

• Idelium Web, the browser-based administration interface.
• Idelium API, the Laravel backend for authentication, configuration, projects, tests, cycles, and results.
• Idelium CLI, the execution agent used to run Selenium, Appium, Postman, and plugin-based steps.
• Idelium Docker, the reproducible local and release deployment topology.

Start here

1. Read Pre-requisite to prepare Docker, Git, OpenSSL, and the required sibling repositories.
2. Read Architecture to understand the enterprise topology and data flow.
3. Read the Roadmap to understand the product evolution path.
4. Read the Enterprise Roadmap for release phases, enterprise-readiness gates, epics, and implementation tickets derived from the console walkthrough.
5. Follow Start IAS to start the Idelium Administration Server.
6. Import the native demo-page JSON with Quick Start Idelium JSON Import.
7. Run a first browser scenario with Quick Start Selenium.
8. Run a first API scenario with Quick Start Test API Using Postman.

Demo login

For a local evaluation, start the stack with:

cd idelium-docker
./quickstart-demo.sh

Then open https://localhost and sign in with:

Email: admin@idelium.org
Password: admin

These credentials are only for local demo mode. Do not use them in production or in shared environments.

Security model for this wiki

The quickstart stores demo credentials under the ignored secrets/ directory. Do not paste generated passwords, API keys, session identifiers, private keys, or complete authorization headers into wiki pages, issues, screenshots, or support messages.

Repository layout expected by the stack

For local builds, keep the three application repositories as siblings:

workspace/
├── idelium-api/
├── idelium-docker/
└── idelium-web/

The Docker stack reads the adjacent API and Web checkouts, labels built images with source revisions, runs migrations through a one-shot initialization container, and exposes only the HTTPS frontend to the host.