Page History

This release includes the following enhancements.

Release date: Month Day, 2024

Natural Language Test Scenario Creation in the AI Assistant

The chat-based AI Assistant can now analyze RESTful OpenAPI/Swagger service definitions and automatically create SOAtest tests test scenarios and data sources for you , including suggesting based on your natural language instructions. Using an agentic workflow, it can suggest multiple test scenarios, parameterizing payloads, and even populating payload data for you. See parameterize payloads based on your direction, create data sources, and automatically populate payload data for you. Over the course of your conversation with the AI Assistant, you can fine tune your test scenarios and data sources to get exactly the results you want. See Creating Tests with the AI Assistant for more information.

Manual Testing in CTP

Code Coverage and Test Impact Analysis for Manual Tests

The new Manual Testing module in CTP allows you to import easily collect code coverage data as you execute your manual tests from a CSV file and associate them with a CTP system so you can refer to them later when executing test sessions. In addition, you can start a session for any of the environments in the Manual Testing module to use when doing your manual testsand, when combined with Parasoft DTP, to reduce manual testing efforts by identifying an optimized subset of manual tests that need to be rerun to validate recent application changes (test impact analysis). When manual testing coverage data is combined with unit and functional testing coverage data in DTP, you will see a more complete picture of your testing efforts.

An easy-to-use web interface lets you import test information from your test management system using CSV. Once you have imported your tests, it's a simple matter to start your coverage agents before conducting your manual tests to capture that data and publish it to DTP for reporting and test impact analysis workflows. Java and .NET applications with web frontends and microservice backends are supported. See Manual Testing for more information.

Automatically Transfer Dependencies when Uploading Virtual Assets to a Remote Server

This feature streamlines the process of transferring virtual assets from a local server to a remote server by automatically managing and uploading their associated dependencies. When

a virtual asset is copied from a local server, it often relies on various external files or resources, such as data sources, scripts, request/response files, or configuration settings. Traditionally, users would need to manually identify and upload each of these dependencies to ensure the asset functions correctly on the remote server.

With this feature, when an asset is copied to a remote server, the local server automatically detects and uploads all associated dependencies to the remote server alongside the asset. This automation saves time and minimizes the risk of missing dependencies, ensuring the asset works correctly on the remote server

.

Using Secrets in Kubernetes Deployments

As part of configuring the soavirt-server in your Kubernetes deployment, you can choose to set up a secret for the server. See Deploying SOAtest and Virtualize in Kubernetes for more information.

gRPC Client Improvements

The gRPC client features two significant improvements. First, you can now send custom headers in metadata so your gRPC server can trace and correlate events. In addition, it now

gRPC client support for token-based authentication

The gRPC client now supports calls requiring token-based authentication. See gRPC Transport for more information.

OAuth 2.0 Authorization Code Flow Configuration Improvements

You can now configure your record the browser login steps for your web applications that use an external OAuth 2.0 authentication to use a built-in call back for the Redirect URI. This way, SOAtest can get the authorization code directly without having to explicitly set up a data bank extraction in your login suite or redirecting to another web application which may consume the authorization code. To make this easier, you can now also configure your OAuth 2.0 authentication with a convenient wizard. See authorization server and SOAtest will automatically generate an OAuth 2.0 authorization code flow reference test suite for you. See OAuth Authentication for more information.

Additional Updates

• SOAtest and Virtualize now ship with Eclipse 2025-03.
• Support for Windows Server 2025 has been added and support for Windows 10 has been deprecated.
• Support for the Java Virtualization Agent marketplace extension is deprecated and will be removed in a future release.
• Support for Oracle 18c and 21c & 21c, MariaDB 10.5 & 10.8, and MySQL 5.7 in CTP has ended.
• Support for Java 11 has ended.
• The AI Assistant has been enhanced to produce more consistent responses from a wider set of LLMs. To support this, the configured LLM must now support structured outputs.
• CTP environment diagrams now show the state of configured coverage agents.
• The Parasoft marketplace now contains a VAPI script to easily integrate with OpenText ALM/Quality Center.
• The SOAtest Maven plugin can now pass or fail a build based on SOAtest test results.

• The following enhancements have been made for the Protobuf marketplace extension:

  • 
    

    Automatically detect and consume ProtoJSON.

  • Support for proto files referencing other proto files in nested directories.

  • Command line option to include files from the protoc include directory.

• CTP's licensing tiers for coverage agents has changed. All users now have access to up to five coverage agents, with seven new tiers allowing access to between 25 and 500 coverage agents.  
• The CTP Asset Utilization Report now includes coverage agents.

• Explicit support for Parlay / Parlay-X has been removed. If needed, it can still be achieved by using custom XPath correlations in the Call Back tool.

• CTP now supports Oracle RAC Fast Application Notification (FAN) events for Fast Connection Failover when the Oracle database connection is configured using a JDBC URL. Be aware that you will need to supply the following three jars and all three must be from the same version and provider source: ojdbc11ojdbc17.jar, ons.jar , and ucp11ucp17.jar. 
• Several new configuration options are available for tThe SOAtest and Virtualize WAR server can now force virtual assets to be deployed on unique basepaths using the virtual.asset.deployment.path.enforce.unique.basepaths configuration optiondeployment, letting you manage your service deployment routes to avoid conflicts. These configuration options let you specify what paths can be used, what paths are blocked, and whether or not unique base paths are required. Deploying on the base path is now blocked by default. See Server Deployment Path Settings for more information about these configuration options.
• The misc.hide.masked.variables setting has been changed to mask.sensitive.data and now also hides authorization request headers in displayed traffic and, in SOAtest, password input fields in HTML browser contents. This option can also be set in the UI by enabling Sensitive Data in Mask sensitive data in displayed traffic in the Miscellaneous Settings. See Additional Preference Settings#Misc Settings.

• -loadtestserver

  command

   command line option for Load Test is

  now

  now -agent. See Load Test Command Line Interface.

• You can now configure how many days CTP retains Virtualize hit summary data to prevent your database from growing out of control while still providing useful information for actions like determining your current Virtualize Hits/day licenses needs.
• MTOM payloads larger than 2GB are now supported.

Breaking Changes

• The Parasoft JDBC driver now supports applications compiled against Java 11 or later. It will no longer support older Java versions.
• The Attachment Handler will now pass a DataHandler input to Extension Tools instead of a String. See Attachment Handler for more information.

Resolved PRs and FRs