Page History

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

This release includes the following enhancements.

Release date: Month Date, Year

MCP Tool Updates

Initial release date: April 28, 2026
Latest update: 2026.1.3 (August 24, 2026)

Virtual Service Creation Using Agentic AI Workflows

The MCP tools that you can use with Virtualize have been greatly expanded. You can now create virtual services from a service definition, including virtual services limited to specific resources in that definition. In addition, if your LLM supports sampling and your MCP tool has permission to use it, you should see much better sample values in your requests and responses. Lastly, your MCP tool will track which virtual services it has created so it can tell what it can do further work on. Just ask it which virtual services it has access to and it will list them for you.

Note: The account you're authorizing with in MCP must have at least Provision access in your Virtualize server to use MCP tools.

Visual Diff Mode

You can now chain an AI Assertor, AI Databank, or Write tool to the screenshot output of browser playback tests. While the first two improve your ability to utilize Parasoft's AI abilities with your visual testing, the latter enables the new Visual mode in the Diff tool. The Visual Diff tool lets you compare images in your tests so that visual differences can be automatically flagged. Control images can come from a test run, a data source, or a file on your drive. You also have the ability to adjust the tool's sensitivity to changes and define areas that should be ignored during comparison. See Visual Diff Mode for more information.

Path-Based Matching

directly from your LLM client, including tools like Copilot in VS Code and Claude Code, without using Virtualize Desktop. You can also create and update virtual services from agentic CLI or CI/CD workflows with tools such as Copilot CLI. Simply connect the Virtualize MCP server to your LLM client and ask it to create REST-based virtual services. Provide a service definition, request and response pairs, or even a simple description of the service, and Virtualize will generate a usable virtual service for you. After creation, the Virtualize MCP server also lets you edit or delete virtual services. See Configuring SOAtest as an MCP Server for more information.

Note: If you are upgrading from an earlier version, you will need an updated license from Parasoft to use the new MCP functionality.

Code Coverage Reporting and Test Impact Analysis for Partial Automated Functional Test Runs

Code coverage reporting and test impact analysis (TIA) in CTP and DTP now support automated test workflows where each run includes only a subset of the full test suite. This enhancement helps teams that cannot execute all tests in a single run against one build. Previously, code coverage reporting required all tests to run against a single build, and TIA required at least one baseline build with a complete test run to identify impacted tests for later builds. Now, the data needed for code coverage and impacted test reporting can be built incrementally across multiple test runs against different builds. See Collecting Coverage for Microservices Guide for more information.

Coverage Agent Self-Registration and Enhanced Cloud Environment Support

The Java and .NET coverage agents can now self-register with CTP when they start up. This simplifies setup by allowing the required configuration to be handled as part of your build and deployment process, reducing the need for manual configuration in CTP from the web interface or REST API. This enhancement also improves support for load-balanced and cloud-based environments where coverage agents cannot be contacted directly.

Visual Regression Testing for Web Applications

You can now perform visual regression testing as part of your automated web UI testing workflow. During playback, screenshots are captured and compared to validate the full page or specific areas of the page, with any differences detected and reported. This can reduce reliance on flaky locator-based assertions and make it easier to verify both the appearance and content of your application.

Improved URL Path Parameter Matching in Virtualize

You can now configure URL path parameter matching in request correlation, REST URL data banks, and inline expressions using parameter names as well as parameter indices. Using parameter names makes path matching more stable, even when the deployment path of the virtual asset changesYou can now configure data source value mappings based on either parameter names or path segment indexes. The latter allows you to configure path-based data banks, correlations, or inline expressions that are stable regardless of deployment path. See Message Responder Overview: Request URL Paths, Customizing Request Matching and Correlations#Request Correlation, REST URL Data Bank#Configuring the REST URL Data Bank Tool, and Extracting Request Values to Populate Responses in Virtualize#Functions for Extracting Information from Headers or URLs for more information.

You can now configure your application under test with a coverage agent that will, upon startup, register itself with a specific system/environment in CTP.

Customized SQL Responder Data Storage

SQL Responders can now be configured to store recorded data in a folder of your choosing, allowing you greater customization and the ability to manage multiple teams on a shared server where each team has their own directory on the server for assets and data. See SQL Responder and JDBC Driver Configuration for more information.

Breaking Changes

• The

