English Changelog test.guide

[FEATURE]: With the help of the new dashboard widget Report Filter (table view), the results of test case executions can be displayed in a table based on a project filter. Optionally, up to three attributes or constants can be selected for display, for example, Requirement ID, Pipeline Link, or System Under Test (SUT).

[FEATURE]: The Q-Gate plan overview has been updated so that filtering of Q-Gate plans is now possible. The default filter automatically hides invalidated and finalized plans.

[FEATURE]: To simplify the exchange of information between Shared Q Gates and Pull Q Gates, the behavior has been extended so that the attributes of the Shared Q Gate are automatically available to the Pull Q Gate (in the GUI and via API).

[FEATURE]: The following new placeholders are available in the review and issue tracker templates: {testcase:verdict}, {testcase:description}, {review:reevaluation}, and {review:customevaluation}.

[FEATURE]: As a server administrator, I can configure an inactivity notification that is sent to users who, for example, have not logged in for six months and may soon be removed from test.guide.

[FEATURE]: The ATX generator option captureSpecialTestSteps has been extended to include the test step IfThenElse.

[FEATURE]: The release filter has been expanded to include filtering of the release start date. This now makes it possible to filter time ranges of releases more easily.

[FEATURE]: The flow.kit bundle for workflow automation has received the following improvements:

[FEATURE]: Appointments in test resource calendars can be easily copied using drag and drop.

[FEATURE]: Activity distributions can now also be retrieved as JSON via the test infrastructure REST API endpoint POST /api/testinfrastructure/activitydistribution/export/.

[CHANGED]: The changelog and user documentation have also been redesigned.

[CHANGED]: When creating new file repositories, the only type of connection available is now Depository from artifact management. However, existing file repositories of other types can still be used and edited. We are making this change so that we can better use the advantages of artifact management in the report filter in the future.

[CHANGED]: The Release Detail Attribute Overview has been redesigned to make it easier to read.

[CHANGED]: The endpoint GET /testCaseExecution/{tceId} of the Report Management API has been updated so that the descriptions for the corresponding test case arguments are now also returned.

[CHANGED]: ⚠️ Updating the underlying framework for the REST APIs has changed how empty data structures are handled. Empty data structures are no longer omitted from the JSON response objects of the endpoints, but are now actually output as empty objects or arrays.

[CHANGED]: For the report database, a validating JDBC connection pool is now used to improve the reliability of the database connections.

[CHANGED]: If an LDAP configuration is used for authentication, it is now possible to specify a Manager Distinguished Name (DN) that is itself outside the User Organization Unit.

[DEPRECATED]: Due to a change in the H2 database, which can be used in test.guide for evaluations, we will no longer be able to guarantee backward compatibility in the future. We therefore recommend using Postgres databases directly for evaluations or switching to them.

[DEPRECATED]: The old API endpoints POST /api/upload-file and GET /api/upload-file/status/{id} are deprecated and will be removed in a future release. To upload, use the official report upload API /api/report/reports.

[DEPRECATED]: The old API endpoints POST /api/archive/download and GET /api/archive/download are deprecated and will be removed in a future release. To download file attachments of reports from file repositories, use the official API /api/report/files/{fileId}/download.

[DEPRECATED]: The value field on the SCM REST API in package and project attributes of the test case index is deprecated and will be removed in the release 1.212.0.

[REMOVED]: The Shutdown menu item has been removed from the system settings. As an administrator, test.guide can instead be shut down normally via the system or Docker/Kubernetes or systemd.

[FIXED]: Switching to Filter by report ID caused users to be logged out of the History page if they switched to another page without performing any further filter operations. This issue has been fixed.

[FIXED]: Fixed an issue where the rendering of graphs for flow tasks and Q-gate plans did not work in the latest Microsoft Edge browser.

[FIXED]: Fixed an issue with advertising artefacts from AWS S3 storages.

[FEATURE]: In test.guide, the stimulation and analysis packages from ecu.test are now linked directly to each other in the test case details and displayed in order to speed up the evaluation of the trace analysis.

[FEATURE]: When creating or editing a report filter widget (trend chart) in the dashboard, you can now specify the time zone in which the data should be displayed. Previously, the server time zone was always used for this purpose.

[FEATURE]: In the test resource overview in test infrastructure management, saved filters can now also be accessed directly via their ID using a URL.

[FEATURE]: Existing test resource filters of a test.guide project can be queried via API using the new test infrastructure REST API endpoint GET /api/testinfrastructure/testresourcefilters.

[FEATURE]: The flow.kit bundle for workflow automation has received the following improvements:

[FEATURE]: The Pull-Q gates have been expanded to now display automatic links to the Share-Q gates behind them. This makes navigation between the two gate types much easier.

[FEATURE]: AWS S3 Storages in the artifact management support advanced settings for server-side encryption.

[CHANGED]: If a description or instruction is defined for a Q-Gate, it is automatically displayed when the Q-Gate dialog box is opened.

[CHANGED]: When you click on a Manual or Approval Q-Gate in a started Q-Gate plan, the dialog for switching the Q-Gate opens automatically.

[CHANGED]: The Q-Gate Plan attribute overview has been redesigned to make it easier to read.

[CHANGED]: In test.guide, the table actions are currently being redesigned in many sections. The goal is to define a standard action that can be used directly, saving users clicks for standard workflows.

[CHANGED]: Since there was always some confusion with the naming of cleanup or auto-remove rules, these have now been uniformly renamed as remove rules.

[CHANGED]: The endpoint GET /api/testinfrastructure/testresourcemachines/{trmId}/data of the Test Infrastructure REST API now also returns the component states of a test resource machine.

[CHANGED]: The Docker image for the test.guide ResourceAdapter has been revised.

[REMOVED]: The unofficial API GET / testcase-details-filter/{tceId} from test.guide 1.42.0 has been removed. Instead, the official API GET /testCaseExecution/{tceId} is available in the Report Management API.

[REMOVED]: The unofficial API GET /testcase-report-filter from test.guide 1.42.0 has been removed. Instead, the official API POST /testCaseExecutions/filter is available in the Report Management API.

[REMOVED]: Support for PostgreSQL 13.x has been discontinued as announced! From now on, PostgreSQL version >=14 is required.

[REMOVED]: As announced, the ecu.test ATX Generator will now only be officially supported from ecu.test version ≥ 2023.2.

[REMOVED]: Due to the relocation of the TestResourceMachine (TRM) detail pages, their URLs have changed. The old URLs (containing monitoring) have now been removed as announced.

[REMOVED]: Moving the Activity View of Test Resources changed the URL of the page. The old URL (containing monitoring) has now been removed.

[FIXED]: When individual playbook steps were cancelled, the entire playbook execution was cancelled and the teardown steps were not executed. This issue has been resolved.

[FIXED]: Users who are registered in a large number of test.guide projects (> 10) may not have been able to easily access other projects via the navigation bar. This issue has been resolved. In this context, we have also ensured that the projects are displayed in alphabetical order.

[FIXED]: When uploading reports via drag and drop using the GUI, the available X2ATX converters were not displayed. This problem has been fixed.

[FEATURE]: The flow.kit bundle for workflow automation has received the following improvements:

