March 2026

March 10, 2026

What's new

Folders via custom structured views

To keep testing portfolios of any size appear well organized, flat lists of your assets (requirements, test cases, test sets) can now be visualized in meaningful structures, based on grouping and filtering criteria. This allows to generate focused visualizations based on different areas of interest. Views can be saved and shared to swiftly switch between them.

We introduced the Group by capability based on custom field definitions of the type Label. Common use cases are grouping tests by test cycles, teams, or components.

Important: The Group by capability (which is part of custom structured views) is available in Test Manager only when delivered through Test Cloud.

We re-designed the UI for filtering criteria (based on feedback), without any functional change.

We revamped the UI for managing views (based on feedback). You can easily switch between your saved views, create new ones, and share your views with your colleagues.

For more information about custom structured views, refer to the following sections: Requirements, Test Cases, Test Sets

.

Accessibility Testing

Accessibility Testing automates accessibility compliance testing within the development pipeline, reducing manual effort and improving testing efficiency. Accessibility Testing enables teams to continuously test and validate accessibility conformance of webpages throughout development and release cycles — ensuring digital inclusion, reducing risk, and enabling faster remediation of issues.

Important: Accessibility Testing is available in Test Manager when delivered with Test Cloud.

Accessibility Testing requires the usage of an Accessibility Check activity, available as part of the UI Automation Activities 26.10.1-preview package or higher.

For more information about Accessibility Testing in Test Manager, refer to Accessibility Testing for Test Cloud.

For more information about the Accessibility Check activity, refer to Accessibility Check.

Test Case Log support in Autopilot Search

Users can directly search and access test case logs without navigating into individual test executions. The exposure of Test Case logs in Autopilot Search reduces the time spent drilling down into executions and makes log discovery faster and more intuitive.

For more information about Autopilot Search features, refer to the Autopilot Search section of the documentation.

Support for GPT 5.1 model

The GPT 5.1 model is supported and enabled for Autopilot for Testers features.

Deprecation of legacy execution

The Allow legacy execution context setting will soon be deprecated. As a result, specifying execution folders at project level or at test-set level will become mandatory for automated test execution.

To learn more about how you can set up execution folders, refer to Configuring test sets for specific execution folders and robots.

Email summary after test execution

After a test execution finishes, users receive a notification email consisting of:

• A summary of test cases by status (Passed, Failed, none)
• A list of test case keys, names and results
• A link to test case logs, by selecting the test case key

Bug fixes

Fixed an issue where the test execution name did not reflect the user’s time zone.