In this section:
Parasoft Recorder is an add-on component for recording API calls and/or user actions during interactions with a web application. You can convert the API traffic into extendable API tests that can be executed from CTP or the SOAtest desktop. Recorded user actions can be downloaded and converted into Selenium tests with Parasoft Selenic (see the Parasoft Selenic documentation for more information). Parasoft Recorder includes the following components:
This section describes the requirements for Parasoft Recorder components and associated functionality.
You can freely download and install Parasoft Recorder, but a valid license is required to use the API test generation features in SOAtest or the Selenium test creation and management features in Parasoft Selenic. Contact your Parasoft representative for complete licensing information.
Advanced Test Generation license feature in SOAtest is required to record traffic and generate tests. The following license options are available:
Refer to the Parasoft Selenic documentation for details about licensing.
Run the installation file appropriate for your OS and follow the wizard for your OS to complete the installation:
See Manual Installation if you experience issues using the installer.
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 Windows and Mac installer will also prompt you to install Parasoft Recorder from the Google Chrome store (Windows shown). See Manual Installation if access to the Google Chrome store is prohibited or if you experience issues using the installer.
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).
During 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.
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 when you launch Chrome.
This action will uninstall and blacklist the extension. As a result, you will not be able to install or update the extension automatically. You will need to uninstall and reinstall Chrome in order to restore the automatic installation of this extension. |
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 extension.
Use the regular Windows program uninstaller in the control panel to fully uninstall the tool. The Mac OS installer ships with an Uninstall Parasoft Recorder 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.
The following instructions describe how to manually install Parasoft Recorder components if you are unable to use the installer. Please note that Java is not included when following the manual installation steps; if Java is not installed on your device, you will need to install it before using Parasoft Recorder.
<PARASOFT-RECORDER-INSTALL-DIR>/chrome-extension directory to install the extension. The tool will be available in the browser bar.
The Parasoft SOAtest Web Proxy and SOAtest server must be running before you can record API traffic (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 Parasoft Recorder Usage 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.
The Parasoft Root Certificate Authority must be installed as a trusted certificate to enable recording of HTTPS traffic. If the certificate authority is not installed, the browser will not consider the connection secure and may refuse to allow the connection.
The Parasoft Root Certificate Authority is normally installed automatically by both the SOAtest Windows installer and the Parasoft Recorder installer. You can also run soatestcli with the -installcertificate option to manually install it if necessary. For example:
soatestcli -installcertificate
If SOAtest is not installed on the local machine, you can manually add the certificate to Chrome:
This procedure assumes that you are using Android Studio/Android Sdk and that you have created an Android Virtual Device (AVD) on a non-production build. Additionally:
Because CA certificates in Android are stored by their hashed name with the file extension .0, you will need to copy and rename the Parasoft certificate. To do that, open a command prompt and navigate to <VIRT_INSTALL_DIR>/plugins/com.parasoft.ptest.libs.web_<version>/root/lib then run the following command:
hashed_name=`openssl x509 -inform PEM -subject_hash_old -in parasoft.cer | head -1` && cp parasoft.cer $hashed_name.0 |
You need to place the hash.0 version of the CA certificate in the system certificate store in the Android filesystem, found at /system/etc/security/cacerts/. The /system partition is mounted as read-only by default, so you need to modify permissions to allow write access. Exactly how you do that depends on what version of the emulator you are using.
Starting with API Level 29, you can't mount the "/" partition with read-write permissions normally. Google has provided a workaround (see https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md for more information), but some users find that this results in their emulator getting stuck in a boot loop. If that's the case, you can try the workaround detailed below:
You have to start the emulator using the |
Start your AVD:
emulator -avd <AVD_NAME> -writable-system |
emulator -list-avds to pull up a list of all your AVDs.Restart adb as root:
adb root |
Disable secure boot verification:
adb shell avbctl disable-verification |
Reboot the device and restart adb as root:
adb reboot adb root |
Remount the partitions as read-write:
adb remount |
If adb indicates that you need to reboot, run adb reboot and adb remount again.
Push the hash.0 version of the certificate:
adb push <PATH_TO_CERT> /system/etc/security/cacerts |
Set certificate permissions:
adb shell chmod 664 /system/etc/security/cacerts/<NAME_OF_HASH.0_CERT> |
Reboot the device again:
adb reboot |
You have to start the emulator using the |
Start your AVD:
emulator -avd <AVD_NAME> -writable-system |
emulator -list-avds to pull up a list of all your AVDs.Restart adb as root:
adb root |
Remount the partitions as read-write:
adb remount |
If adb indicates that you need to reboot, run adb reboot and adb remount again.
Push the hash.0 version of the certificate:
adb push <PATH_TO_CERT> /system/etc/security/cacerts |
Set certificate permissions:
adb shell chmod 664 /system/etc/security/cacerts/<NAME_OF_HASH.0_CERT> |
Reboot the device again:
adb reboot |
<VIRT_INSTALL_DIR>/plugins/com.parasoft.ptest.libs.web_<version>/root/lib.On recent iOS versions, you also need to enable full trust for the parasoft root certificate. To do so:
If you installed the Parasoft Web Proxy as a Windows service, you can use the SOAtest Web Proxy console to start and stop the proxy.
The web proxy API will be started on port 40090 by default. The proxy port used for recording API traffic will be assigned by scanning for open ports starting with port 40443. You can configure port numbers and other options when starting the proxy in the web proxy console. See Advanced Parasoft Recorder Configuration for additional information.
Open the console and click Stop to shut down the proxy.
On Mac OS, the web proxy will be located in your Applications/Parasoft folder.
The web proxy is a JAR file that you can run with the java command:
%INSTALLDIR%/jre/bin/java -jar com.parasoft.traffic.proxy.jar
The Parasoft Recorder installer for Windows or Mac includes an instance of Java, while the Parasoft Recorder zip file does not. If you manually install Parasoft Recorder using the zip file, you will need to either manually install Java or use an instance that is already installed on your system. Java 11 or later is supported. |
The web proxy API will be started on port 40090 by default. The proxy port used for recording will be assigned by scanning for open ports starting with port 40443. You can specify system properties to configure port numbers and other options when starting the proxy. See Advanced Parasoft Recorder Configuration for additional information.
Execute the JAR file with the --version argument (-v) to print the version number on the command line. Example:
%INSTALLDIR%/jre/bin/java -jar com.parasoft.traffic.proxy.jar --version
The version number can be helpful if you need to troubleshoot issues with Parasoft Recorder.
Executing the JAR with this argument only enables the proxy to report the version and does not start the proxy.
See Advanced Parasoft Recorder Configuration for additional information.
chrome://extensions homepage.