[FEATURE]: In order to automate the synchronization of system groups, the User Management REST API has been extended to include the POST | GET /config/systemGroups/synchronization endpoints.

[FEATURE]: When using ecu.test packages or projects in a playbook, certain environment variables can be accessed.

[FEATURE]: The new ATX option archiveRecordingsExcludeFile can be used to exclude specific trace files from saving, which is enabled by the archiveRecordings option. This prevents unnecessarily large video recordings from being transferred and stored, for example.

[CHANGED]: When a Share-Q-Gate is set up, this is now indicated more clearly by an icon.

[CHANGED]: When sending project filter emails, if the email is very large due to the number of results, it will be automatically truncated with a corresponding note. This ensures that it can still be displayed in the email program.

[CHANGED]: The JiraJql block in Workflow Automation no longer throws an error if no tickets are found.

[CHANGED]: The filter panel in the test resource management is now more compact and collapsible.

[CHANGED]: The GET /api/testinfrastructure/testresourcemachines/{trmId}/data endpoint of the Test Infrastructure REST API now also returns the connection state (heartbeat) of a test resource machine.

[CHANGED]: Previously, the quick filter Today was based on the server’s time zone, but now it is based on the user’s time zone.

[DEPRECATED]: In the report management API GET /testCaseExecution/{tceId}, the field downloadUrl in the artifacts FileReference is marked as deprecated. The artifact can be accessed via the new endpoint GET /files/{fileId}/download.

[DEPRECATED]: The endpoint GET /ap/v2/monitoring/resources of the Monitoring REST API is deprecated and will be removed in a future release.

[DEPRECATED]: The endpoint GET /api/v2/monitoring/heartbeat of the Monitoring REST API is deprecated and will be removed in a future release.

[FIXED]: When uploading reports from ecu.test via the ResourceAdapter TestGuideUploadPlugin, some error messages were not returned to ecu.test. This issue has been fixed.

[SECURITY]-[FEATURE]: Authentication via OpenID Connect now also supports OpenID Connect RP-Initiated Logout. This means that when you log out of test.guide, you will also be logged out of the OpenID provider.

[FIXED]: Filtering for playbooks with a specific label failed with an error message via the REST API. This issue has been fixed.

[FEATURE]: When filtering playbook histories, playbook labels can also be AND-linked.

[FEATURE]: When filtering artefacts by attributes, attribute values can be negated.

[FEATURE]: The flow.kit bundle for the Workflow automation has the following improvements:

[FEATURE]: In the Test Resource Overview in Test infrastructure management, attributes of test resources (TRs) and their values can now be displayed directly in the table.

[FEATURE]: The most recent monitoring states of a Test resource machine (TRM) can be queried via the new endpoint GET /api/testinfrastructure/testresourcemachines/{testResourceMachineId}/data in the Test Infrastructure REST API.

[CHANGED]: The name of the test case is now also explicitly displayed in the test case detail view. This makes it easier to analyze results from the grouping filter, for example.

[CHANGED]: The endpoint GET /testCaseExecution/{tceId} of the Report Management API has been extended so that the description for the corresponding test case execution is now also returned.

[CHANGED]: If OpenID Connect is used and I, as a user, am already logged in at the Identity Provider (IdP), I will be automatically logged in when opening a link to test.guide.

[CHANGED]: Various Windows plug-ins in ResourceAdapter now use Windows PowerShell directly instead of the outdated Windows library “wmic” to query system information from the operating system.

[CHANGED]: When creating a new test resource in the test infrastructure management, a calendar is now always created automatically.

[FIXED]: When using PRF reports from ecu.test, test.guide may have incorrectly displayed the trace analysis plots in the test case detail views. This issue has been fixed.

[FIXED]: In workflow automation, it was possible to create flow tasks of type EXTERNAL_EVENT for disabled flow triggers. This issue has been fixed.

[FIXED]: A fixed encoding was always used when uploading coverages. When uploading via the REST API, the server’s system encoding was used, and when uploading via the UI, UTF-8 was used. Now, the encoding of the coverage XML file is used, if available. Otherwise, UTF-8 is used.

[FEATURE]: First of all, thank you very much for your feedback on the new UI 🙏. The biggest issue, navigation in test.guide, has been redesigned based on your feedback.

[FEATURE]: For the connection to Jira, a configuration for Jira Cloud and Jira Data Center is now available. This distinction is necessary because Jira Cloud behaves differently in some respects. Existing Jira connections will be migrated automatically.

[FEATURE]: In Workflow automation, you can now query the details of individual appointments using their ID.

[FEATURE]: Usability: The review page can be opened in a new tab, making it easier to compare with the test case details.

[FEATURE]: In playbook filter steps, attribute values can be negated when defining the filter.

[FEATURE]: Artifacts can be made available as links in the artifact management if they have been previously uploaded to an Azure Blob Storage.

[FEATURE]: Passwordless authentication via an IAM role is possible for AWS S3 storages in the artifact management.

[FEATURE]: To reopen complex filters for test resources more quickly, you can now save and load filters under Test infrastructure  Test resources.

[FEATURE]: Descriptions can now be added to Q-Gates. This makes it possible to better define manual process steps in the Q-Gates.

[FEATURE]: When switching Manual or Approval Q-gates, it is now possible to specify a reason in order to document the decision more clearly.

[FEATURE]: To improve the automation of Q-Gate plans, a flag can be set in Approval Q-Gates to ensure that they switch automatically when all inputs are PASSED.

[FEATURE]: To improve navigation in Q-Gate plans, you can click on a Q-Gate to navigate to the respective actions in the associated table.

[FEATURE]: The flow.kit bundle for the Workflow automation has the following improvements:

[FEATURE]: In Workflow automation, flow tasks can now also be filtered by their creation date.

[FEATURE]: With the new endpoint GET /api/testinfrastructure/appointments/{appointmentId} of the Test Infrastructure REST API, the details of individual appointments can be queried using their ID.

[FEATURE]: As server manager, I can deactivate the connection to the monitoring database under System configuration  Monitoring.

[FEATURE]: With two new placeholders in the Issue Tracker Templates, plain username can now also be used when creating a ticket.

[FEATURE]: In Workflow automation, it is now possible to react to the complete execution of a playbook run.

[DEPRECATED]: PostgreSQL 13.x support will be discontinued in mid November 2025! PostgreSQL in version >=14 is required afterwards.

[DEPRECATED]: Support for Java 17 will be discontinued at the end of October 2026. From then on, at least Java 21 will be required, which is the next Java version with long-term support.

[FIXED]: In the PDF test summary reports that were generated using the included report design, or a design derived from it, the test plan was not added as a filter expression when opening the test.guide result filter link for the individual test plans listed.

[FIXED]: An issue in the Mapping upload rules has been resolved. Under certain circumstances, this could prevent an upload to test.guide.

[PERFORMANCE]: 🚀 The performance of processing upload rules has been improved, so uploads now process faster.

[FEATURE]: After ten years, it was time to give test.guide a new, more modern look. As part of the UI changes, we also made some UX improvements. We look forward to your feedback!

[FEATURE]: The Approval Q-Gate now also allows you to configure project roles. When specified, you can specify which project role a person needs in order to be able to switch the Approval Q-Gate.

