2024.10.0

Release date: November 11, 2024

What's new

Orchestrator folder and package version selection for executing test sets

We're excited to announce an update that improves the management and execution of specific System Under Test (SUT) versions, especially for patch testing. You now have the ability to select test cases to be executed from a particular Orchestrator package version when running a test set.

Key updates include the following:

Default folder association: Each Test Manager project can now be linked to an Orchestrator folder as the default folder. This is the folder context for any automated execution. This helps when a certain folder is used most of the time for a particular Test Manager project. For more flexibility, you can override this default folder on each test set.
Package and version selection: On a test set, you can now select which packages and versions are used for execution. This allows testing of different versions of a system under test since it allows to select compatible automation versions for each run.
Autoselecting packages: The Autoselect option automatically selects all packages to be added to the test set, chooses the latest version of each package, and skips any test cases that aren't available in the selected package or the chosen version. Autoselection happens based on the test cases assigned to the test set.
Execution indication: Each test case from the test set now displays whether it can be executed automatically based on the currently selected folder/package/version combination.

Tenants created before this update have the Allow legacy execution context setting enabled, allowing you to execute tests with or without execution folder contexts. Tenants created after this update have this setting disabled, allowing you to execute sets, only with execution folder contexts configured.

Visit Tenant level settings, Automation project configuration and Configuring test sets for specific execution folders for more information.

Additional Heatmap filters

You can now filter your Heatmap to see the transactions for which no test cases were assigned.

Visit Heatmap display to explore the enhancements.

SAP FIORI landing pages in Heatmap

You can now switch the Heatmap to display the transactions from the SAP FIORI landing pages of your SAP system! This feature offers flexibility in testing your SAP system, and the possibility to customize your preferred mode of interacting with your SAP testing portfolio.

Visit Changing the heatmap settings to learn how to work with the enhanced heatmap settings.

Email notifications for test executions and project import events

We enhanced the email notification system for testing events! You can now enable email notifications for the following events:

TestManager TestExecutions
ProjectMigrations

Visit Events to learn how to personalize your notification subscriptions, and Managing notifications to learn how to customize your organization's notification subscriptions.

Precondition for manual test cases

To define preconditions for manual tests, you can now add preparatory steps for your manual test cases. Preconditions help by stating the actions that must occur before the actual testing starts. Visit Adding manual steps to a test case to learn how you can add preconditions to your manual test cases.

New version of the project migration schema

The precondition for manual test cases feature also comes with a new version of the schema that you use for importing or exporting your testing projects. To accommodate the new functionality of a manual test case, the 1.0.1 version of the schema now supports the Precondition property in the JSON files of your test cases, so you can import or export your preconditions. Visit Import project to learn how to retrieve the schema for your testing project.

Mixed execution

With mixed executions, you can now run both manual and automated test cases simultaneously, to make your testing processes more efficient. Mixed execution offers increased flexibility by allowing you to re-execute test cases, no matter their nature of execution.

Visit Executing mixed tests to read about working with mixed executions.

New testing artifacts to export or import within your projects

The TMH file format for exporting and importing projects now supports new object types: test results and defect links. This allows you to create comprehensive backups for your testing projects. Note that robot logs are not included in the TMH file format, despite the addition of test results and defect links.

Visit Export project to learn about the test objects included in the TMH file.

Label custom field definitions

You can now use labels as a data type on custom fields. This feature allows you to select from a pre-defined list of values, enhancing the structure of data in your repository.

Custom fields now include a Data type attribute. The attribute is Text by default, but you can change it to Label. Additionally, you can assign a custom field definition to various object types such as: Requirement, Test Case, and Test Set.

With this update, the CSV file that you can export for your requirements and test cases, have new columns for custom labels.

Visit Custom fields to learn how to create label custom fields.

Enhanced filtering and customizable views

Filters

You can now apply filters when you view test objects within your project, using the Filters type. The Filters type offers you predefined filters (which correspond to information columns in a test object view, such as Name, Description, or Last Modified), and custom filters. Custom filters represent the custom labels that you define in the Custom field definitions section of your project.

Views

You can also save these custom and predefined filters that you apply, as views. Views can either be personal or be available to all other project users.

