Septiembre de 2026

September 2026 release notes for Test Manager in Automation Cloud Public Sector and Test Cloud Public Sector.

September 4, 2026

Clipboard data available as an MCP tool argument on test steps

The Test Manager Model Context Protocol (MCP) tools for adding and updating test steps (Bulk add test steps, Bulk update test steps) accept an optional Clipboard data argument, matching the field already available in the Test Manager UI.

This lets you set or update a step's Clipboard data programmatically — for example, when generating test cases with variable input through Autopilot Chat or Delegate — without falling back to UI automation. Existing callers that omit the argument are unaffected.

For more information, refer to the Manual test cases section of the documentation.

Requirements page redesign

The requirement details page is redesigned with the following changes:

• The toolbar exposes Evaluate Requirement and Assign test case (grouping Create new test case, Assign existing test case, Generate test cases, and Find obsolete tests) as direct actions, alongside Optimize coverage, which is kept as a duplicate entry point with no retirement date currently set.
• The description field uses a rich-text editor instead of Markdown syntax, and shows No description added when empty.
• Labels, custom fields, attachments, and audit metadata (Created by / Updated by) are reorganized into the requirement overview.

The overview uses a responsive layout that stacks secondary content below the main area at narrower widths.

Assigned test cases gain Grid view and List view options. List view uses virtual scrolling, loading test cases in batches of 500, and shows compact last-result indicators (Passed, Failed, No result). You can filter assigned test cases, including by last result, and select one or more to Unassign or Delete them in bulk. Test cases still cannot be executed directly from a requirement.

For more information, refer to the Requirements section of the documentation.

Easier to read and copy full log messages in test executions

Long or truncated robot log messages in the Logs tab of a test execution were hard to read in full, and could not be copied.

The Logs tab has an Info column: select the info icon on any log row to open its full message in a pop-up, with a Copy message button.

The Logs tab also gains message search and sorting on the Level column, plus a Level filter to show only the log levels you care about:

• Trace (All)
• Info + Warn + Error + Fatal
• Warn + Error + Fatal
• Error + Fatal
• Fatal

For more information, refer to the Analyzing test results section of the documentation.

Corrección de errores

• Fixed ObjectLabels bulk add/remove requests with an invalid or unsupported objectType (combined with an empty or over-the-limit list of object IDs) returning a 500 error instead of 400 Bad Request with a validation message. (TMHUB-32720)
• Fixed ObjectFilters create/assign requests with a malformed filterExpression (wrong JSON type, or null) returning a 500 error instead of 400 Bad Request with a validation message. (TMHUB-32720)
• Fixed malformed request bodies with incorrectly typed fields (for example, a search value sent as an array instead of a string) returning a 500 error instead of 400 Bad Request, across Test Manager API endpoints. (TMHUB-32720)