Autemos ORION is the new release of Autemos, the AI-powered test automation platform. ORION brings existing test code, visual workflows and intelligent automation together. It adds Code to Test, Custom Code Blocks, Data-driven Test Execution, Code Sync, versioning and extended governance features. Quality, changes and results stay under your control.

TL;DR: ORION connects code-based test automation with visual workflows and extends Autemos with Custom Code Blocks, Code Sync, versioning, Data-driven Test Execution, Jira/Xray Reporting, Notifications, Edit from Here and Audit Logs. Your existing investments stay usable, and every change to the automation can be traced.

Software ships at shorter intervals, applications get more complex and quality expectations keep rising. Many companies have spent years building test automation: Playwright and Selenium tests, in-house frameworks, test runs in CI/CD pipelines and thousands of test cases in test management.

Teams still hit the same obstacles. Existing tests don't move easily into new tools, visual platforms reach their limits with complex logic, and changes to tests are hard to trace. Test data gets maintained in several places, and results have to be compared by hand across systems. As automation grows, so does the effort for maintenance, coordination and control.

Why does complexity grow along with automation?

Complexity in test automation appears once individual tests have to become a company-wide solution, since several roles with different needs then work on the same test suite. Modern frameworks automate browser actions, API calls and checks reliably, and AI helps with creation and maintenance.

In a company, 4 perspectives meet:

• Test automation engineers want to keep using existing frameworks and their own code.

• Business testers want to follow business processes and adapt tests without programming each time.

• Test managers need reliable results, traceable changes and a link to test management.

• IT leads have to make sure permissions, traceability and governance keep up.

Each of these needs often gets its own tool. Code lives in the repository, test cases in Jira, test data in spreadsheets, execution logs in other systems and business knowledge in the heads of individual employees. With ORION, we bring these worlds together on one platform.

Modern test automation has to be simple enough for business users, flexible enough for engineers and controllable enough for enterprises.

What's new in Autemos ORION?

ORION brings 8 new and extended capability areas that work together across the full lifecycle of automated tests.

Figure 1: Autemos ORION and its new features at a glance.

Code to Test: how do existing Playwright tests become visual workflows?

Code to Test turns existing, supported Playwright test code in Java into a visual workflow, using the designated Autemos annotations. The code becomes traceable test steps that you can view and keep editing in Autemos. You no longer have to choose between the effort of maintaining the legacy suite and an expensive rebuild in a new tool.

Figure 2: The Java/Playwright test and its Autemos workflow side by side. Each step maps to a place in the code.

Tests built up over years hold knowledge about business processes and system behavior. Engineers keep working with familiar technology, and less technical team members can follow each step in the visual workflow. Our comparison of Playwright and Selenium describes both frameworks in detail.

The scope has a clear limit: arbitrary application code does not become a test automatically. The current version focuses on supported, annotated Java/Playwright test code.

Custom Code Blocks: what if standard actions aren't enough?

Custom Code Blocks add your own program logic directly inside an Autemos workflow. A test still consists of visual steps and gets custom code only where it needs it. In customer projects we regularly see business rules, special checks and technical requirements that predefined actions don't cover.

Figure 3: An open Custom Code Block in a workflow. The script runs on the server in a sandbox and controls the browser or device through ctx commands.

On many no-code platforms, such a test can't be built at all, or the logic moves to an external solution. In Autemos it stays in the workflow. Business-focused testers use the visual features, and technical specialists extend the automation at the points that need more flexibility.

No-code where it should be simple. Code where it's needed.

Code Sync and versioning: how do you keep changes under control?

Code Sync detects supported changes to the generated test code, compares them with the workflow and applies them in a controlled way. Versioning makes workflow changes traceable and restores earlier versions when needed.

The code changes dialog has 3 steps:

1. Autemos shows the code generated at the last sync next to the current version in the Git repository.

2. "Workflow changes" lists each detected change, with a note if it can't be applied.

3. You decide whether to apply the changes to the workflow, accept only the baseline, ignore them or push to Git.

Figure 4: The code changes dialog shows the differences between code and workflow, including changes that won't be applied.

Teams can edit in their development environment and keep the link to the visual automation.

The DORA research program (DevOps Research and Assessment) explicitly lists "All supporting automated tests and any manual test scripts" among the artifacts that belong in version control (DORA, 2026). The code Autemos generates fits that approach.

Figure 5: A workflow's version history. Each version shows nodes and edges, code sync updates carry the commit, and earlier versions can be restored.

Anyone working on automation in a larger team has to be able to see its change history.

Data-driven Test Execution: how does one workflow cover many test scenarios?

Data-driven Test Execution runs one workflow with different datasets, so you don't rebuild the automation for each data variant. ISTQB describes data-driven testing as "A test automation approach in which test data is separated from a test script to allow its repeated execution with various test data" (ISTQB Glossary, 2026).

Business-heavy applications need this all the time. An insurance application handles different contract variants, a bank checks account types, currencies and permissions, an online shop works with different customer data and product combinations. The flow stays the same and only the data changes. Separate tests or hard-coded input values create duplicates and extra maintenance.

