Visit https://docs.parasoft.com/display/SVC20253/Release+Notes for the latest release information.

This release includes the following enhancements.

Release date: October 14, 2025

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.

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 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 Processor and XML List 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

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. See Creating Tests with the AI Assistant for more information.

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 see Validating Incoming Requests for an example of using validators like this one in a common workflow.

Adding MIME Attachments to Outgoing Messages

The new Attachments tool allows you to add MIME attachments to an outgoing message before it is sent. This tool is primarily used to add binary attachments to a SOAP message according to the "SOAP with Attachments" (SwA) specification. This replaces the SwA functionality that was removed in the 2024.1 release. See Attachments Tool for more information.

Additional Updates

• SOAtest and Virtualize now ships with Eclipse 2025-09.
• Support for Windows 10 has now ended.
• You can now specify a request or response for the asynchronous socket listener and transport using hex values in a String, making it easier to configure the payloads. See Asynchronous Socket Transport 1.1 and Asynchronous Socket Listener 1.1 for more information.
• CTP users with an LLM Integration license can now access the Parasoft Intelligent Digital Assistant (IDA) from the Help menu in CTP. The Parasoft IDA is an LLM-powered chatbot designed to answer user's questions about Parasoft products.

• It is no longer necessary to pass a license to the Java or .NET coverage tools when creating a static coverage file for usage in application coverage workflows.

• Parasoft Search now scans environments in .tst and .pva files.
• SOAtest reports now include errors for .tst files that did not run because SOAtest couldn't open them.
• Standalone tools now resolve variables in the input tab text mode.

• Remote OS Command Injection (Time Based) rule added to supported Penetration Testing Rules.

Resolved PRs and FRs

SOAtest and Virtualize

CTP

Resolved PRs and FRs in 2025.3.1

SOAtest and Virtualize

CTP

Resolved PRs and FRs in 2025.3.2

SOAtest and Virtualize

CTP

Resolved PRs and FRs in 2025.3.3

CTP

Resolved PRs and FRs in 2025.3.4

CTP