[FEATURE]: To ensure a clear overview of current and completed Q-Gate plans, these are now displayed separately.

[FEATURE]: With the new review setting Allow on-the-fly tag creation, it is possible to add new tags when automatically creating reviews.

[FEATURE]: Workflow automation has been extended with flow triggers for calendar entries of test resources.

[CHANGED]: Project notifications can now also be sent directly to specific users in the project.

[FEATURE]: The current ALM Octane version 25.3 is supported.

[CHANGED]: To ensure safe operation, a new limit for the result filter has been implemented.

[DEPRECATED]: The LDAP functionality Configure Employee Directory will be removed from test.guide in six months. If you still need this functionality despite OpenID Connect, please contact us at support@tracetronic.com.

[PERFORMANCE]: 🚀 The performance for loading the detail page for extensive flow tasks has been improved.

[FEATURE]: With the next ecu.test version 2025.3, trace.xplorer will support a new URL signal called Link to test case execution when exporting key indicators from test.guide. This provides a link to the results page in test.guide for each test run.

[FEATURE]: The flow.kit bundle for the Workflow automation has the following improvements:

[FEATURE]: In the Workflow automation, invalid flow sources are now detected more quickly:

[FEATURE]: Test executions can be aborted by calendar bookings of test resources.

[FEATURE]: Test case executions generated by test execution tasks also receive the constants TT_PLAYBOOK_HISTORY_ID and TT_PLAYBOOK_HISTORY_REVISION.

[FEATURE]: To make it easier to automate checking user project permissions, the following endpoint has been added to the user management REST API: GET /project/{projectId}/users.

[FEATURE]: With the new endpoint GET /api/testinfrastructure/configurations of the Test Infrastructure REST API, the configurations of a Test Resource Machine (TRM) can be retrieved.

[CHANGED]: The Quality Gates have left Dev Preview status.

[CHANGED]: The display of the Customer Report Fields in the test plan detail view has been changed so that all values of the fields from the test plan are now always displayed—even if the field was not set in a test execution.

[CHANGED]: It is possible to rename existing project roles.

[FIXED]: It could happen that dashboards were not updated at the specified interval when multiple test.guide instances were connected via a proxy.

[FIXED]: Flow tasks with the event type EXPORT_TEST_CASE_REPORTS, which was removed in version 1.197.0, are removed during the upgrade.

[FIXED]: In the GenericUserCode block in flow.kit, the handling of default values has been corrected. Previously, parameters were correctly evaluated as optional, but default values were not applied.

[FEATURE]: The flow.kit bundle for the Workflow automation has the following improvements:

[FEATURE]: The reference fields of defects and manual runs in Octane can now be set using either the ID or the label.

[FEATURE]: In playbook filter steps parameter values can be interpreted as list.

[CHANGED]: In the details of the started Q-Gate plans, the Q-Gate graph is now displayed directly below the metadata.

[CHANGED]: The endpoint GET /testCaseExecution/{tceId} of the Report Management API has been extended so that the folderPath for the respective execution is now also returned.

[CHANGED]: The endpoint GET /roles of the User Management API has been changed so that project members without project manager rights can now also query roles.

[CHANGED]: Until now, when using the Json2ATX plug-in, the first test case execution was used to specify the timestamp of the test plan. Now, the timestamp from the test plan is used.

{
    "name":"Testplan",
    "timestamp":1662631048000,
    "testcases":[
        {
            "@type":"testcase",
            "name":"TestCase",
            "verdict":"NONE",
            "description":"My Description",
            "timestamp":1662631050000,
            "executionTime":578,
            ....
        }
    ]
}

[FIXED]: For PDF documents exported via the REST API, the links to the test.guide result filter have instead led to the project selection since a change in version 1.197.0, as the project ID was missing from the link.

ATTENTION!!!: When the new test.guide version is launched, the monitoring database will be automatically migrated in order to merge the TRM attribute entries at the TR level (see PREVIEW entry). We recommend that you back up the database before launching the new version. test.guide will remain accessible during the migration.

[PREVIEW]: In the Test Infrastructure module, the attributes have been moved from the Test Resource Machines (TRM) level to the Test Resource (TR) level. This makes it possible to describe test resources in general terms using attributes, making them easier to manage in test.guide.

[FEATURE]: To simplify database configurations in cloud environments, they can now also be configured using environment variables instead of the GUI.

[FEATURE]: When using OpenID Connect, it is now possible to specify a claim that contains the company name. In combination with the system group synchronization, this enables new users to directly get started within their associated projects without undergoing the registration process.

[FEATURE]: Manual connection checks for storages of the artifact management can be performed without entering credentials.

[FEATURE]: Certain storage configurations in the artifact management can be edited without re-entering the credentials.

[CHANGED]: If a Q-gate plan has not been started, the Q-gate names can be edited.

[REMOVED]: The project view under Monitoring  Project view has been removed as announced.

[FEATURE]: It is possible to define descriptions for playbook histories.

[FEATURE]: As a test manager, I can use the new review filter option Ticket existing to check whether a defect ticket has been created for each FAILED review.

[FEATURE]: Teaser: With ecu.test 2025.3, it will be possible to calculate test case coverage not only for the current workspace, but also for all executions in test.guide.

[FEATURE]: When rerunning flow tasks in Workflow Automation, it is now possible to select the source for the flow bundle.

[FEATURE]: For flow triggers in Workflow Automation, it is now possible to subscribe to events of flow triggers.

[FEATURE]: The flow.kit bundle for the Workflow automation has the following improvements:

[CHANGED]: In Workflow Automation the payload size limitation for flow tasks has been removed. This allows larger payloads to be sent via the External event via REST-API as well. The limit is also removed for the Test case report export with flow trigger. To process large payloads, the corresponding flow bundles must be updated.

[CHANGED]: If monitoring plug-ins from the ResourceAdapter cannot query certain values (such as CPU load) from the operating system, these values are now displayed as “N/A” instead of “-1” in test.guide. Furthermore, the respective individual state is set to “not available (gray)” instead of “ok (green)”.

[CHANGED]: In the ResourceAdapter’s testguideupload Plug-in, the handling of authentication/authorization errors was improved. Previously, there were cases were these errors were incorrectly treated as IO errors.

[FEATURE]: Test executions can be blocked or allowed by bookings of test resources.

[FEATURE]: The Flow-Tasks of the Workflow automation can be queried via API.

[FEATURE]: In the Workflow Automation, the ID of the current flow task is available as the environment variable TT_FLOW_TASK_ID during the execution of the flow.kit bundle.

[FEATURE]: The flow.kit bundle for the Workflow automation has new blocks:

[CHANGED]: When you open the Q-Gate overview, the Q-Gate plans are now displayed directly instead of the Q-Gate filter. The filter can also be accessed via the button in the overview.

[CHANGED]: The Auto removal of deposited files previously only took place between 1 a.m. and 5 a.m. The end time restriction has now been removed, so that all files affected by the cleanup rule are always deleted.

[CHANGED]: For Q-Gate attributes and Q-Gate Plan attributes, the attribute value has been increased from 128 to 256 characters.

[CHANGED]: For flow triggers with a configured project filter, the name and category of the project filter are displayed directly on the flow trigger page. Additionally, the flow trigger is automatically deactivated at the next event if the configured project filter has been deleted.

