one:cx Editions

With report management, test runs can be viewed and analyzed from every angle:

• test runs and regression tests can be compared
• test steps can be tracked
• trends can be identified and errors evaluated

All test reports are stored in a database. With extensive filter and evaluation options, the database helps users to quickly identify relevant reports.

Teams can:

• collaborate on results and reevaluations
• share reports via links or subscriptions

This ensures that no important results are overlooked.
The central collection of all test data provides the ideal foundation for collaboration and AI-driven data evaluations.

Configurable widgets are used to provide users with meaningful dashboards of their test results.

Similarities can be determined and automatically summarized based on classified error patterns. This saves users time when regression tests are evaluated daily.

With release management, structured overviews of test results are provided to support objective release decisions.

• Testing goals can be defined, and results can be organized using any metadata (e.g., requirements, test level, etc.).
• Actual coverage can be tracked in real time and compared with the initially defined target state.
• Completed test campaigns can be protected from changes by final approval and archiving.

Jira issues for bugs found can easily be created based on templates. Issues can be linked with new results. Views of issues can be created based on test results.

Test resources are managed in a central inventory, where users can:

• create new entries
• delete obsolete ones
• assign attributes such as ownership or capability tags to facilitate test‑case matching

The system continuously records status information, including:

• a heartbeat to verify reachability
• operational metrics such as CPU load and RAM usage

A remote desktop session can also be launched via downloading stored RDP files to interact directly with any listed resource.

Important information about each test resource is automatically captured:

• Which software version is installed?
• What hardware is connected?
• When was the software version changed?
• How often is the resource used for manual or automated testing?

Users will have the answers easily.

The report is automatically pre‑processed and queued, guaranteeing that every detail is preserved — even during brief service interruptions or scheduled maintenance.

Managing different test resources across multiple teams and running automated tests on the same resources is a big challenge.

With infrastructure booking, the resources needed can be reserved by users.

Calendar‑controlled test execution can be set to abort running test jobs based on specific calendar bookings.
In the settings, it can be chosen whether certain bookings are allowed to interrupt ongoing executions and how the interrupt should be executed.

Software‑in‑the‑Loop (SiL) tests are run on virtual worker nodes dynamically provided by one:cx. Only a container image needs to be provided by users, everything else is handled automatically. Tests, analyses of large traces, or workflows can be run on extra nodes.

Application lifecycle management enables end-to-end traceability from requirements to testing and releases. This supports regulatory requirements, improves product quality, and reduces project risks.

With the ALM integration framework, all the flexibility needed to interlink ALM‑based management processes and ALM‑based traceability with continuous testing and continuous integration processes based on one:cx is provided.

Based on this framework, template workflows are available for frequently used ALM systems like PTC Codebeamer, Jama Connect, IBM ETM, and Siemens Polarion.

With remote test execution, a playbook can simply be started that reproducibly sets up the test environment, obtains necessary artifacts (e.g. via git), runs the tests, and cleans everything up again — allowing efficient use of valuable HiL systems, even in distributed teams.

Automated executions can be scheduled using a CRON‑like expression to define when and how often a playbook runs. Task priorities ensure that the most important playbooks are executed first.

A test order contains, among other things, a name, a start and end date, and a defined scope, which is specified in an ALM system, e.g. a Codebeamer tracker.

Test order management enables tests to be planned and executed by users.
Manual and automated parts of the scope can be unified in one process.

In scaled setups with many different test environments, it is important that resources are used efficiently. Test plans should therefore be executed in parallel and distributed as much as possible to save time.

one:cx matches the test environments based on the recognized and required equipment, giving users a clear overview even in large test farms.

Automated executions can be added or scheduled directly via a calendar, enabling team‑wide coordination of who uses which test bench and when.

Higher‑priority jobs can interrupt and abort running tasks, ensuring that critical work is always completed first.

As part of the enterprise agreement, users may receive as many ecu.test licenses as needed to cover all validation activities.

Time‑consuming test preparation is drastically reduced. With ecu.test agent, test case development is now faster than ever before, because test implementations are generated directly in no time at all by the assistant.

The data.app agent democratizes access to complex test data analysis. It acts as an intelligent interface between raw technical data and decision‑critical information. Regardless of users’ technical background, customized visualizations are generated by the agent – from in‑depth debugging charts for test automation engineers to aggregated KPI dashboards for upper management.

Custom test‑process automations are built using simple blocks with the workflow automation. These user‑defined workflows are started by events that can originate inside one:cx (e.g. a new artifact/report upload or a release being locked) or outside the platform (e.g. a status change in Jira via webhook).

Starting with the flow edition, all functionalities are available without restriction.

New software versions should be integrated and tested quickly. To accomplish this, approvals should be set automatically when the required quality is achieved, supporting collaboration. In the platform, processes are modeled with quality gates.

Quality gates or Q‑Gates make software quality measurable and enforce clear criteria before automatically moving to the next stage (e.g. integration or release).

It is possible to pass artifacts on to other teams, inform colleagues via email, or start further tests if a gate is passed successfully. Different kinds of Q‑Gates help users set up very flexible criteria.

Staging facilitates collaborative work across departmental boundaries and represents the next step of process automation.

Q‑gates can be shared between different projects, such as sub‑processes, teams, or stages. The shared state is accessed through “pull Q‑gates.”

This approach makes it possible to work independently on individual projects while still sharing important information across interfaces, making dependencies and the entire process visible to users.

As strategic partners, users are part of a strategic platform governance board with direct transformation advisory and active contribution to the product roadmap. Users benefit from global premium support by tracetronic and early access to new platform features. Joint innovation projects are driven together, and KPI dashboards tailored to users’ vehicle projects are provided.

All the foundation needs to run secure, compliant, and fully observable test‑processes is provided: role‑based access control, secure secret management, and full‑stack observability.

By syncing one:cx with the customer’s IAM, user group memberships are imported automatically and mapped to one:cx roles. When users log in with their corporate credentials, the correct permissions are instantly received – eliminating duplicate accounts and ensuring consistent security. This zero‑touch provisioning enables immediate, right‑level access.

Enterprise‑level compliance is provided by the platform by enforcing policies derived from regulatory requirements across all global instances. Compliance settings such as report retention policies can be centrally defined and applied consistently throughout the organization. In addition to test and report data, monitoring data, quality gate plans, and other relevant artifacts are also covered by these policies. This ensures that all critical data types are managed, stored, and retained in a compliant and auditable manner.