Page History

...

Easier Generation of Dynamic Lists in Response Payloads

New JSON and XML List Processor tools allow you to select items from a payload to be processed individually, enabling you to build a dynamic list for use in an outgoing payload based on the content of those items. They can be chained to another tool (for example, a message responder or REST client) or used as stand-alone tools. The tools process each selected item individually, allowing you to perform data source lookups or other processing steps to generate item-specific content to include in the outgoing payload (such as details for an item id specified in the original payload). The tools aggregate each outgoing item into a list that is inserted into the outgoing payload. A primary use case is to build response payloads in Virtualize based on the content included within incoming requests.

These tools replace the Multiple Response Generator, which is now deprecated, and add support for JSON (whereas the Multiple Response Generator only supported XML) while removing the need for multiple virtual assets (a "front-end asset" and "back-end asset") to be deployed to support the use case.

See JSON List Generator and XML List Generator for more information about these tools

.

These tools replace the Multiple Response Generator, which is now deprecated, and adds support for JSON (whereas the Multiple Responses Generator only supported XML) while removing the need for multiple virtual assets "front-end asset" and "back-end asset" to be deployed to support the use case.

See JSON List

Generator

Processor and XML List

Generator

Processor for more information about the tools and Handling Lists with a Dynamic Number of Items for a tutorial showing the JSON List Processor in action.

Viewing Asset Utilization by Team or Project

Product: (SOAtest, Virtualize)

The Asset Utilization Report in CTP supports multiple new features to make it easier for organizations to understand their usage of Parasoft Virtualize.

Data can now be reported by team or by project when you organize assets on Virtualize servers using folders in the VirtualAssets project. By default the report now groups data by folders, so that when you first view the report it is easy to see usage aggregated by team or project or any other organization method you choose

.

The report also supports new metrics: Peak Hits per Second and Average Hits per Second. This data allows you to get a better understanding of which teams and/or assets have the highest usage spikes.

Data in the report can now be exported to a CSV file, easily enabling the data to be consumed and processed by external tools.

The Asset Utilization Report in CTP supports multiple new features to make it easier for organizations to understand their usage of Parasoft Virtualize

.

Data can now be reported by team or by project when you organize assets on Virtualize servers using folders in the VirtualAssets project.

The

report now groups data by folders by default, so that it is easy to see usage broken down by folder when first viewing the

report

. When folders are used to separate assets by team or by project, you can gain insight into asset usage per team or per project.The report

also supports new metrics: Peak Hits per Second and Average Hits per Second. This data allows you to get a better understanding of which teams and/or assets have the highest usage spikes.

Data in the report can now be exported to a CSV file, easily enabling the data to be consumed and processed by external tools.

AI Assistant and AI Tool Enhancements

Test scenarios created from the AI Assistant now contain assertions if the user includes instructions to perform validation of specific requirements. Assertions are created by adding LLM-enabled AI Assertor tools to appropriate REST Clients within the scenarios.

The The AI Assistant now supports creation of test scenarios that span multiple microservices by allowing you to specify multiple service definition files.

The AI Assertor and AI Data Bank tools can now be applied to web browser test scenarios by chaining them to the Browser Contents output of Brower Playback Tools.

MCP Client and MCP Listener Enhancements

MCP Client now supports OAuth and Basic authentication.
MCP Listener has updated the heartbeat mechanism and added the ability to disable heartbeat.
Both MCP Client and MCP Listener now support the Streamable HTTP transport.

Identify When Virtual GraphQL Services Need to be Updated

You can now identify incoming GraphQL queries to the Virtualize server that no longer adhere to the schema for a GraphQL service, so that callers know they need to update their GraphQL queries and their GraphQL responders when the schema changes. This is done through the new GraphQL Query Validator tool, which validates GraphQL queries against a schema defined using Schema Definition Language (SDL). The new tool can be attached to any tool that sends or receives messages in GraphQL format to verify that the queries are valid. See GraphQL Query Validator for more information.

Also

Also see Validating Incoming Requests for an example of using validators like this one in a common workflow.

Adding MIME Attachments to Outgoing Messages

Scroll Ignore

This release includes the following enhancements.

Table of Contents

maxLevel	2

Release Initial release date: October 14, 2025
Latest update (SOAtest and Virtualize): 2025.3.5 (August 24, 2026)
Latest update (CTP): 2025.3.6 (August 24, 2026)

Automatic Identification of Manual Tests Impacted by Application Changes

You can now identify an optimized subset of manual tests that need to be run to sufficiently test recent application changes or perform manual regression testing for release. This allows your team to focus testing on only a specific set of tests while still having the confidence that sufficient testing was done.

You can see a real-time view of the execution status of each manual test for a given application in a given environment - passed, failed, incomplete, impacted (needs retesting), or not executed. This view automatically updates as you execute tests or whenever the application changes. If the underlying code that is associated with a previously executed manual test changes, the view will automatically update the test status to show that it is impacted and needs retesting. With this summary, you can focus your efforts on manual tests that are impacted or haven't been run yet. If a test is shown as passing and is not impacted - you know that you don't need to run the test again, even if the build has been updated since you ran the test.

In addition, Manual Testing in CTP now requires a separate license.

conditionalcontent

Product: (SVC)