[DEPRECATED]: The project view under Monitoring  Project view will no longer be supported and will be removed in release 1.200.0. If you urgently need this view, please contact support@tracetronic.com with your use case.

[FIXED]: When starting the ResourceAdapter in version 1.197.0, the tray icon might have incorrectly displayed offline even though the test.guide server was available. This issue has been fixed.

[FIXED]: When selecting a date in the date picker, an offset of -1 hour was always automatically applied in the English date format. This issue has been fixed.

[PREVIEW]: test.guide now offers the option of automating individual workflows

[PREVIEW]: The new Q-Gate type 'Workflow Q-Gate' allows integration with the new module Workflow Automation to automatically execute flow bundles as soon as the Q-Gate plan reaches a certain stage.

[PREVIEW]: To improve the visualization, you can now select whether the Q-gate Graph should be displayed from bottom to top, top to bottom, or left to right.

[PREVIEW]: To simplify the management of retention periods in the company in test.guide, a global remove rule for test resource appointments has been added.

[PREVIEW]: The search function in test.guide can now be reached from each page via the icon in the bottom right corner.

[FEATURE]: A Share button has been added to the Compare configuration history of a Test Resource Machine (TRM) page in Test Infrastructure Management.

[CHANGED]: User-defined names of playbook steps are used in ecu.test as test case names and thus also for reporting in test.guide.

[CHANGED]: Previously, if a coverage filter definition was assigned to a release, it could only be replaced by another one. Now it is also possible to remove the coverage filter definition from a release.

[CHANGED]: The release Q-gates have been expanded. Now you can specify that the gate only switches when the results NONE and PASSED have been checked.

[CHANGED]: It is now possible to use the web interface simultaneously in multiple projects, e.g. by using browser tabs.

[REMOVED]: The use of implicit ecu.test start and stop steps in the playbook has been removed.

[FIXED]: If the login fails when creating an Issue Tracker configuration, an error message is now displayed.

[FIXED]: The exported test results to IBM ETM now contain correct links to test.guide again.

[PREVIEW]: To simplify the management of retention periods in the company in test.guide, both automatic remove rules for the project and global remove rules for the company for the Q-Gates have been added.

[PREVIEW]: The Q-Gates REST API has been extended by the endpoints GET /plans/{planKey} and GET /plans/{planKey}/qgates/{qGateName} to enable direct access to the corresponding details.

[FEATURE]: Via the history view, the uploads of test case executions in test report management can now be sorted according to their size. This makes it possible to analyze which test plans are currently causing the most traffic, for example.

[FEATURE]: When setting up test.guide, a validation is performed directly during the configuration of the base URL to check whether test.guide can reach itself. This is important for test.guide to run properly.

[FEATURE]: A Share button has been added to the booking view for test resources in the test infrastructure management.

[FEATURE]: When creating defects via the ALM connection Octane, files can now also be attached.

[FEATURE]: Playbook parameters can be used in attributes and test script or test suite IDs of playbook filter steps.

[FEATURE]: Specific details of playbook steps are also displayed as icons in the playbook editor for a better overview.

[CHANGED]: In order to better display large Q-Gate graphs, they are now displayed horizontally instead of vertically.

[FIXED]: An error during the initial setup of test.guide under Windows via batch or service installation has been fixed so that the setup does not have to be executed twice.

[FIXED]: The statistics on test.guide functions that interacts with ALM systems (export results, create defect, get defect status, import ALM coverage and browse ALM coverage) are now accumulated correctly.

[SECURITY]-[CHANGED]: When exporting data to Excel, the cell contents are explicitly formatted as text cells. This ensures that the exported values are not automatically interpreted when you click in the cell.

[PREVIEW]: When a Q-Gate plan is started, the system checks within the next minute whether the stored Q-Gate releases have already been fulfilled.

[FEATURE]: The new REST API endpoints GET /filters and GET /filters/{filterId} in the Report Management API allow you to query all project filter information that are stored in the project.

[FEATURE]: As a project manager, I can create short-lived AuthKeys for technical users via the new REST API endpoint POST /users/{userId}/authkeys in the User Management API. This allows, for example, upload processes from external systems to be automated more securely.

[FEATURE]: With ecu.test 2025.2 and the ATX generator option includePkgSVNRevision enabled, the active branch is now also captured in the Branch attribute, even for Git-versioned workspaces.

[FEATURE]: The statistics on test.guide functions that interacts with ALM systems (export results, create defect, get defect status, import ALM coverage and browse ALM coverage) have been added to the usage statistics.

[FEATURE]: Remove rules for TR appointments can be created at the project level.

[FEATURE]: There is an automatic connection check for storages in the artifact management.

[FEATURE]: Playbook histories can be renamed.

[CHANGED]: Project permissions have been added to allow individual permissions for Q-Gate plans. All users with create release permissions will be migrated automatically and will get the new Q-Gate permissions.

[FIXED]: The Octane result export no longer aborts for all results, if a business rule defined in Octane fails for one result.

[ALPHA PREVIEW]: Q-Gates can now be shared in projects for other Q-Gate plans, projects, or even test.guide instances. This makes it easier to automate workflows between projects, departments, or companies.

[FEATURE]: The new endpoints POST /settings/filerepositories and POST /settings/filerepositories/{id}/activate in the Report Management REST API allow for the automated creation and activation of Depository type file repositories from artifact management.

[CHANGED]: The response of the endpoint GET /releases/{releaseId} of the Release API has been extended by the field path.

{
  "releaseId": 126,
  "testCaseTagSetId": 134,
  "name": "MyFirstSubRelease",
  ...
  "parentId": 125,
  "path": ["MyReleaseFolder", "MyFirstSubRelease"],
}

[DEPRECATED]: The functions integrated in test.guide for interaction with Jama, Polarion, and IBM ETM will be discontinued by the end of 2025. There will be successor solutions that will allow workflows to be adapted to individual project needs much more flexibly than before. If you have any questions, feel free to approach us: support@tracetronic.com.

[REMOVED]: The setting ecutest.automationBlockedBy=TEST_ACTIVITY of the ExecutionPlugin of the ResourceAdapter has been removed.

[FIXED]: When uploading results from test.guide to IBM ETM, it could happen that the specified iteration is not considered while searching or creating execution records. This could cause test.guide to create the results in ETM in an execution record with an incorrect iteration. This only affects test plans that have several iterations in their test schedule.

[SECURITY]: The SameSite attribute of test.guide’s session cookie is now set.

[SECURITY]: If needed, the login with user name and password, e.g. for the ServerAdmin, can be completely disabled when using OpenID Connect. For more info, check out the Operations Manual in chapter 10.1.6.

[PREVIEW]: In order to be able to automatically anonymize personal data, the global remove rules have been expanded.

[FEATURE]: With the help of the new "Release details" dashboard widget, releases from a selected release folder can be displayed directly on the start screen for all project members.

[FEATURE]: Test resources can be filtered by location.

[FEATURE]: The endpoint GET /api/v2/monitoring/healthstates of the Monitoring REST API has been extended to allow reversing the order of the response so that newer entries are returned first.