• SOAtest MCP server now requires a license that includes the new MCP Server license feature. If you are upgrading, you must obtain an updated license to continue using the MCP server.

Additional Updates

• You can now constrain your GraphQL Message Responders, Clients, and Query Validators using an introspection URL instead of an SDL. See GraphQL Message Responder, GraphQL Query Validator and GraphQL Client for more information.

• The AI Assistant has been updated to require explicit instructions before it will add an AI Assertor to tests it creates. You can also describe specific values for payload elements in your prompt and they will be applied as appropriate.

• If you use AWS, you can now authenticate requests using AWS Signature Version 4, allowing you to make AWS API requests from a TST or PVA. See Adding Global Properties#Global Authentications for more information.

• Assertor tools and the Data Repository CRUD Tool can now be used for validation in pre-correlation inputs for virtual assets, allowing you to validate requests and respond using results from those tools.

• Header details are now shown when creating message responders with the Virtualize traffic wizards, making it easier to assure that the request correlation you configure will produce the expected outcome. See Creating Parameterized Message Responders from Traffic and Creating Fixed Message Responders from Traffic for more information.

• Added a new option to the Request/Response Files mode of a Message Responder to make the server keep searching for a matching responder if none of the request files match the incoming search. In addition, wildcard matches are now supported in the following parts of the request: URL path, URL query parameter, and payload. See Request Response Files for more information.

• New endpoints in the Virtualize REST API have been added to work with individual message proxy connections. These connections can also now be named.
• The throughput limitation on Message Proxies for Runtime Server has been removed

Additional Updates

• SOAtest and Virtualize now ships with Eclipse 2025-09.
• For the Fixed Length Client and Fixed Length Call Back tool, you can now define a field that is of variable length, so that the data model can read the last field of your message when it contains fewer characters than its defined length.
• JDBC Driver Hybrid mode has been given robust handling when Virtualize or the original database is not available.
• When a TST is copied to a remote server, all associated dependencies are automatically detected and uploaded to the remote server alongside the TST.

• Added support for including environment and test output details in the XML report from SOAtest desktop. This was previously only supported in SOAtest server.

• The CTP REST API can now publish coverage results asynchronously, improving support for large volumes of coverage data. 
• You can now configure the Diff tool so it won't flag a difference just because an XPath element's position/index changes in relation to the parent node (or when it "moves" relative to the parent node). See Diff Tool: Understanding XPaths for more information.

• The AI Assistant has been updated to require explicit instructions before it will add an AI Assertion to tests it creates. You can also give it specific payload data in your prompt.

• Added the ability to name connections within proxies. These names are used to work with specific connections within the proxy through the REST API.

• If you use AWS, you can now authenticate requests using AWS Signature Version 4, allowing you to upload files to an S3 bucket from a TST or PVA. See Adding Global Properties#Global Authentications for more information.

• You can now constrain your GraphQL message responders by either a GraphQL SDL or an introspection URL. See GraphQL Message Responder for more information.

• When running Load Test from the command line, you can now run it with a -fail option to fail the command by returning a non-zero exit code if QoS metric failures or other errors are reported.

• Load Test Continuum has been updated with improved graphs that now allow you to get data for specific dates and include a threshold graph that can be toggled on and off.

• Added a new option to make the server keep searching for a matching responder if none of the request files match the incoming search. In addition, wildcard matches are now supported in the following parts of request: URL path, URL query parameter, and payload. See Request Response Files for more information.

• The The defaultTransport attribute in custom message formats now supports the usage of custom transports. See Adding a Custom Message Format#definingParasoft for more information.

• For the Fixed Length Client and Fixed Length Call Back tool, you can now define a field that is of variable length, so that the data model can read the last field of your message when it contains fewer characters than its defined length.

• SOAtest and Virtualize now ships with Eclipse 2026-03.
• CTP now supports Oracle AI Database 26ai.

Resolved PRs and FRs

SOAtest and Virtualize

CTP

Updates in 2026.1.1

SOAtest and Virtualize

Resolved FRs and PRs

CTP

Resolved FRs and PRs

Updates in 2026.1.2

SOAtest and Virtualize

Resolved FRs and PRs

CTP

Resolved FRs and PRs

Updates in 2026.1.3

SOAtest and Virtualize

Resolved FRs and PRs

CTP

Resolved FRs and PRs