1. Right-click your project and choose Add New> 

   Test (.tst) File...

   or

   Provisioning Action (.pvn) File...

   You can also click the Add Recorded Scenarios button in the toolbar.

2. Specify a name and the directory for the file in the wizard and click Next.

3. Choose Web> Record web scenario and click Next. 

   
   

4. Choose one of the following options to specify a starting point for the web scenario and click Next.

   
   

   Record starting from a referenced scenario allows

   Choose this option to start recording a new web scenario that builds on an existing (reusable) web scenario. For example, you can record one scenario that captures the steps to log into your application, and then reference this when creating new scenarios. This way, you don’t need to record the login steps every time that you want to create a new scenario that requires a log in. If the login steps change, you just need to update the one login scenario. All related scenarios will automatically use the updated information.

   Record new web scenario

   Choose this option to record a new scenario from scratch.

5.  Complete the next Record Web Scenario wizard page.

   For SOAtest:

   Test Suite Name Specify the name of the test suite that the scenario should start from Start Recording From / Test Suite Reference Enter the URL of the site where you want to record. To record applications that "live" on the same machine as SOAtest, do not use localhost—instead, use the machine name (e.g., mymachine.parasoft.com) or the IP address (e.g., 10.10.11.11). If you are recording a scenario based on a referenced scenario, specify the name of the test suite containing the reference. Generate Functional Tests Enable this option if you want SOAtest to record user actions on the page, and generate a test suite that will allow you to replay the entire scenario for cross-browser testing. Enable the Auto Generate Response Stubs sub-option if you want SOAtest to automatically generate stub outputs for functional tests that have asynchronous responses. Generate Asynchronous Request Tests If the web site uses the XMLHttpRequest object or hidden IFrame calls to asynchronously request data from a server, enable Auto Generate Asynchronous Request Tests to capture those requests and their responses. SOAtest will also generate and autoconfigure tests to validate these requests. For more information, see Exploring the Asynchronous Test Requests Generated. Browser Choose the browser used to record the scenario. For Chrome, the path may be set automatically (e.g., from system settings or browser playback preferences). Generate Test Maintainability Report Specifies whether you want SOAtest to generate a  report that helps you gauge the maintainability of a test suite. See Creating a Report of Test Suite Maintainability for details.

   For Virtualize:

   Action Suite Name Specify the name of the action suite that the scenario should start from Action Suite Reference / Start Recording From If you are recording a scenario based on a referenced scenario, specify the name of the action suite containing the reference. If you are recording an all new scenario, enter the URL of the site where you want to record. To record applications that "live" on the same machine as SOAtest, do not use localhost—instead, use the machine name (e.g., mymachine.parasoft.com) or the IP address (e.g., 10.10.11.11). Generate Functional Tests Enable this option if you want to record user actions on the page and generate a test suite that will allow you to replay the entire scenario for cross-browser testing. Enable the Auto Generate Response Stubs sub-option if you want to automatically generate stub outputs for functional tests that have asynchronous responses. Browser Choose the browser used to record the scenario. For Chrome, the path may be set automatically (e.g., from system settings or browser playback preferences).

6. Click Next and Complete the Create Environment page (Optional).

   • The controls in this page allow you to specify whether environment variables automatically get added to recorded scenarios.

   • These variables are generated by default. If you do not want these variables generated into the recorded scenarios, disable the Add url variable to your existing environment option.
   • Name specifies the name that will be used for the environment if a new environment is created. (A new environment is created if one does not yet exist for that scenario).
   • Prefix specifies the prefix that will be used on the environment variables that get generated into the environment and that are referenced by the scenarios. The text below the prefix field demonstrates what the environment variable name will look like based on the specified prefix.
7. Click the Finish button. The designated start page will open in the selected browser. If you configured recording to start from a referenced scenario, that scenario will be played back in the browser before you can start recording the new scenario steps.
8. Specify the functionality that you want to capture by interacting with the browser. You can click links, complete and submit forms, use the navigation bar to enter open URLs, access shortcuts, go forward or back, and so on.
    

   • To ensure that recording works properly, wait until each page has fully loaded before performing an action. For example, if you click on a link and this causes a page load, you should wait for the page to finish loading so that 

     SOAtest

     or

     Virtualize

      can detect that a page load occurred.
      

9. When you are finished recording, click Stop Recording. A new 

 will appear in the 

.