The roadmap positions Idelium as a domain-specific test automation framework, not a browser-recorder format importer. The goal is a modern language with an open-standards execution backend.
Language first
Idelium is moving toward a simple, stable and documented DSL with a clear AST representation for every feature.
- Versioned DSL specification.
- Canonical AST serializable as JSON.
- Readable syntax for test authors and maintainers.
Standards-based execution
Execution starts from the W3C WebDriver standard and evolves toward optional WebDriver BiDi capabilities for richer diagnostics.
- Browser session management for Chrome, Firefox and Edge.
- Step-by-step execution with waits, selectors and assertions.
- Future browser events, console logs and network observation through BiDi.
Implementation steps
- Define DSL v1Stabilize commands such as open page, click, enter text, waits, assertions, navigation and screenshots.
- Build parser and ASTSeparate parsing, canonical AST and execution responsibilities so each script can be validated and serialized.
- Execute through WebDriverRun scripts through a reliable WebDriver runtime, then add reporting, CI integration and optional BiDi diagnostics.
Common questions
- Is Idelium tied to a browser-recorder format?
- No. The roadmap explicitly avoids tying Idelium to a proprietary authoring format and focuses on its own DSL.
- What execution standard does Idelium target?
- The execution foundation is W3C WebDriver first, with WebDriver BiDi planned for advanced diagnostics.