[FEATURE]: With the new REST API endpoints for project creation and project user management, the creation of new projects can be automated and simplified.

[DEPRECATED]: The endpoint GET /project/{projectId}/roles of the Platform API is deprecated and will be removed in a future release. The new User Management API endpoint GET /roles can be used instead of the deprecated endpoint.

[FIXED]: When bulk editing ResourceAdapter configurations via test.guide, general configuration parameters were deleted if they were hidden by the filter options. This behavior has been corrected.

ATTENTION!!!: When the new test.guide version is started up, the report database is automatically migrated to optimize release Q-gate calculations. This can take several hours depending on the data volume. It is recommended to back up the database before starting the migration. During the migration, access to test.guide is possible.

[PREVIEW]: As a user, I can use the new search function (under Info → Search) in test.guide to go directly to pages related to the search term in test.guide.

[PREVIEW]: To simplify the administration of retention periods in the company in test.guide, global removal rules have been extended to include the administration of release removal rules.

[FEATURE]: Execution tasks at a glance with a new dashboard widget.

[FEATURE]: Test resources can be filtered by name.

[FEATURE]: Deleting multiple test resources, including the underlying test resource machines and all associated data, is possible via a new delete button on the test resource overview page.

[FEATURE]: The usage statistics for test.guide functions, available under System configuration → System status, can now also be downloaded automatically via the REST-API under the endpoint /api/platform/usagemetrics. The new global permission METRICS_ACCESS has been added to control access to the metrics.

[FEATURE]: OpenText ALM Octane: Support for version 25.1.

[CHANGED]: For review templates, you can specify that when the review template is applied, only specific fields are overwritten and other fields remain as they are.

[CHANGED]: In export templates, the start time for the placeholder {testcase:executionTimestamp} is formatted according to the ISO-8601 standard as a date-time with an offset, e.g. ‘2011-12-03T10:15:30+01:00’.

[DEPRECATED]: The Jenkins dispatcher in the Execution Plug-in of the ResourceAdapter is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The value field on the SCM REST API in package and project attributes of the test case index is deprecated and will be removed in one of the next releases.

[SECURITY]: A cross-site scripting vulnerability in the tooltips that could be used to execute stored filter descriptions as HTML code, for example, has been fixed.

[PREVIEW]: The Q-Gate overview has been extended so that the time of the last action of a Q-Gate is displayed and the state log for each Q-Gate can be used to see in detail what happened when.

[PREVIEW]: In order to better manage artifacts and test reports that are subject to a certain information classification and retention period in the company, and to be able to manage them more centrally in test.guide, there are now global removal rules that can be set by server managers and automatically apply to all test.guide projects.

[FEATURE]: The release overview has been enhanced to allow you to lock and unlock multiple releases. You can now select and process multiple releases.

[FEATURE]: In the release overview, an autocomplete was added to the filter for the release name.

[FEATURE]: The new endpoint GET /testinfrastructure/testresourcemachines/byresourcelocationid of the Test Infrastructure REST-API can be used to query the TRM-ID of a Test Resource Machine (TRM) via the associated ResourceLocationId.

[CHANGED]: When creating release Q-gates, release folders can now also be specified. The release Q-gate is switched as soon as a release folder fulfills the conditions via its sub-releases.

[DEPRECATED]: From December 2025, the ecu.test ATX generator will officially only be supported by ecu.test version >= 2023.2. If it is not possible to update the project to at least this ecu.test version by December 2025, please contact support@tracetronic.com.

[FIXED]: The export of results to Codebeamer no longer times out for TestSets with many TestCases.

[PERFORMANCE]: 🚀 The ALM connection Octane has been optimized further so that defects can be created more quickly.

[PREVIEW]: With the help of the new option "Show TRF in browser", all details of the ecu.test TRF report can be displayed in HTML format directly in the browser from test.guide, which enables a faster review.

[PREVIEW]: If a Q-Gate plan has to be invalidated, for example because the incorrect release was configured, this Q-Gate plan can now be duplicated and the release simply changed.

[CHANGED]: The PDF template data source has been extended and now also contains the relative paths to the artifacts in the tables: TCE_ARTIFACTS, REVIEW_ATTACHMENTS and TESTSTEP_ARTIFACTS in the new PATH column, so that these paths (such as the paths for debug.log and error.log in the screenshot) can be used in the PDF for display.

[CHANGED]: The ReleaseStateChangedEvent has been expanded to include the name and path fields, so that the webhook contains information about the release track in which the change happened.

[CHANGED]: There is a permanent link to the lastest version of a playbook.

[DEPRECATED]: The setting ecutest.automationBlockedBy=TEST_ACTIVITY of the ExecutionPlugin of the ResourceAdapter is deprecated and will be removed in the release 1.194.0.

[DEPRECATED]: The use of implicit ecu.test start and stop steps in the playbook is deprecated and will be removed in the release 1.196.0.

[FIXED]: The ALM connections behave more stable when the template configuration page is opened.

[PREVIEW]: When creating a Q-Gate plan, a description and additional attributes can be specified. This data can also be extended and updated during a started Q-Gate plan, so that it is possible to enrich the Q-Gate plan with information at runtime.

[PREVIEW]: If it is determined after starting a Q-Gate plan that it cannot be executed, e.g. due to a incorrect configuration, it is now possible to invalidate such plans. Once a plan has been successfully completed, it is now also possible to finalize plans.

[FEATURE]: There are new dynamic playbook filter steps for packages and projects in the playbook.

[FEATURE]: The timestamp of the last update of an configuration item of a test resource machine is now displayed in the tooltip on the TRM detail page.

[FEATURE]: With the new Inactive since filter, server managers can now more easily identify and delete users who have not logged in for a long time.

[FEATURE]: For the OpenID Connect connection, test.guide always automatically requests the scopes openid, profile and email. Further scopes can now be requested via the configuration.

[DEPRECATED]: The endpoint DELETE api/v2/monitoring/resources of the Monitoring REST API is deprecated and will be removed in a future release. As an alternative, the endpoint DELETE api/testinfrastructure/testresourcemachines/{testResourceMachineId} can be used in the Test Infrastructure REST API.

[REMOVED]: In the Monitoring  IT view, the button for deleting the monitoring data of a test resource machine has been removed. Please use the delete button on the respective test resource detail page in the module Test infrastructure to delete a TRM including all associated data.

[REMOVED]: Due to a consistency adjustment, the following development preview endpoints of the Test Infrastructure REST API have been removed. Please use the new endpoints described in Release 1.184.0.

[FIXED]: When date fields in Jira tickets are filled in, the time zone of the user is considered.

[FIXED]: There is now a unique order for querying releases via the REST API.

[FIXED]: In the issue tracker Octane, its now possible again to write HTML into the description field when creating new tickets.

[FIXED]: The Browser based login process of test.guide in ALM systems (especially Octane and Codebeamer) is successfully completed.

[PERFORMANCE]: 🚀 The attribute and constants filterings in the test case coverage have been speeded up.

[PERFORMANCE]: 🚀 The ALM connection Octane has been optimized so that defects can be created more quickly.

[FEATURE]: A new info page with information on analyzing ASTRACE files with trace.xplorer basic has been added.

[FEATURE]: For a better overview, you can switch between different views in the booking view under test infrastructure.

