Panaya

Panaya Test Automation 26.11.103: API control and sharper automation reviews

Panaya Test Automation 26.11.103 adds APIs for managing parameters, datasets, and planned runs at scale. It also gives teams more control over test evidence, failure alerts, dynamic automation scripts, and AI-assisted comparison and self-healing behavior.

By Chris CarpenterTest AutomationSAP TestingQA
Panaya_Logo.svgPanaya Test Automation Transparent Logo.png
Panaya Test Automation 26.11.103: API control and sharper automation reviews cover graphic
Back to Panaya release updates
Release facts
VendorPanaya
ProductPanaya Test Automation
Version26.11.103
Published by MeritoNovember 1, 2026
Vendor release notesPanaya Test Automation 26.11.103 release notes
Release historyPanaya Test Automation release history

Teams can now use APIs to retrieve test and component parameters and manage datasets and planned runs from external systems, which is what we see our customers needing the most in their AI-driven SDLC.

New Test Automation APIs

Automation engineers can connect external systems to Panaya Test Automation for parameter, dataset, and planned-run management. The new APIs retrieve test and component parameters and support creating, retrieving, updating, and deleting datasets and planned runs.

This gives teams a supported way to coordinate automation data and execution plans outside the user interface when their workflow requires it.

Focused test evidence exports

Test reviewers can choose which screenshots belong in a test evidence PDF. Panaya Test Automation 26.11.103 allows screenshots from Sleep instructions, Take Screenshot instructions, and other instructions to be included or excluded from the export.

This changes the evidence selection, not the underlying execution record. Teams can prepare PDFs with fewer screenshots that are not relevant to the review at hand.

Failed-run and agent alerts

Teams can configure an email notification when an automated execution contains one or more failed runs, including executions initiated through an API. Configure this under Configuration > Notification > Manage.

Agent monitoring also now applies a missing-heartbeat notification after 10 minutes and sends it to the inbox. This gives people responsible for unattended execution a defined signal when an automation agent stops reporting.

More resilient Windows and tree interactions

Windows automation instructions can now match application windows using wildcard support in window titles. This helps scripts identify windows when their titles vary between executions.

ScriptBuilder also adds text-matching conditions for tree-node selection. Test authors can select dynamically named nodes using Equals, Not Equals, or Contains conditions, with either fixed values or parameters.

AI-assisted execution comparison in Beta

ScriptBuilder can now perform AI-powered automatic comparison of test executions as a Beta capability. It analyzes screenshot differences, gives an overall assessment of their significance, and presents instruction-level findings with identified changes, severity, and potential impact.

The Beta label matters for teams assessing where to use this capability in their review process.

Control when AI self-healing updates scripts

Script authors can decide whether locators found through AI self-healing are automatically written back to automation scripts. The script-properties setting is enabled by default and can be configured independently for tests and components.

A locator update is saved only when the test passes, the script is checked out, and no conflicting modification exists. This makes the conditions for persisting a healed locator explicit.

Dynamic table targeting in ScriptBuilder

Test authors can use parameters and expressions for column names, column indices, and row-selection values. Scripts can therefore define table targeting with dynamic values rather than only fixed selections.

This is useful where the data structure or the target value used in a test changes across executions.

What this means for your team

QA engineers can connect execution planning and test data work to external systems, then they can receive email signals when unattended runs fail or agents miss a heartbeat. Script authors can make Windows, tree, and table interactions less dependent on fixed text or values. During daily reviews, teams can limit PDF evidence screenshots and use the Beta comparison findings along with their normal assessment. In an AI-driven SDLC, the self-healing save control lets teams decide when an AI-suggested locator becomes part of a checked-out script.

Based on the official Panaya release notes.

How Merito helps

Merito helps teams adopt and govern Panaya Test Automation capabilities through managed services, including practical workflows for automation operations and evidence review. See also Panaya Test Automation 26.10.

Merito is an authorized Panaya reseller and services partner. Our Panaya Test Automation team helps you adopt the 26.11.103 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.

About Panaya Test Automation

Panaya Test Automation licenses, renewals, upgrades and implementation are available through Merito, an authorized Panaya reseller and services partner.

Frequently Asked Questions