1 Release Notes
This document provides the release notes for Oracle Solution Test Automation Platform (STAP) 1.25.1.0.0.
This document contains the following sections:
New Features
This section describes the new features in STAP release 1.25.2.0.0.
- UI Automation Plug-in
- JMX Plug-in
- Publishing Automation Reports
- Automated Proxy Configuration
- New STAP REST API
- Configuring the Heap Size for JVM
- Creating Reference Cases
- Additions to Keys in Helm Chart for the TES Microservice
- Automated Backup and Restore of the STAP Database
- Handling Escape Characters
- SOAP Plug-in Query Parameter Support
- Action Execution Enhancements
UI Automation Plug-in
The STAP UI Automation Plug-in enables low-code, browser-agnostic web UI automation within the STAP framework. This release adds intelligent wait handling, self-healing selectors, DOM stabilization, and automatic retry logic to reduce test flakiness and improve reliability. The plug-in extends the Action Plug-in Framework for consistent test automation across REST, SOAP, SSH, and UI actions.
JMX Plug-in
STAP now supports the JMX Plugin, enabling monitoring and management of Java applications and their resources within the platform.
Publishing Automation Reports
You can publish automation reports for scenarios run in a PDF format, or in a user-interactive HTML format. For more information, see "Publishing Reports" in User Operations Guide.
Automated Proxy Configuration
You do not have to manually set the proxy configuration for your environment and cluster anymore. The deployment process automatically detects and applies proxy configuration specified in the override-values.yaml file.
New STAP REST API
STAP contains a new REST API that allows you to create and manage scenarios, environments, jobs, actions, and users. For more information, see REST API Reference for Solution Test Automation Platform.
Configuring the Heap Size for JVM
You can configure the heap size for the Java Virtual Machine (JVM) to prevent “Out of Memory” error messages in the log file. For more information, see "Increasing Heap Size to Avoid “Out of Memory" Error Messages".
Creating Reference Cases
STAP now supports reference cases, which allow you to define a case once and reuse it across multiple scenarios. Any updates to the original case automatically apply wherever it is referenced, reducing duplication and ensuring consistency. For more information, see "Reference Case".
Additions to Keys in Helm Chart for the TES Microservice
The keys in the values.yaml file for the TES microservice have been updated to support global variables and the PDF generator adapter.
Automated Backup and Restore of the STAP Database
STAP now supports automating the backup and restore of its database. You can choose to backup and restore the database either automatically or manually. For more information, see :"Backing Up And Restoring STAP".
Handling Escape Characters
- Date Validation Escape Character: The escape character used for date validation is now retained during script publishing, ensuring accurate date handling.
- Function Data Enhancement: Commas are now supported in function arguments and
data variable values. Use the
%{COMMA}escape function to include commas within argument values, providing more flexibility in data handling.
SOAP Plug-in Query Parameter Support
The SOAP plug-in now accepts query parameters using the $query
variable in Data. You can define a single $query parameter, which will
be appended to the URL after processing variables, enabling more dynamic API
testing.
Action Execution Enhancements
This release introduces the new Repeat Case feature for Dynamic Action Control. This allows for the repeated execution of a case until validation is successful, ensuring precise and adaptable automation. The Repeat Case function requires at least one condition, offering flexibility in automation workflows.
Known Problems
This section lists the known problems in this release of STAP.
- Error When Updating an Existing Scenario During Publishing
- Attempting to update an existing scenario while publishing results in an error.
- Workaround: Append a version number at the end of the scenario name before publishing. This will create a new scenario that can be used in jobs.
- Duplicate Environment Names are Allowed
- The system allows multiple environments to be created with the same name.
- Workaround: Before creating a new environment, search for existing ones to avoid duplicates.
- Runtime Dashboard Stops Displaying Data due to Connection
Issues
- The UI runtime dashboard stops displaying data due to disconnections or network issues.
- Workaround: Refresh the page and re-login to restore data visibility.
- Only Non-Referenced and Unused Jobs can Be Deleted
- Jobs with execution history or reports cannot be deleted in this release to retain historical data of jobs.
- Typo in the values.yaml File for STAP DB Restore in the TDS
Deployment
- There is a typo in the
values.yamlfile for STAP DB restore in the TDS deployment. - Workaround: Update the value under restore from
enabletoenabledin the TDS Helm chartvalues.yamlpresent in the TDS Cloud Network Took Kit (CNTK):
restore: enabled: true - There is a typo in the