[FEATURE]: The ALM connections RQM and Codebeamer now behave more stable when simultaneously exporting results in several jobs.

[FEATURE]: Workspace dependencies of playbooks that reside in a Git repository may be checked out sparsely.

[FEATURE]: Playbook steps can be filtered by testscript ID and testsuite ID when being added to a playbook via the playbook editor.

[FEATURE]: The new view for playbook runs contains one link each to a filter with the generated execution tasks.

[FEATURE]: LDAP Authentication: Insecure SSL connections can now optionally be accepted for evaluation and testing purposes.

[CHANGED]: To prevent inperformant queries in the Test Infrastructure REST-API, the endpoint POST api/testinfrastructure/appointments/filter has been extended by a pagination.

[FIXED]: The ALM connection Codebeamer behaves more stable when timeouts occur from Codebeamer.

[FIXED]: The ALM connections behave more stable when the template configuration page is opened.

[FIXED]: An issue with uploading files that were larger than the upload limit has been resolved; these files were not cleared from the server.

[FIXED]: The label uniqueness check in coverage filter definitions, added with test.guide version 1.187.0, has been removed because it could break test automation in certain setups. This check will be re-introduced in a future release, but we will prepare the introduction so that existing projects are not affected.

[FIXED]: A problem with filtering when adding new packages or projects in the playbook editor has been fixed.

[FEATURE]: Test resources can be deleted together with all associated test resource machines and all data via GUI.

[FEATURE]: There is a new overview for all playbook runs of a playbook history.

[FEATURE]: Test execution tasks can be filtered according to their aggregated results in the execution task overview.

[FEATURE]: ecu.test workspaces can be indexed via REST API and the indexed contents can be queried.

[FEATURE]: With the new audit log, both project managers in their project and server managers on the instance can check when and how certain settings were changed for a period of two years.

[FEATURE]: In applicationsettings.yml, the operations team can use the new nightlyReportRemovalTimespan parameter to set how long per day the report removal rules should run.

[FEATURE]: To be able to check which PDF template was used to create a specific test summary report, each PDF created is now provided with a hash that can be compared with the PDF template hash in test.guide.

[FEATURE]: Codebeamer: Insecure SSL connections can now be optionally accepted for evaluation and test purposes.

[FEATURE]: ALM connection Polarion supports authentication via Personal Access Token.

[FEATURE]: ALM connection Octane supports text with multiple lines in the field description when creating defects.

[FEATURE]: The placeholder {testcase:executionTimestamp} has been added to the export templates, which makes it possible to write the start time to a result.

[CHANGED]: The ATX generator setting archiveMiscFiles no longer considers subproject directories if these have been executed as separate subprojects, in order to avoid duplicate data collection.

[CHANGED]: The settings for the retention period for the monitoring data have been moved to the new settings page System configuration  Test infrastructure.

[CHANGED]: Previously, it was possible to create coverage filter definitions where the same labels could be used within one layer. Now it is checked that these are unique for the display.

[SECURITY]: Update of the Apache Wicket library to the current version to solve the Vulnerability CVE-2024-53299.

[PERFORMANCE]: 🚀 The result filter has been optimized for a more performant display of the results.

[PREVIEW]: The new Approval-Q-gate is available. It is used to ensure that those responsible must explicitly approve further process steps before actions are triggered. This means that even STOPPED states are only propagated after approval.

[FEATURE]: The moving of appointments of a test resource by drag and drop is now also possible in the booking view.

[FEATURE]: A server admin can now easily change the retention period of the data in the monitoring database.

[FEATURE]: Polarion: Support for version 22 R1.

[FEATURE]: Project filter subscriptions can be edited – for example, the execution interval can be changed.

[CHANGED]: When creating e-mail notifications, it is now possible to use simple HTML tags to format the e-mail.

[CHANGED]: ReleaseStateChangedEvent has been extended by the field releaseDType so that the webhook contains information about which type of release (Release or Release folder) has been changed.

[CHANGED]: In the grouping widgets in the dashboard, you can set whether or not the percentage distribution of the results should be displayed.

[CHANGED]: test.guide support for synchronizing system groups via OpenId Connect has been extended so that the system groups can be determined not only from the AccessToken claim, but also from the claim of the UserInfo response.

[CHANGED]: For consistency reasons, all occurrences of "Test bench" have been replaced by "Test resource" in the activity view (Test infrastructure → Activity).

[FIXED]: In the ATX generator setting archiveFilesPerPackage , superfluous semicolons, e.g. at the very end, until now caused all files in the package directory to be included. This is no longer the case. Superfluous semicolons are ignored now.

[FIXED]: The setting ecutest.automationBlockedBy=ACTIVITY of the ExecutionPlugin of the ResourceAdapter did not work correctly. This bug has now been fixed.

[FIXED]: The page for editing the template for creating defects in ALM Octane could no longer be opened. This bug has now been fixed.

[FEATURE]: Appointments in the calendar of a test resource can be moved by drag and drop.

[FEATURE]: New test resources can now also be created via the test.guide UI.

[FEATURE]: The artifact overview on the test plan details page has been expanded so that the uploaded artifacts are also displayed in a tree view for each test case. In addition, buttons are available to open the artifacts directly in the browser.

[FEATURE]: To get from a release Q-gate to the underlying release details, a direct link is available via the release Q-gate flag.

[FEATURE]: The supported choice of ecu.test steps in the playbook editor also considers the defined workspace dependencies.

[FEATURE]: In the Playbook Editor, names for playbook steps can be specified, which are displayed in the Log view on the execution tasks details page.

[FEATURE]: It is possible to jump directly from attributes and parameters on execution tasks to the filtered execution tasks.

[FEATURE]: The details of a test.guide task can now be viewed on the new details page.

[FEATURE]: The migration of storages from a depository can be aborted on the depository details page.

[FEATURE]: System settings → System status can be used to view Usage statistics for the test.guide features. This is particularly useful for operation in order to analyze which features are used and to size the system accordingly for the respective use.

[CHANGED]: The grouping widgets on the dashboard show the percentage distribution of the results.

[FIXED]: When using the ecu.test (≥ 2025.1) upload dialog to transfer reports to test.guide, it is now possible again to set additional constants and attributes in the dialog, even if the ATX generator parameter useSettingsFromServer is used.

[FIXED]: Fixed a bug in the new Test Infrastructure REST API endpoints in the customAttributeEntries section that caused the endpoints to always return a 404 response code.

[FEATURE]: Appointments for test resources can be created directly in the booking view by clicking on a free time slot.

[FEATURE]: The display of the calendar on the test resource details page has been improved to provide a quicker overview of the appointments.

[FEATURE]: Test Resource Machines can now also be deleted via the test.guide UI.

[FEATURE]: When uploading ecu.test reports via the ResourceAdapter, it is now possible to upload larger reports in chunks. This may be necessary, for example, if gateways in front of test.guide imposed size limits per upload.

[FEATURE]: When adding package or project steps to the playbook, their attributes from the Git repository can be displayed and filtered.

[FEATURE]: When specifying constant values or package parameter values in an ecu.test step in the playbook (package or project step), you can prevent a used variable from being escaped as a Python expression during replacement. To do this, use the notation ${raw:VAR} when using a variable with the label VAR.