Figure 6: Selecting datasets before the run. Each named dataset produces one test run, here 4 runs from 4 datasets.

Autemos has built-in test data management: you can enter data directly in tables and reference it in workflows. The workflow describes what gets tested. The test data decides which values the test runs with. This split keeps the automation easier to maintain and easier for new team members to read.

Figure 7: The resulting test runs. Each dataset shows its status and links to its test report.

Jira/Xray Reporting: how do test results reach test management?

ORION reports automated test results back to Jira/Xray, so they show up where test planning, test control and quality assessment happen. A test run first produces a technical result. A test manager wants to know more: which requirements are covered, which test cases passed and where the risks are.

In many organizations, Jira with Xray is the central platform for these questions. With Autemos Polaris, we already strengthened the link between Xray test cases and the Autemos Recorder. ORION takes this integration further and cuts the handoffs between technical execution and business-side test management.

Figure 8: An Xray run in Autemos with linked tests, results and earlier runs. If Xray doesn't answer in time, Autemos reports the failed sync and offers a retry.

An automated test delivers its full value once the right people can get its result and make sense of it.

Edit from Here: how do you change a test without re-recording it?

Edit from Here resumes an existing workflow at a selected point and continues editing it with the Autemos Recorder. When an input field, a new validation or an extra process step arrives, the automated test doesn't need a full re-recording.

Figure 9: The Recorder continues an existing E2E test in an e-banking demo at the insert point. The following steps appear as "Up next".

This helps most with long E2E tests. You pick up at the right point and skip replaying the whole business process, which makes existing tests simpler and more targeted to extend.

Notifications: how do you hear about important test runs?

The extended Notifications in Autemos ORION tell you about important events around test runs directly in the platform. Tests start manually, on a schedule or from external processes, and more and more of them run in the background. The more of them you have, the more it matters to spot relevant events in time.

Figure 10: The notification center with the result of each test run, passed or failed.

Nobody has to watch every run. Your team can put its attention on the cases that need a decision.

Audit Logs: who changed what, and when?

Audit Logs make recorded activities and events in Autemos visible in one place, and they answer who made a change, which activity ran and when an event occurred. That matters for audits, failure analysis, operations and collaboration in larger teams.

Figure 11: The detail view of an audit event with timestamp, user, action, affected object and result.

In regulated industries, test automation has to work and be traceable. Since 17 January 2025, Art. 9(4)(e) of the EU's Digital Operational Resilience Act (DORA) has required financial entities to have ICT change management policies "to ensure that all changes to ICT systems are recorded, tested, assessed, approved, implemented and verified in a controlled manner" (EUR-Lex, 2022). Audit Logs supply the evidence from the test automation side, and the processes themselves stay with your organization.

With AI involved in creating or adapting tests, this counts even more. That calls for clear ownership and controllable processes.

What does Engineering Intelligence mean for your test automation?

At Autemos, Engineering Intelligence means connecting existing test code, visual workflows and AI on one platform, so the automation performs well, stays readable and stays under control. Each ORION feature handles a concrete task. Together they further dissolve the split between classic test automation and visual platforms.

Existing code stays usable. Business users can read and edit test flows, and technical specialists keep their flexibility. Test data can be reused, and changes and results stay visible. Built for Control means you decide how to build, extend and run your automation.

As with Polaris, many ideas for ORION came from customer projects. Our teams work with test automation in complex enterprise environments every day. We see where classic frameworks are strong, where visual tools make collaboration simpler and what teams need once automation outgrows single projects. Often teams already have the technologies and lack a connection between them.

Frequently asked questions

What is Autemos ORION?

ORION is a release of the AI-powered test automation platform Autemos. It extends the connection between existing test code and visual workflows and adds capabilities for data-driven execution, change management, reporting and traceability.

Can I bring existing Playwright tests into Autemos?

Yes, if the tests are prepared and annotated Java/Playwright test code. In its current version, Code to Test turns that code into visual Autemos workflows. Support for further variants is part of ongoing development.

Can I use my own program logic in Autemos?

Yes. Custom Code Blocks add your own technical extensions inside visual test workflows, so you can combine standard actions with your own logic.

What does Data-driven Test Execution give me?

It separates test logic from test data, so one workflow runs with different input data. That cuts duplicate test implementations and makes test variants simpler to maintain.

How does ORION support traceability?

Code Sync and versioning keep workflow changes under control. Jira/Xray Reporting connects technical test results with test management, and Audit Logs make recorded activities visible.

What comes next

Over the coming weeks, Autemos will present the ORION features one by one and show with concrete examples how to use them in practice. This continues the work we started with Polaris: we connect the parts of quality engineering more closely and create more room for technical flexibility and enterprise-wide control.

Successful test automation means creating tests faster, protecting existing investments, keeping complexity manageable and keeping quality high over time.

Autemos ORION. Engineering Intelligence. Built for Control.

Want to try ORION with your own tests and use cases? Book a personal demo and see how Autemos can take your existing test automation further.