You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »



Release date: May 9, 2023

Author Stored for Message Proxies, Virtual Assets, and Test, Responder, and Action Suites

The last user to modify a Test Suite (.tst), Responder Suite (.pva), Action Suite (.pvn), Message Proxy (.pmpdd), or Virtual Asset (.pvadd) is now stored in those artifacts. Users who wish to make full use of this capability should update CTP and all SOAtest and Virtualize servers and desktop installations to 2023.1.

New Responder Mode Driven by Directory of Request and Response Files

Virtualize users can now take advantage of a new responder mode for JSON and Plain XML that makes use of a directory of request-response pairs, making it easier to add new data. Request and response files are automatically paired based on filenames in the directory you specify. HTTP, MQ, JMS, and custom protocols are supported.

Test Impact Analysis

<placeholder>

Application Coverage/Coverage Agent

<placeholder>

Test Configuration Properties Migrated to Settings

Application coverage can now be reported by SOAtest without it being aware of a Jtest or dotTEST installation. The path to Jtest or dotTEST is no longer configured in SOAtest preferences; instead, application coverage settings are now configured in your settings file (see Configuring Settings for more details). The table below shows migration details for this shift.

Old Test Configuration PropertyNew Settings Property
com.parasoft.xtest.execution.api.web.collect_application_coverage application.coverage.enabled
com.parasoft.xtest.execution.api.web.application_coverage_host
com.parasoft.xtest.execution.api.web.application_coverage_port
com.parasoft.xtest.execution.api.web.application_coverage_protocol 
application.coverage.agent.url
com.parasoft.xtest.execution.api.web.application_coverage_user_id application.coverage.user.id
com.parasoft.xtest.execution.api.web.application_coverage_report_as_test_failure Not Applicable, always enabled
com.parasoft.xtest.execution.api.web.application_coverage_upload_to_dtp application.coverage.agent.dtp.publish
com.parasoft.xtest.execution.api.web.application_coverage_static_coverage_file application.coverage.static.file
com.parasoft.xtest.execution.api.web.application_coverage_image_tagsapplication.coverage.images
com.parasoft.xtest.execution.api.web.application_coverage_tia_generate_baseline_report 
com.parasoft.xtest.execution.api.web.application_coverage_tia_report_location 
Not Applicable, replaced with -impactedTests CLI argument
com.parasoft.xtest.execution.api.web.application_coverage_tia_application_location application.coverage.binaries

Breaking Changes

  • Any Test Suite (.tst), Responder Suite (.pva), Action Suite (.pvn), Message Proxy (.pmpdd), or Virtual Asset (.pvadd) created or edited in 2023.1 cannot be opened in older versions of SOAtest or Virtualize. To prevent this issue, upgrade CTP and all SOAtest and Virtualize servers and desktop installations to 2023.1.

Additional Updates

  • Support added for Snap-based browsers in Ubuntu.

  • Team Server has been removed and is no longer supported. If your team configurations, rules, and rule mappings are still stored in DTP Team Server, migrate them to a shared location before upgrading DTP to version 2023.1 or later. See Migrating Team Server Information to a Shared Location for more information.
  • Support for Windows Server 2019 has ended.
  • Free Edition is now limited to 1000 hits per day.
  • soavirt.war now includes a script for encoding passwords. See Licensing the Server and Server Configuration for more information.
  • soavirt.war can now run up to four tests in parallel. Note this update does not apply to the SOAtest and/or Virtualize desktop application, which runs tests consecutively. CTP users will need to upgrade their CTP installations to take advantage of this increased capacity.

  • OIDC support for Google authentication added.
  • Improved look and feel when running in dark theme. Users installing the plug-in for Eclipse should have Eclipse 2022-03 (version 4.23) or later for the best dark theme experience. Affects SOAtest and Virtualize users only.
  • Enhanced XML encoding options in Form XML make it easier to switch between Form XML and Literal views while preserving Unicode characters and XML encoding configuration. See Form XML for more details.
  • CTP users can mark some resources as "private," hiding them from non-administrators who have not been granted access to them. 

  • Desktop users can access the REST API locally even when those license features are not applied, allowing you to test integrations with the REST API and validating workflows locally before deploying completed assets to a remote server.
  • Support for JBoss monitors (used in Load Test) is deprecated and will end in the next release.
  • CTP users can switch message proxy mode between primary and secondary connections.
  • CTP users can create proxies inside of proxy folders.
  • Support for deploying a SOAVirt Server in Kubernetes has been enhanced, including the ability to deploy data repository servers. See Deploying in Docker and Kubernetes for more details.
  • You can configure a Message Responder to bypass any Message Proxy failover settings that have been set up and return the custom return status and payload configured in the Responder instead.
  • New CTP widgets are available for monitoring Hits per Second. 

  • CTP users can configure Tomcat to log user information along with each request and response. 

  • In the Virtualize Server Hit Statistics report available in CTP, you can control whether hit count, peak hits per second, or both (default) are shown on the chart. 

  • You can now create and manage Database Correlation data sources (introduced for Virtualize in 2022.2) from CTP. 

  • You can now connect to a MongoDB server or service that you have set up as a Data Repository using a MonogDB connection string.  
  • You can install a Windows Service for SOAVirt Server. See Installation: Windows for more information.
  • You can connect CTP component instances to application coverage agents as part of the Parasoft Application Coverage solution. After doing so, notifications regarding coverage agent connectivity will be displayed on the environment diagram in CTP. 

  • IBM WebSphere MQ tool can now be configured to keep the connection to the queue manager alive, which allows the use of an MQ browse cursor across subsequent tests. See IBM WebSphere MQ for more information.

Resolved PRs and FRs

IDDescription




























  • No labels