[FEATURE]: Depending on the test result evaluations, the upload of package and project step results to playbooks can be suppressed, so that, for example, only FAILED and ERROR test results are uploaded for later analysis.

[FEATURE]: The overview of the test execution tasks shows the status of the tasks as well as the aggregated evaluation of the test results.

[FEATURE]: Under Project Settings → Filter Settings, you can now configure the initial filter period which is automatically used when the report filter page is opened.

[FEATURE]: Artifact management now includes new filter options for cleanup rules. In addition to artifact age, cleanup rules can now be created based on file names, file extensions, file sizes, artifact shares and artifact attributes.

[CHANGED]: The creation of Release Q-gates has been simplified so that a threshold for the successful results can now be specified without a scope.

[CHANGED]: In the log file api-access.csv, the calls to the REST API are logged for analysis in the event of performance problems. This log now contains the IP address of the client and the host name of the server in clear text. The data is stored for a maximum of 14 days.

[CHANGED]: For consistency reasons, there are changes to some development preview endpoints of the Test Infrastructure REST API.

[CHANGED]: On the comparison page for the test resource configurations, the link behind the name of the test resource now leads to the test resource detail page and no longer to the first test resource machine detail page.

[DEPRECATED]: Due to a consistency adjustment, the following development preview endpoints of the Test Infrastructure REST API are deprecated and will be removed in a future release. Please use the new endpoints described in Release 1.184.0.

[DEPRECATED]: The ecu.test ATX Generator now uses the official asynchronous report upload API /api/report/reports, which replaces the following old APIs.

[FIXED]: Fixed a situation where an endless loop could prevent report upload if one configured a Map attribute upload rule with equal source and target attributes.

[PREVIEW]: The release Q-gates have been extended so that they can also be switched if a relevant re-evaluation has been performed for all the defined results. This means that processes following defect evaluation can be completed more effectively in an automated process.

[PREVIEW]: The calendar feature for booking test resources can now be used directly without setting the FeatureFlag.

[FEATURE]: The calendars of several test resources can be compared in the new booking view to quickly find a time slot at a suitable test resource.

[FEATURE]: New appointments can be created directly in calendars of test resources by clicking into the calendar.

[FEATURE]: In the settings of the SCM tool, you can choose whether to clone a Git repository either shallowly or now also with its full history.

[FEATURE]: In execution tasks and playbooks, specific SCM tool settings can be overridden.

[FEATURE]: In the overview of the execution tasks, the execution tasks can be filtered based on their minimum and maximum priority.

[FEATURE]: As of ecu.test 2024.3 the new PRF report format is activated by default, which makes it possible to obtain individual TRFs per package execution. test.guide now also supports opening the format directly from the browser. This means that only the required package TRF reports can be analyzed more quickly without always having to download a large project TRF, as was previously the case.

[FEATURE]: Artifacts can be filtered by their minimum and maximum file size in the artifact overview.

[FEATURE]: When creating new Jira tickets in the review process, the input of Jira assets is better supported by auto-completion.

[FEATURE]: Test case details have been enhanced to show test case execution and test plan report IDs, and linked to the test plan overview page for faster access.

[FEATURE]: The /testCaseExecutions/exportTms/{tmsTaskId}/download endpoint has been added to the Report Management API, allowing access to the resulting TMS export report in format of a CSV file.

[CHANGED]: The /testCaseExecutions/exportTms/{tmsTaskId}/status endpoint of the Report Management API changed its return type to allow accessing detailed status information.

[CHANGED]: The link on the upload history page has been changed so that the test plan link now goes directly to the test plan overview page and no longer to the result filter, which can still be found via the new link over the report ID.

[CHANGED]: When uploading reports via the ResourceAdapter by using the test.guide Report Upload Plug-in, the behavior has been changed so that if the test.guide server is unavailable for 24 hours, these reports are not initially moved to the Faulty folder, instead the upload is continued after the connection is re-established.

[CHANGED]: The activity view of the test resources has been moved from the "Monitoring" module to the "Test infrastructure" module.

[REMOVED]: Deactivation of the Test42 connection

[REMOVED]: Deactivation of the Rally connection

[FIXED]: test.guide versions 1.180, 1.181 and 1.182 contain an bug related to the result export to the ALM systems Octane, Codebeamer or ETM.

[FIXED]: The export of multiple results to Octane will continue, even if Octane does not accept individual result uploads due to unauthorized defect linking.

[PREVIEW]: The test execution distribution can be configured so that high-priority tasks can abort low-priority tasks, so that, for example, low-priority stress tests can be automatically replaced by high-priority tests.

[PREVIEW]: As a user, I can now select in the grouping filter to also display the test case executions in the grouping that are in the filter range but cannot be assigned to a group ([N/A]).

[FEATURE]: If you want to analyze the videos, images or log files uploaded during test case execution, they no longer have to be explicitly downloaded, instead they can be directly displayed in the browser (if the browser supports the format).

[FEATURE]: The view of the calendar of a test resource can be changed between day, week and month.

[FEATURE]: To outsource the ecu.test report uploads to test.guide via the ResourceAdapter so that ecu.test can continue testing directly, there is the option uploadThroughResourceAapter. Now there is also the option uploadThroughResourceAapterFallback, which tries to upload the report directly if the ResourceAdapter is not available.

[FEATURE]: The validation of user permissions via the REST API /api/userManagement/users has been extended for Server Manager so that the new fields individualProjectRoles and systemGroupProjectRoles now show which roles have been assigned to users.

{
  "projectId": 1,
  "activationStatus": "ACTIVATED",
  "individualPermissions": [
    "PROJECT_USER_MANAGEMENT",
    "PROJECT_MANAGEMENT"
  ],
  "projectRoles": [
    51,
    2
  ],
  "individualProjectRoles": [
    51,
    2
  ],
  "systemGroupProjectRoles": [
    51
  ],
  "effectivePermissions": [
    "PROJECT_USER_MANAGEMENT",
    "PROJECT_MANAGEMENT",
    "TESTCASE_UPLOADER",
    "UPLOAD_CLEANER"
  ]
}

[FEATURE]: To improve collaboration on a test resource calendar, it is displayed who created and last changed an appointment, along with the associated times.

[FEATURE]: New TestResourceMachines (TRMs) under a test resource can now also be created via the graphical user interface.

[FEATURE]: OpenText ALM Octane: Support for version 24.3.

[FIXED]: The CPU Load Per Process Plug-in and the RAM Usage Per Process Plug-in returned values for incompletely specified process names if a process was found that partially matched the specified name (e.g. the process “SearchIndexer” was also considered when the process name “arc” was specified). This has been corrected so that the complete process name must always match.

[PREVIEW]: Release and manual quality gates can now have predecessors and take into consideration the states of predecessors, so that processes and their dependencies can be directly modeled. In this context, there is also the new state “IN PROGRESS” for Q-gates, which indicates that the result of this Q-gate is still pending before the following Q-gate(s) can be switched.

[PREVIEW]: In order to maintain a better overview in the calendar of a test resource, appointments can be categorized.

[FEATURE]: There is a new distribution strategy for playbooks: "Clone on all specified test resources", which makes it possible to explicitly run playbooks on multiple specified test resources.

