test.guide 2026 Q3

Appointments can now be supplemented with freely definable attributes in the form of name-value pairs. This allows structured additional information to be stored directly with the appointment and processed further.

For example, a Flow task that starts when the appointment begins can read these attributes for downstream automations and react accordingly.

The attributes can be managed in the appointment dialog and transmitted and retrieved via the Test Infrastructure REST API.

• Attribute names must be unique within a single appointment.
• Attributes for recurring appointments can be customized individually for each appointment in the series.
• The attributes are supported by the REST endpoints for creating, retrieving, filtering, and updating appointments.

In workflow automation, you can now specify on which TestResourceMachines (TRM) a flow is executed.

To do this, resource labels are assigned in the FlowAutomationPlugin. These labels are referenced by the flow triggers and automatically applied to newly created flow tasks.

As a result, flow tasks run only on machines that meet the necessary requirements, such as connected network drives, installed software, or specific firewall permissions.

For EXTERNAL_EVENT-type flow triggers, the required labels can also be overwritten via the REST API at startup. This allows you to dynamically determine which TRM a workflow runs on only when the task is created. This is useful, for example, for collecting artifacts generated after a test execution, uploading them to test.guide, and then cleaning up the machine.

In the user interface, known resource labels are suggested for autocomplete during trigger configuration.

For flow tasks, it is visible which TRMs are compatible or whether no matching machine was found.