...
- SOAtest Traffic Recorder: The traffic recorder is an extension for the Chrome browser. It is installed on the local machine and provides an interface for configuring your connection to SOAtest, as well as starting/stopping recording.
- Parasoft SOAtest Web Proxy: The proxy is installed on the local machine, processes traffic, and creates a .tst file in SOAtest.
- Parasoft Root Certificate Authority: The CA enables HTTPS traffic to be recorded.
...
- Advanced Test Generation Desktop: Enables you to create assets from the web proxy on the same machine where SOAtest is installed. Connections Connections from remote machines are not allowed.
- Advanced Test Generation 5 Users: Up to five users can create assets from any machine that can connect to the SOAtest server.
- Advanced Test Generation 25 Users: Up to 25 users can create assets from any machine that can connect to the SOAtest server.
- Advanced Test Generation 100 Users: Up to 100 users can create assets from any machine that can connect to the SOAtest server.
...
Run the parasoft_soatest_smart_api_test_generator_<version>_win32.exe file for installation on Windows . Follow the wizard to complete the installation. See Manual Installation if you are on Mac OS or if experience issues using the installer. or the parasoft_soatest_smart_api_test_generator_<version>_macos.dmg for installation on Mac OS. If Mac OS can not run the .dmg for security reasons, right-click the file and choose Open With> Installer.
Follow the wizard for your OS to complete the installation. See Manual Installation if you experience issues using the installer.
During Windows installation, you During Windows installation, you will be prompted to install the Parasoft SOAtest Web Proxy as a Windows service. This enables you to start and stop the proxy using the services console under the Windows Control Panel, as well as use the SOAtest Web Proxy console in the Windows Start menu (see Starting the Web Proxy). You can also manually start the proxy by running the executable JAR file (see Manually Starting the Web Proxy).
...
The installer will prompt you to install the Parasoft Root Certificate Authority if it is not detected. The CA is required to record traffic over HTTPS. The CA is normally installed along with the SOAtest/Virtualize desktop application. You can also add the CA manually (see Installing the Parasoft Root Certificate Authority).
After the installer finishesDuring installation on Mac OS, you can enable the web proxy to automatically start whenever you log into the machine.
You can enable or disable automatic start up for the web proxy after installation by in the System Preferences> Users & Groups> Login Items settings.
| Info | ||
|---|---|---|
| ||
You can click the padlock icon to view the Apple developer ID certificate authority (CA). The certificate identifies Parasoft as a trusted source of software for Apple devices.
|
After the installer finishes, you will be prompted to enable the extension will be prompted to enable the extension when you launch Chrome.
| Warning | ||
|---|---|---|
| ||
This action will uninstall and blacklist the extension. As a result, you will not be able to install or update the extension automatically. |
...
The installer will prompt you to start the Parasoft SOAtest Web Proxy when the installation completes. If you choose to finish the installation without starting the proxy, see Starting the Web Proxy for instructions on starting the proxy on demand. If the proxy is running, see Using the Browser Extension for next steps. The SOAtest server must be running before you can use the extensionmust be running before you can use the extension.
Uninstalling the SOAtest Smart API Test Generator
Use the regular Windows program uninstaller in the control panel to fully uninstall the tool. The Mac OS installer ships with an Uninstall SOAtest Smart API Test Generator utility that you can run if you wish to completely uninstall the tool. The Mac OS utility will be located in your Applications/Parasoft folder.
Manual Installation
The following instructions describe how to manually install the SOAtest Smart API Test Generator components if you are unable to use the Windows installer.
...
The Parasoft SOAtest Web Proxy and SOAtest server must be running before you can use the extension (see Starting the Web Proxy). If the SOAtest server is running and the default configuration is used to start the proxy, you will be able to start using the extension to record traffic. See Using the Browser Extension if these components are running). You will also need to configure connections to the Parasoft SOAtest Web Proxy and SOAtest server once the browser extension is installed.
...
Open the console and click Stop to shutdown the proxy.
On Mac OS, the web proxy will be located in your Applications/Parasoft folder.
Manually Starting the Web Proxy
...
- Navigate to the web application you want to generate tests from and click the Parasoft icon.
- Choose Start Recording and begin your test scenario.
- When finished, click the logo and choose Stop Recording.
- Specify information for the test when prompted. Test names must be unique. You can also associate tests with artifacts in your requirements and/or defect tracking system.
- Click Create Test Asset when ready or Discard Recording to exit the test creation window without saving generating the test file.
When the SOAtest Traffic Recorder finishes processing the recorded traffic, you can review the test file in the TestAssets project of the SOAtest Test Case Explorer or in the API Testing module in CTP. Parasoft .tst files will appear under the TestAssets/users/<username> directory, where the /users/<username> sub-directory is created based on your CTP username.
If you are using the Smart API Test Generator with a local instance of SOAtest, your tests will appear in the TestAssets/users/anonymous directory.
...
You can configure the web proxy by specifying system properties in the Manage Web Proxy console or from the command line when executing the .jar file. You can specify the following properties:
| Scroll Table Layout | ||
|---|---|---|
|
...
| disableDiffCreation | Enables/disables diff creation. See Diff for additional information. Default is |
|---|---|
| disableDataBankCreation | Enables/disables data bank creation. See Data Exchange Tools for additional information. Default is |
| disableEnvironmentCreation | Enables/disables the creation of an environment and environment variables. Default is false. |
| includeContentTypes | Defines a comma-separated list of content types to include during traffic processing. Default is application/json. |
| excludeContentTypes | Defines a comma-separated list of content types to exclude during traffic processing. Default is empty. |
| disableDiffParameterization | Enables/disabled disables diff parameterization. Parameterization enables you to use data banked values in the diff. If diff parameterization is disabled (setting this property to true), only static values will be available. Default is false. |
| diffToolIgnoreNames.<number> | Defines a regex matching element names that should be ignored when creating a diffs. Default is You can specify additional name patterns by adding properties and appending them with For example:
|
| diffToolIgnoreValues.<number> | Defines a regex matching values that should be ignored when creating diffs. Default is to ignore timestamps:
You can specify additional value patterns by adding properties and appending them with For example:
|
...