...

1. If not already running, start the SOAtest Web Proxy. See Starting the Web Proxy.
2. Navigate to the web application you want to generate tests from and click the Parasoft icon.

3. Enable the API Traffic for Parasoft SOAtest option and click Start Recording. The application type setting does not affect API traffic recording.
   Image Added

   You can record UI actions and API traffic simultaneously by enabling both API Traffic for Parasoft SOAtest and UI Actions for Parasoft Selenic.

   The application type setting does not impact API traffic recording. 
   Image Removed

   Note

   When you start recording, a message will appear at the top of your browser window informing you that Parasoft recording has started debugging the browser. Do not cancel this process. Navigating to a non-website page in the browser (for example, by clicking Back in the browser and returning to a blank starting page) will cancel traffic recording. Additionally, in Chrome v88+, if you close the debugger on another tab while recording, it will disconnect the debugger in all Chrome tabs, including the one you are currently recording, causing Parasoft Recorder to stop receiving traffic. This is a known bug in Chrome. See https://bugs.chromium.org/p/chromium/issues/detail?id=1170381.

4. Perform your test scenario.
5. When finished, click the logo and choose Stop Recording.
6. If you configured Parasoft Recorder to capture UI actions while exercising your API test scenario, you will be prompted to save them first. See Recording UI Actions. 
7. 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. 
   
8. Click Create Test Asset when ready or Discard Recording to exit the test creation window without generating the test file.
9. When the Parasoft Recorder finishes processing the recorded traffic, you will be prompted to view the test in the CTP API Testing module. SOAtest will process the traffic using internal heuristics, as well as any matching rules in the smart test templates (.stt), to generate the test. Refer to Training the Smart API Test Generator for additional information.
    

10. The test will appear under the TestAssets/users/<USERNAME> directory, where the /users/<USERNAME> sub-directory is created based on your CTP username.
    
    You can also view the test in the SOAtest desktop Test Case Explorer.
     
    If you are using the Parasoft Recorder with a local instance of SOAtest, your tests will appear in the TestAssets/users/anonymous directory.

...

1. Open a command prompt and run regedit. The registry editor opens.
2. Locate the HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER > Software > Policies > Google > Chrome folder.
3. Delete the ProxyMode key and reboot your machine.
4. Check the registry to make sure the key was not regenerated.

Recorded File is Empty/Missing Data

When you start recording, a message will appear at the top of your browser window informing you that Parasoft recording has started debugging the browser. Canceling this process disrupts the recording.

Additionally, in Chrome v88+, if you close the debugger on another tab while recording it will disconnect the debugger in all Chrome tabs, including the one you are currently recording, causing Parasoft Recorder to stop receiving traffic. This is a known bug in Chrome. See https://bugs.chromium.org/p/chromium/issues/detail?id=1170381.

Recording UI Actions

Anchor
Recording UI Actions Recording UI Actions

1. Navigate to the web application you want to generate tests from and click the Parasoft icon.
2. Enable the UI Actions for Parasoft Selenic option and choose either General , or Salesforce  or Guidewire for the application type, or choose General if your application is not a Salesforce or Guidewire application; specifying the application type  (specifying Salesforce optimizes the locator strategy for the specific application. it).  
   Image Added
   You can also record UI actions and API traffic simultaneously by enabling both UI Actions for Parasoft Selenic and  and API Traffic for Parasoft SOAtest.  Image Removed
3. Click Start Recording and perform your test scenario.
4. When finished, click the logo and choose Stop Recording.
5. Specify information about the actions your captured when prompted. By default, the application domain and a time stamp indicating when recording began are used for the test name. Descriptions help other users understand the user experience the test is intended to verify. You can also associate tests with artifacts in your requirements and/or defect tracking system. All of the test information will be added as Javadoc comment when the file is used to generate a Selenium test in Selenic. 
   
6. Click Continue and save the file. 
7. If you configured Parasoft Recorder to API traffic while performing your UI tests, you will be prompted to save the API tests after saving the UI actions. See Recording API Traffic. 

...

1. Start a UI test session and click the Parasoft icon to open the Parasoft Recorder actions.
2. Click Assert Text to enter assertion mode.
   Image RemovedImage Added
3. The pointer will change into crosshairs and elements that you hover the crosshairs over will be outlined.
   
4. Click on the element to capture the assertion.
5. Click Confirm in the Assert Text dialog to accept the asserted value. You can also make modifications to the text in the Value field. The locator selected for the assertion appears in the Locator field. You can also click Cancel to exit assertion mode without asserting the text.
    
6. Complete your test session and download the recording as described in Recording UI Actions.

...