The filters, and the view to which you save them, are persistent within the project, either personal, or public to all project users.

Visit the following resources to learn how to apply filters and manage views for the supported test objects:

Configuring display of test objects with columns

Every project section that shows objects, including Requirements, Test Cases, and Test Sets, now has a Columns type. The Columns type contains properties native to a test object (such as Name, Description, and other), as well as custom field definitions and custom labels. You can use this type to customize the display of your test objects.

Enforce execution order

The new Enforce Execution Order feature allows you to set a default order for test set execution, streamlining the process. The feature enables you to enforce a specific execution order for statically assigned test cases, with dynamically assigned ones following in a random order only after the completion of static cases.

Key updates include:

An Enforce execution order toggle in the test set Configuration and test execution Settings.
The ability to reorder static assignments of test cases when Enforce execution order is enabled.

Visit Enforcing an execution order to learn how to enforce an execution order for test cases within a test set or test execution.

Test execution labels

Test executions now inherit labels from their corresponding test sets. You can modify these labels and filter test executions based on them. Visit Test results to learn more about working with test executions.

Export of test objects

You can now selectively export test objects, and their dependent objects, from a project. This feature offers you the flexibility to import them into a different project, facilitating the movement of specific sections of a project to another. This is especially useful if you want to split a test project or move portions of it somewhere else. You can selectively export the following objects:

Requirements
Test cases
Test sets

For more information about exporting parts of your testing projects, visit the following pages:

Default reporting timezone date

This update brings the Default reporting date time zone feature, designed to enhance the consistency of test execution representation on the dashboard across various time zones.

Visit General project settings and learn how to configure a default timezone for your testing projects dashboard.

SAP Change Impact Analysis

This solution allows you to analyze the impact of SAP software changes, such as modifications to ABAP code, customizations, application of SAP Notes, and Support Packages. Leverage the insights from this analysis to optimize your testing process, reduce testing efforts, understand the impact on business processes, and efficiently focus on necessary testing areas.

To use SAP Change Impact Analysis, you need to go through three phases:

Learning - collecting information about transactions and their dependencies using activities in Studio, with the help of the SAP Testing Project template.
Analysis - analysing the changes with the help of SAP Change Impact Analysis heatmap in Test Manager. The results show the impacted test cases (Fits) and highlight SAP transactions and programs affected by changes without assigned test cases (Gaps).
Action - creating test cases for new discovered Gaps, that are not covered by tests in your regression portfolio, and assigning the impacted test cases to the test sets.

Visit Change Impact Analysis to learn how to efficiently focus your SAP testing efforts.

Execution type displaying for test results

Expand your knowledge of your testing portfolio by checking the execution types for each test case that you run. Now you can see, in the Execution tab, the type of execution that ran for each test case log.

Improvements

General improvements

The combined Create/Edit permission has been split, providing more specific permissions: Create and Edit.
The Read only role has been updated and is now referred to as Viewer.
Updated the display of project tiles for an enhanced user experience.

Custom field definitions improvements

Custom fields now support multiple object types at the same time. For example, a custom field that you assign to requirements, you can now assign it to test cases and test sets, as well.
You can now delete multiple custom fields at once, instead of individually.
You can now filter custom fields by Data Type, and Object Type, to help you structure your test data repository.

Custom field definitions changes

You cannot edit the name of a custom field definition anymore.

Heatmap improvements

Error messages related to your SAP system connection now show more details, to ease your debugging process.
To allow test cases to link to the executed transactions, when using the Heatmap, you can now set the Enable SAP monitoring setting to True for your Test Automation projects. Visit Heatmap to check how you can use the updated settings.

Upcoming deprecations

The native connectors used for creating ALM tool integrations, except SAP Solution Manager, will be deprecated. The deprecation schedule has been set as follows:

Deprecation of all native connectors starts on September 30, 2024.
Specifically, the deprecation of the qTest connector starts on April 30, 2025.

The long-term alternative to native connectors is UiPath® Test Manager Connect.

Visit the Upcoming deprecations for Test Manager to learn about the timeline and how the deprecation impacts you.

Test Suite Release Notes

Was this page helpful?