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.1.0.0.

No-code Automation

Allows users to automate tests without the need for coding skills. This feature makes it easy for all customers to adopt STAP, including those with no coding background.

Extensible Plugins

Provides a broad suite of plugins to test different environments, making it a versatile solution for testing software. It supports various types of plugins, including web, mobile, and API testing.

Application Monitoring

Monitors application interfaces, such as Web or REST endpoints, in real time and provides insights into the performance and behavior of the application, allowing users to identify potential issues and optimize performance.

Integration with Test Tools

Works seamlessly with other testing tools, enabling users to integrate it into their existing workflows. This feature makes it easier for teams to adopt STAP without disrupting their current processes.

Seed Data Loading

Loads seed data to target systems with configuration and without any code or scripts.

Failure Detection

Helps detect failures swiftly. The screenshot and test execution video gives a visual replay of the test execution and helps identify what went wrong.

Performance Metrics Gathering

Logs performance information which can be used to generate metrics and comparisons with previous runs (builds or releases).

Reports Generation

Generates standard reports and supports plugins to generate reports in custom formats.

Synthetic Data Generation

The Synthetic Data Generator is a critical component of a test automation platform, designed to produce diverse, scalable, and high-quality data for testing applications. It eliminates the reliance on real-world data by generating customizable datasets that emulate production-like conditions, ensuring comprehensive test coverage and improving testing efficiency.

STAP offers internal and external types of plugins for synthetic data generation.

  • Internal plugins handle various data types, including numeric, alphanumeric, and text.
  • External plugins connect with third-party providers. Currently integration with Data Faker application is supported.

Known Problems

This section lists the known problems in this release of STAP.

  • Job Names Cannot Contain Numeric Values
    • Job names that include numeric values (for example, Job1 or Job101) cause issues.
    • Workaround: Use only alphabetic and special characters in job names. For example, use "Sanity Test Job" instead of "Job1".
  • Error When Updating an Existing Scenario During Publishing
    • If you attempt to update an existing scenario while publishing, it 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.
  • SOAP Action Publishing Does Not Include Request Data
    • When publishing a SOAP action, the default request data is not included.
    • Workaround: Use the SOAP request data from the scenario instead of relying on the action's default request data.
  • 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.
  • Only Non-Referenced and Unused Jobs Can Be Deleted
    • To ensure retention of historical job data, you cannot delete a job that has an execution history or any reports.
  • Valid Input Required for Connection Type When Creating an Environment
    • In the Environment Connection UI, you must provide a valid input for the connection type; otherwise, job failures may occur.
    • Workaround: Ensure a valid value is entered for the connection type. See Action Plugins environment configuration documentation for more details.
  • The History page displays identical steps for all cases.
    • In the History page, the listed cases display same sequence of steps for all cases.
    • Workaround: Detailed case-specific steps can be accessed through execution service reports.