Visit https://docs.parasoft.com/display/SVC20202/Release+Notes for the latest release information.
This is a major release that includes several changes that affect legacy functionality. The following changes enable us to evolve and adapt to new and emerging technologies and application development strategies:
Release date: October 26, 2020
Updated Smart API Test Creation Configurations
We've made the following improvement to the smart API test generation workflow.
Application-specific Smart API Test Creation Properties Files
The smart API test generator can now use Salesforce- or Guidewire-specific configurations to create tests from API traffic captured with Parasoft Recorder. SOAtest ships with additional tst_creation.properties files that are automatically added to the TestAssets/test_templates directory in the workspace. The configurations are used when SOAtest detects that the Salesforce or Guidewire application type has been selected during recording.
Updated Wizard for Generating Smart API Tests
The Generate Smart API Tests wizard now allows you to specify the test creation file to use when generating tests. By default, the wizard prompts you to use the configuration file for general, Salesforce, and Guidewire applications shipped with SOAtest, but you can create multiple instances so that you can customize test generation for a variety of cases.Refer to Creating Smart API Tests from Traffic for additional information.
Versioning for Smart API Test Creation Properties
The tst_creation.properties file used to configure smart API tests is now automatically prepended with new features available in the latest release. Previously, the existing tst_creation.properties file was preserved in order to maintain custom configurations. In this update, custom configurations are still preserved, but any new parameters are added to the file with default configurations.
Refer to Configuring Smart API Test Generation for details.
Parasoft Recorder no longer ships with the tst_creation.properties file. Instead, the recorder ships with a tst_creation.properties.example file, which is not used by default.
Refer to the Parasoft Recorder documentation for details.
All test creation configuration files will now be generated in the <WORKSPACE>/TestAssets/test_templates directory instead of the <WORKSPACE>/TestAssets directory. If you have an existing tst_creation.properties file in the TestAssets directory, it will be moved to the new location when the workspaces is restarted.
New Task Suppression Format
Suppressions for static analysis violations and failed test case steps are now added to a parasoft.suppress file, which can be stored in source control along with your test files. As a result of this change, the Suppressions View has been deprecated and will only show suppressions created in older versions of SOAtest as read-only.
End of Life for Legacy Functionality
The following functionality, tools, and integrations have been removed in this update.
Legacy Browser Testing Engine
The Parasoft legacy browser testing engine is no longer supported and has been removed.
SOAtest will use the Selenium WebDriver to play back your tests, but you may be required to manually update tests that were configured to playback with the Parasoft legacy engine. See About the Selenium WebDriver Engine for additional information.
SOAtest Legacy Stubs Server
The SOAtest legacy stubs server has been removed. Existing stubs under the stubs project folder will no longer be deployed. Stubs will automatically be converted to virtual assets when the Virtualize license is applied.
If Virtualize detects the Stubs project when starting on a workspace that contains SOAtest stubs, it will automatically copy the files to the VirtualAssets project. Stub .tst files will be changed to .pva files and deployments based on the existing stubs.xml file in the Stubs project will be created.
You can initiate the migration process by shutting down SOAtest and Virtualize and deleting the VirtualAssets project. The automatic migration process will be triggered when the product starts up.
Built-in ISO 8583 Functionality
Native support for ISO 8583 has been removed. To replace this functionality, you can download and deploy the Parasoft ISO 8583 Extensions. Contact your Parasoft representative for details.
Existing ISO 8583 Message Clients and Responders will no longer be available or function after upgrading, so you should install the Parasoft ISO 8583 Extensions and migrate existing ISO 8583 configurations to the extension prior to upgrading.
AmberPoint Test Creation
SOAtest no longer creates tests from AmberPoint SOAP message files. Existing tests created from AmberPoint files will still function.
Asynchronous Request Tests
You can no longer configure SOAtest to generate asynchronous request tests when creating tests from web recordings.
Auto-generated Response Stubs
You can no longer configure SOAtest or Virtualize to automatically create response stubs when creating tests from web recordings.
SOAtest no longer generates tests based on services declared in a BEA AquaLogic Enterprise Repository. Existing tests created from BEA repositories will still function, but compliance policy and functional test results will no longer be reported to the registry.
CentraSite Active SOA Registry
SOAtest no longer generates tests based on services published to CentraSite Active SOA registries. Existing tests created from using the CentraSite integration will still function, but compliance policy and functional test results will no longer be reported to the registry.
The integration with Parasoft Jtest 9.x has been removed, which affects the following functionality:
JUnit Test Creation
XML in SOAtest and Virtualize Server REST API
The application/xml media type is no longer supported when communicating with any version of the REST API.
Removed Support for Source Control Management Systems
Support for the following SCMs is removed:
Resolved PRs and FRs