2024.10.0

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:

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.

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

Visit Heatmap display to explore the enhancements.

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.

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

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

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.

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.

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.

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.

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.

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:

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

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.

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

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.

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:

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

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.