Release date: October 7, 2022

Enhanced OAuth 2.0 Support

Support for OAuth 2.0, the industry-standard protocol for authorization, has been improved. We have added the ability to more easily test applications that authenticate using OAuth 2.0 and simplified the process to improve the user experience. Users can now create a reusable login test suite to get an OAuth 2.0 authorization code that will then automatically be applied to all relevant requests in the test scenario. The three most common grant types are supported: Authorization Code, Authorization Code with PKCE, and Client Credentials. 

Enhanced GraphQL Support

The 2022.1 release introduced a GraphQL Client that was limited to a literal input mode into which you could input the text of a predefined GraphQL query. With this release, support for GraphQL has been greatly expanded, including:

  • A new GraphQL Message Responder in Virtualize enables the creation of virtual assets that can parse and understand GraphQL. Virtual assets can be created by hand or from recorded GraphQL traffic. See GraphQL Message Responder for more information.

  • The GraphQL Client tool now contains a Form GraphQL mode that allows you to view, edit, and parameterize GraphQL queries in an easy customized input form. The Form GraphQL mode can be constrained to the fields defined in a GraphQL Schema Definition Language (SDL) document or unconstrained for adhoc editing. See Form GraphQL for more information.

Inline Expressions for Extracting Request Values for Use in Virtual Asset Responses

Virtualize users can extract request values to populate responses by using inline expressions. Inline expressions allow you to explicitly define parameterization of response payloads using extracted values from requests. Instead of using separate data bank tools to extract request values, you can now define from where to extract values directly in the response payload, simplifying both creation and maintenance of the virtual assets since the configuration of the extractions appears directly where the extracted values are used. See Extracting Request Values to Populate Responses in Virtualize for more information.

Inline expressions also include the ability to calculate and return dates and times using specific parameters and formatting, such as adding a time interval to a date retrieved from a request. Inline expressions simplify the configuration and maintenance of passing data from requests to responses and configuring date values within virtual assets. A new Date Time format has been added to allow you to specify formats that should be used to determine whether a string value represents a date/time and, if so, how to parse it when generating inline expressions for message responders. See the "Date Time Format" preference in Additional Preference Settings  for more information.

CRUD Support for SQL Databases in Virtualize

New support has been added for CRUD workflows and data source correlations in responders using SQL databasesSee "Configuring a Database Correlation Data Source" under Adding a Data Source at the Suite, Project, or Global Level for more information.

SSL Connection to Data Repository

SOAtest, Virtualize, and CTP users can now configure their remote data repository servers to connect over SSL. See Installing a Remote Data Repository Server for more information.

Enhanced Documentation for Docker and Kubernetes

Support for deploying SOAtest, Virtualize, and CTP in Docker and Kubernetes has been greatly expanded. See Deploying in Docker and Kubernetes for more information and sample configuration files.

Marketplace Extensions

Parasoft continues to offer additional capabilities through the online Marketplace to enable customers to extend the tool for specific use cases and protocols. In this release:


  • gRPC Transport: The new gRPC Transport Extension adds support for the Google Remote Procedure Call (gRPC) transport to applicable messaging client tools in SOAtest. This enables you to take full advantage of SOAtest's rich interface when configuring, sending, and validating messages sent over gRPC. Unary, client-streaming, server-streaming, and bi-directional calls are supported. In addition, testers of gRPC APIs are able to configure TLS encryption and client certificate authentication to support testing with secure gRPC services. See gRPC Transport for more information.
  • HTTP/2 Transport: The HTTP/2 Transport Extension has been updated to support Java 11 which is required for use with SOAtest 2022.1. See HTTP/2 Transport Extension 1.1 for more information.
  • MongoDB Tool: Formerly known as the MongoDB Query Tool, the enhanced and renamed MongoDB Tool has been updated to include full Create, Read, Update, and Delete (CRUD) functionality, where previously it only supported select (Read) operations.. See MongoDB Tool 1.3 for more information.


  • Async Tool: The new Async Tool enables asynchronous execution of chained outputs after a configured delay. This makes it easy to execute asynchronous actions that happen after a response has been sent. For example, after an HTTP 200 OK response is sent, a chained tool can be used to send an additional message to a topic or queue.  

  • gRPC Listener: The new gRPC Listener Extension adds gRPC support so that Virtualize assets can respond synchronously to unary calls and asynchronously to client-streaming, server-streaming and bi-directional calls. This is necessary in order to virtualize the services of a gRPC server. See gRPC Listener for more information.
  • PCAP Parser: The new PCAP Parser reads packet capture (PCAP) files created using the Wireshark network protocol analysis tool and uses them to create traffic files that can used in Parasoft virtual assets or test scenarios. See PCAP Parser for more information.
  • RabbitMQ Listener: The RabbitMQ Listener plugin has been enhanced to support listening for messages on an exchangeSee Rabbit MQ Message Listener 1.2 for more information.

Additional Updates

  • TFS SDK libraries are now no longer distributed as part of Parasoft SOAtest and Virtualize. If you want to enable TFS source control support, you will need to install TFS SDK from the vendor.
  • Settings can be imported into the GUI from the command line. 

  • The default class name used by the MySQL database data source type has been changed from to com.mysql.cj.jdbc.Driver. Also, using the MySQL database data source type now requires the MySQL driver to be version 6.0 or higher.
  • OIDC authentication with OKTA is now supported.

  • Support for HP ALM and HP Quality Center has ended.
  • You can now append an equal sign (=) to REST client query parameters with empty values.
  • Support added for users who want to set up the data repository server using their own installation of MongoDB. An init script is provided for automating deployment of a remote data repository server. See Installing a Remote Data Repository Server for more information.
  • Virtualize message proxies using the HTTP forward proxy type can now be accessed from mobile apps running on IOS systems. To enable support, a new version of the Parasoft root certificate authority must be re-installed. See HTTP Forward Proxy Configuration for more information about HTTP Forward proxies. 

Resolved PRs and FRs



Unable to configure license for SOAvirt.war using CTP


Job Not Running and Immediately SKIPPED


Ensure a malformed JDBC connection URL causes the correct error message


Allow attaching HTML Cleanup tool to REST Client response traffic


Test Execution for Large Diff Continues After Stating 'Finished'
SOA-15228Traffic Viewer Editor is broken for long lines of text


Rest clients cannot pull data from data source column configured through search and replace
SOA-15578Smart TST generation hangs


Unable to configure kerberos security settings on war deployment


Provide a way to turn off hit statistics reporting per data source row


Multiple Response Script Condition Always Resolves Datasource getValue to First Row


Save Event Log History After Stopping Virtual Asset Monitoring


Generated Data Repo DS Reverting Location Changes When DS Moved
VIRT-2974Secure Communication of Data Between Data Repository And Virtualize
  • No labels