Best Of
SOAtest, Virtualize, CTP 2026.1 Product Release Announcement
We’re excited to announce that Parasoft SOAtest, Virtualize, and CTP 2026.1 are here! This release focuses on bringing AI-driven workflows deeper into your testing process while making service virtualization, code coverage analysis, and web UI testing more scalable and automated than ever.
Here’s what’s new and why it matters to you:
AI-Powered Service Virtualization in Your Workflow
Virtualize 2026.1 brings service virtualization directly into modern AI-driven development workflows.
Developers can now connect their LLM clients to the Virtualize MCP server to generate, deploy, and manage REST-based virtual services, without leaving their AI-enhanced IDE or workflow.
This enables:
- Agentic AI workflows – Virtual services can be autonomously created and updated as part of your pipeline.
- Smarter test data – Virtual responses include more realistic example data when LLM clients that support sampling are used.
- Note: New licenses are required to enable MCP features for users who migrate from an earlier version of the product.
See Using Parasoft Tools as an MCP Server for details.
Code Coverage Reporting and Test Impact Analysis for Partial Automated Functional Test Runs
CTP 2026.1 introduces enhanced coverage agents designed for cloud and clustered environments, making large-scale coverage collection more efficient and practical.
Key enhancements include:
Incremental Coverage & TIA Across Test Runs
- Support for automated workflows where each run executes only a subset of tests
- No longer requires a baseline build with complete test execution for TIA
- Code coverage and impacted test data can now be built incrementally across multiple runs and builds
Coverage Agent Self-Registration
- Java and .NET coverage agents now automatically register with CTP on startup reducing manual setup in the CTP web interface
- Configuration can be handled directly within build and deployment pipelines
Enhanced Cloud & Load-Balancer Support
- Improved compatibility with cloud-native and distributed environments
- Supports scenarios where coverage agents cannot be directly accessed
This means teams with large test suites no longer need to run everything at once to get a clear view of their complete application coverage—incremental code coverage and test impact analysis can now scale with your development process. See Collecting Coverage for Microservices and Connecting CTP to Coverage Agents for how to enable these workflows.
Automated Visual Regression Testing
SOAtest 2026.1 introduces built-in visual validation as part of your automated web UI testing workflows.
With this update, you can:
- Automatically capture screenshots during test execution
- Detect UI regressions using visual diff comparisons
- Embed visual testing results directly into XML and HTML reports
This makes it easy to validate UI changes as a part of functional testing, bringing visual regression testing into your standard automation and reporting flow.
With 2026.1, you can move faster with AI-assisted service virtualization, scale your testing with test impact analysis and incremental code coverage, and expand validation with automated visual regression—all within your existing workflows.
Review the release notes to learn more about the 2026.1 release of SOAtest, Virtualize, and CTP.
jakubiak
SOAtest, Virtualize, CTP 2026.1 Product Release Announcement
We’re excited to announce that Parasoft SOAtest, Virtualize, and CTP 2026.1 are here! This release focuses on bringing AI-driven workflows deeper into your testing process while making service virtualization, code coverage analysis, and web UI testing more scalable and automated than ever.
Here’s what’s new and why it matters to you:
AI-Powered Service Virtualization in Your Workflow
Virtualize 2026.1 brings service virtualization directly into modern AI-driven development workflows.
Developers can now connect their LLM clients to the Virtualize MCP server to generate, deploy, and manage REST-based virtual services, without leaving their AI-enhanced IDE or workflow.
This enables:
- Agentic AI workflows – Virtual services can be autonomously created and updated as part of your pipeline.
- Smarter test data – Virtual responses include more realistic example data when LLM clients that support sampling are used.
- Note: New licenses are required to enable MCP features for users who migrate from an earlier version of the product.
See Using Parasoft Tools as an MCP Server for details.
Code Coverage Reporting and Test Impact Analysis for Partial Automated Functional Test Runs
CTP 2026.1 introduces enhanced coverage agents designed for cloud and clustered environments, making large-scale coverage collection more efficient and practical.
Key enhancements include:
Incremental Coverage & TIA Across Test Runs
- Support for automated workflows where each run executes only a subset of tests
- No longer requires a baseline build with complete test execution for TIA
- Code coverage and impacted test data can now be built incrementally across multiple runs and builds
Coverage Agent Self-Registration
- Java and .NET coverage agents now automatically register with CTP on startup reducing manual setup in the CTP web interface
- Configuration can be handled directly within build and deployment pipelines
Enhanced Cloud & Load-Balancer Support
- Improved compatibility with cloud-native and distributed environments
- Supports scenarios where coverage agents cannot be directly accessed
This means teams with large test suites no longer need to run everything at once to get a clear view of their complete application coverage—incremental code coverage and test impact analysis can now scale with your development process. See Collecting Coverage for Microservices and Connecting CTP to Coverage Agents for how to enable these workflows.
Automated Visual Regression Testing
SOAtest 2026.1 introduces built-in visual validation as part of your automated web UI testing workflows.
With this update, you can:
- Automatically capture screenshots during test execution
- Detect UI regressions using visual diff comparisons
- Embed visual testing results directly into XML and HTML reports
This makes it easy to validate UI changes as a part of functional testing, bringing visual regression testing into your standard automation and reporting flow.
With 2026.1, you can move faster with AI-assisted service virtualization, scale your testing with test impact analysis and incremental code coverage, and expand validation with automated visual regression—all within your existing workflows.
Review the release notes to learn more about the 2026.1 release of SOAtest, Virtualize, and CTP.
jakubiak
SOAtest, Virtualize, CTP 2026.1 Product Release Announcement
We’re excited to announce that Parasoft SOAtest, Virtualize, and CTP 2026.1 are here! This release focuses on bringing AI-driven workflows deeper into your testing process while making service virtualization, code coverage analysis, and web UI testing more scalable and automated than ever.
Here’s what’s new and why it matters to you:
AI-Powered Service Virtualization in Your Workflow
Virtualize 2026.1 brings service virtualization directly into modern AI-driven development workflows.
Developers can now connect their LLM clients to the Virtualize MCP server to generate, deploy, and manage REST-based virtual services, without leaving their AI-enhanced IDE or workflow.
This enables:
- Agentic AI workflows – Virtual services can be autonomously created and updated as part of your pipeline.
- Smarter test data – Virtual responses include more realistic example data when LLM clients that support sampling are used.
- Note: New licenses are required to enable MCP features for users who migrate from an earlier version of the product.
See Using Parasoft Tools as an MCP Server for details.
Code Coverage Reporting and Test Impact Analysis for Partial Automated Functional Test Runs
CTP 2026.1 introduces enhanced coverage agents designed for cloud and clustered environments, making large-scale coverage collection more efficient and practical.
Key enhancements include:
Incremental Coverage & TIA Across Test Runs
- Support for automated workflows where each run executes only a subset of tests
- No longer requires a baseline build with complete test execution for TIA
- Code coverage and impacted test data can now be built incrementally across multiple runs and builds
Coverage Agent Self-Registration
- Java and .NET coverage agents now automatically register with CTP on startup reducing manual setup in the CTP web interface
- Configuration can be handled directly within build and deployment pipelines
Enhanced Cloud & Load-Balancer Support
- Improved compatibility with cloud-native and distributed environments
- Supports scenarios where coverage agents cannot be directly accessed
This means teams with large test suites no longer need to run everything at once to get a clear view of their complete application coverage—incremental code coverage and test impact analysis can now scale with your development process. See Collecting Coverage for Microservices and Connecting CTP to Coverage Agents for how to enable these workflows.
Automated Visual Regression Testing
SOAtest 2026.1 introduces built-in visual validation as part of your automated web UI testing workflows.
With this update, you can:
- Automatically capture screenshots during test execution
- Detect UI regressions using visual diff comparisons
- Embed visual testing results directly into XML and HTML reports
This makes it easy to validate UI changes as a part of functional testing, bringing visual regression testing into your standard automation and reporting flow.
With 2026.1, you can move faster with AI-assisted service virtualization, scale your testing with test impact analysis and incremental code coverage, and expand validation with automated visual regression—all within your existing workflows.
Review the release notes to learn more about the 2026.1 release of SOAtest, Virtualize, and CTP.
jakubiak
Re: Get a JSON node's child whose attribute equals a specific value?
You can use the JSON Assertor. For these you can create a "Value" assertion where you can click "Change Element" then select "Edit XPath manually".
verify "content" now has two children
Use XPath count(/root/data/content/*) with expected value of 2.
verify "content" has a child whose "contentType" is "EXTENDED"
Use XPath count(/root/data/content[*/contentType='EXTENDED']) with expected value of 1.
DIFF tool - parasoft SOA test how to use
Scenario: Compare two files -> File A [ json or XML] File B [ json or XML] and compare in DIFF , how to use it ?
And again compare File B and File C [ json or xml] , now after these comparisons , a global message called GM- final XML will be triggered if file comparisons are accurate and only creation will happen if it spots any differences in that DIFF tool , if 0 differences no GM will be created.
Pattu
Re: How to Transform Expected Value to Regular Expression
Thanks for the detailed description. I believe I understand what you are trying to do now.
So for instance you first receive a response that looks like this: (with other elements also in the response)
<xml>
...
<values>test tester testers</values>
...
</xml>
Then you make a new query wherein a separate response looks like this:
<xml>
...
<singlevalue>testers</singlevalue>
...
</xml>
And now what you want to do is check to make sure that the "<singlevalue>" element contains one of the strings from the "<values>" element.
You have the right idea in using a regular expression assertion however I think there is something a little easier that you can do to create the regular expression rather than just transforming the values of the response.
What I recommend is that you store the regular expression inside of a Test Suite Variable and then parameterize the regular expression against this test suite variable. I have attached a very simple tst file that shows you can achieve this. (i created the file in SOAtest 6.2 service pack 5 so you may need to update to that service pack in order to open the tst file: SOAtest > Check for Updates (assuming you already have SOAtest 6.2)).
Here's a description of what i did in the tst file and you can easily move this over to your own implementation:
1) I attached a Response SOAP Envelope --> XML Data Bank as an output to the test that receives the response containing the element with three values.
-- Inside the Data Bank, I extract the value for the element and give it a data source column name (i.e. values).
2) Next I added a Test Suite Variable to the root test suite folder that containes the tests I'm running.
-- I double click the scenario node > Select the "Test Variables" tab > Click "Add" > Give the variable a name (ie "ValueRegExp") > Type: String > Select the "use local value" radio button > clear the value field so that it's empty. > Click OK.
-- Save the changes.
3) Next I added an Extension Tool Test, right after the Test that receives the response with three values in the element (it doesnt have to be immediately after, just sometime after this test).
-- In the extension tool I wrote the following code:
from com.parasoft.api import *
def createRegExp(input, context):
values = context.getValue("Generated Data Source", "values")
value = values.split(" ")
return context.setValue("ValueRegExp", value[0] + "|" + value[1] + "|" + value[2])
Note that I used the "Python" language and that I checked the box indicating that the "Return Value indicates success".
What this code does is:
a) it grabs the value you extracted in the XML Data Bank (values = context.getValue("Generated Data Source", "values"))
b ) stores them in a "value" array by the java function call ( value = values.split(" ") )
c) sets the value for the test suite variable with the value "value1|value2|value3" (return context.setValue("ValueRegExp", value[0] + "|" + value[1] + "|" + value[2]))
4) Then in the test wherein I receive a response that contains a single value, I add an XML Assertor as ouput. In the configuration for a regular expression, I changed it to "parameterized" and selected the name of the test suite variable I selected.
After saving all changes and running the test suite, you can see that the test passes since I receive a value that is one of the three values. You can change the value in the test to be anything else so you can see it fail as well.
If you have any questions, please feel free to let me know. Otherwise, adapting these steps to your own test should allow you to do regular expression assertions with those three values.
Thanks,
Denard
Re: How do I output traffic response from data-driven test into an excel file?
For reporting, SOAtest generates reports in XML and HTML format. Traffic is included for failing test cases but you can optionally enable traffic for passing test cases as well. In the test configuration, look for "Report traffic for all tests".
Announcing Parasoft Selenic 2026.1
The latest release of Parasoft Selenic (2026.1) is now available. This release expands the capability of Selenium tests created from recording while enhancing the configuration options available and adding support for the latest tools and environments used by testers.
Parasoft Selenic now supports the following:
- Configuration of locator strategies in the Parasoft Recorder Chrome extension
- Parasoft Selenic Docker image on Docker Hub
- Actions to close a subwindow are now recorded and included in generated tests
- Improved and shortened the length of class and variable names in certain cases
- Added support for IntelliJ 2025.3
Review our release notes to learn more about the 2026.1 release of Selenic.
Scope not speciefied
INFO: Scope not specified: No resources specified as scope, using all workspace projects as selected scope.
Hi everyone, I am running unittest and for the scope I have given "-data ${CPPTEST_WORKSPACE}" but I got that error. I have tried also with "-resource ${CPPTEST_WORKSPACE}" but it didnt help. Does anybody know why that it happens?
tani
Re: Resource Permissions via API
Hi Jeff,
CTP only allows resource permission changes through the web interface. There was never an API for resource permissions. The only change related to resource permissions and jobs was back in 2020. See the release notes at https://docs.parasoft.com/display/SVC20253/SOAtest+Virtualize+and+CTP+20201
Resource Permissions for Jobs
The ability to execute, create, and delete jobs is now protected by resource permissions. As a result, users with provision roles can only execute jobs and view reports to which they have been given access through resource permission controls. If you want to continue anonymously executing jobs and viewing reports in CTP without logging in, disable the Restricted option in the Resource Permissions screen. This option is enabled by default.