[FEATURE]: Playbooks can be filtered via the new test.guide REST-API POST endpoint /api/v2/execution/playbook/filter.

[CHANGED] The settings for the activity types are now located under Test infrastructure → Settings and no longer under Project Settings → ResourceAdapters.

[CHANGED]: The ResourceAdapter Jenkins-Agent-Plugin uses other arguments to start Jenkins agents.

[CHANGED]: The log file api-access.csv also contains the processing time of the request for performance analysis.

[FIXED]: The upload rule Map constant and replace values using a regex caused an error during application and the upload was rejected with HTTP status 500. This problem has been fixed.

[FIXED]: In the following development preview endpoints of the Test Infrastructure REST API, the return codes have been corrected, which were sometimes incorrect if an incorrect UUID or request body was provided. This has been fixed.

[FEATURE]: The new ATX option skipCaptureReviews allows you to disable the capturing of ecu.test comments and re-evaluations as test.guide reviews.

[FEATURE]: The keywords now and today can now also be used when sharing coverage filters via URL, e.g. from=now-3d&to=today+07:00.

[CHANGED]: The Excel export has been extended to include the column effective verdict, resulting in column shifts!

[DEPRECATED]: The TestResourceMachine (TRM) detail pages moved, resulting in different URLs. Old URLs (containing monitoring) are still supported for now, but will be removed in a future release. Please update existing bookmarks, if necessary.

[DEPRECATED]: The setting ecutest.automationBlockedBy=TEST_ACTIVITY of the ExecutionPlugin of the ResourceAdapter is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The use of implicit ecu.test start and stop steps in the playbook is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The endpoint /api/download-file/ResourceAdapter of the Monitoring API is deprecated and will be removed in a future release. The new Test Infrastructure REST API endpoint GET /api/testinfrastructure/resourceadapter/download can be used instead of the deprecated endpoint.

[DEPRECATED]: Direct linking to TestResourceMachine detail pages (also known as testbench detail pages) via the ResourceLocationId elements in the URL will be removed in a future release. These pages can now be linked via the TrmId. Please adjust any bookmarks accordingly. Suitable parameters for the links can be created using the share function on the respective page.

[REMOVED]: As announced in Release 1.119.0, the value field when querying constant and attribute values via /testCaseExecutions/{tceId} has been removed. Use the values field instead.

[PREVIEW]: To get an easy introduction to the coverage topic, the grouping filter can be saved directly as coverage.

[FEATURE]: On the test resource details page, you can now use the info buttons at the top right of the page and in the TRM table to display the IDs of the respective TR and its TRMs.

[FEATURE]: When creating a new release remove rule, it is now also possible to create remove rules based on release attributes.

[FEATURE]: Rerun or abort multiple execution tasks in a single step.

[FEATURE]: A setting in the command playbook step can be used to control via exit codes how playbook execution should continue after the step.

[FEATURE]: The new REST API endpoint GET /api/report/reports/history in the Report Management API allows you to list all uploads using an upload date filter – similar to the history page in test.guide.

[FEATURE]: The new REST-API endpoint POST /api/testinfrastructure/testresources/filter in the Test Infrastructure API enables the filtering of test resources based on configurations and attributes of the associated TestResourceMachines analogous to the GUI under Test infrastructure → Test resources.

[CHANGED]: The REST-API endpoint GET /api/report/reports/{reportId} has been extended so that the TestCaseExecutionId (tceId) is now directly included and does not have to be parsed via the URL.

[CHANGED]: The expand option in the coverage filter has been replaced by a result filter. This makes it possible to display the subtrees that only contain FAILEDs or are not covered at all more quickly in large coverages, for example.

[DEPRECATED]: The setting ecutest.automationBlockedBy=TEST_ACTIVITY of the ExecutionPlugin of the ResourceAdapter is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The use of implicit ecu.test start and stop steps in the playbook is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The endpoint /api/download-file/ResourceAdapter of the Monitoring API is deprecated and will be removed in a future release. The new Test Infrastructure REST API endpoint GET /api/testinfrastructure/resourceadapter/download can be used instead of the deprecated endpoint.

[DEPRECATED]: Direct linking to TestResourceMachine detail pages (also known as testbench detail pages) via the ResourceLocationId elements in the URL will be removed in a future release. These pages can now be linked via the TrmId. Please adjust any bookmarks accordingly. Suitable parameters for the links can be created using the share function on the respective page.

[DEPRECATED]: As announced in Release 1.119.0, the value field when querying constant and attribute values via /testCaseExecutions/{tceId} will be removed in place of the new values field in Release 1.180.0.

[SECURITY]: When using the REST API, the authentication key can also be passed as a header instead of as a query parameter. This new header is called TestGuide-AuthKey. If it is set, the query parameter authKey is ignored. It is recommended that all API calls be updated to use the new header.

ATTENTION!!!: When this new test.guide version is launched, it will automatically migrate the report database to optimize performance. It is recommended to back up the database before starting the migration. The migration step can take up to one hour, depending on the amount of data. During this time, NO access to test.guide is possible.

[FEATURE]: In the Released details, the execution tasks executed for this release can now be opened directly via the button "Jump to execution tasks " in the task overview.

[FEATURE]: Playbooks can be filtered by label on the Playbook overview page. This is possible via the Advanced filters option.

[FEATURE]: The automatic report upload by the ResourceAdapter can be deactivated for playbook package and project steps.

[FEATURE]: It is now possible to use the proxy configured for test.guide to connect test.guide to IBM ETM.

[CHANGED]: If you click on the name of a test resource in the test resource list, you will now be taken directly to the associated test resource detail page and no longer to the detail page of the first test resource machine.

[CHANGED]: When creating and editing appointments of test resources, when changing the start time, the end time of the appointment is automatically adjusted so that the duration remains constant.

[DEPRECATED]: The setting ecutest.automationBlockedBy=TEST_ACTIVITY of the ExecutionPlugin of the ResourceAdapter is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The use of implicit ecu.test start and stop steps in the playbook is deprecated and will be removed in one of the next releases.

[DEPRECATED]: The endpoint /api/download-file/ResourceAdapter of the Monitoring API is deprecated and will be removed in a future release. The new Test Infrastructure REST API endpoint GET /api/testinfrastructure/resourceadapter/download can be used instead of the deprecated endpoint.

[DEPRECATED]: Direct linking to TestResourceMachine detail pages (also known as testbench detail pages) via the ResourceLocationId elements in the URL will be removed in a future release. These pages can now be linked via the TrmId. Please adjust any bookmarks accordingly. Suitable parameters for the links can be created using the share function on the respective page.

[DEPRECATED]: As announced in Release 1.119.0, the value field when querying constant and attribute values via /testCaseExecutions/{tceId} will be removed in place of the new values field in Release 1.180.0.

[REMOVED]: The old REST-API version 2 for SCM configurations under …​/api/v2/scm has been removed in place of the new …​/api/v3/scm.

[REMOVED]: In Reporting (including the associated REST API), the information about which user uploaded the PDF template has been removed to simplify compliance with the GDPR.

[SECURITY]: By default, you are now automatically logged out after 60 minutes of inactivity.