In this section:

Configuring Authentication Settings

When you first record a scenario, the authentication information specified in the Security Preferences are used first. If you want to record a scenario on a web application that requires Kerberos authentication, you need to specify the Kerberos authentication credentials in the Security Preferences before recording the scenario. For details on how to do this, see Configuring Kerberos Authentication for Tools for additional information.

1. Right-click your project and choose Add New > Test (.tst) File...You can also click Add Recorded Scenarios on the tool bar.
   

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: Enable 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.

     Selenium WebDriver Note

     If you choose to record starting from a referenced scenario that is set to play back with WebDriver in Safari, the Browser option will automatically be set to Chrome by default, but you can change the default selection.

   • Record web scenario: Choose this option to record a new scenario.

5.  Complete the next Record Web Scenario wizard page and click Next.

   

   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 (for example, mymachine.parasoft.com) or the IP address (for example, 10.10.11.11). If you enabled Record starting from a referenced scenario, specify the name of the test suite containing the reference. You can enable Persist as relative path, which configures SOAtest to generate artifacts relative to the reference suite. To reference tests in another project, use the ${project_loc} variable.
   Chrome Path	The Chrome path may be set automatically (for example, from system settings or browser playback preferences). Change if necessary.
   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.

6. (Optional) Enable Add url variable to your existing environment and specify a variable name and prefix in the fields provided. If enabled, this option automatically adds a variable for the URL to the scenario. Environment variables in Parasoft can be used to set conditions around scenarios that may change depending on the testing stage. For functional tests, environment variables are used for the URL of the first navigation test. For asynchronous request tests, they are used in the endpoint and the HTTP header "Referrer" of each Messaging Client that is generated for each asynchronous request.

7. Click Finish and 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. Interact with the application in the browser. 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 full page loads can be detected. 

   Recording Clicks in a Text Input Field (for example, in a Calendar Widget)?

   See Recording Clicks for Calendar Widgets for tips.

   When beforeUnload dialogs open during recording, SOAtest will always record "Accept Script Dialog." However, if you want the test to cancel the dialog instead, then you need to modify the recorded test case to use "Dismiss Script Dialog" instead.

   Completing Forms

   To complete forms, enter the values directly into the GUI controls as if you were actually navigating the site. For instance, type in your username and password, select radio buttons, check or clear check boxes, and so on. 

   • Password recall and auto-completion are not supported during recording.
   • Google Toolbar's Auto Fill feature is not supported.
   • A "type" action may not be recorded if you type the beginning of a term into a field, but then click on a suggestion from a drop down.

9. Click Stop Recording when you are finished recording.  A new Test Suite will appear in the Test Case Explorer.This new Test Suite will contain different tests depending on your selections from the wizard’s Test Type field. For more information, see the following subsections.

Additional Information

• Extending existing scenarios: See Extending an Existing Web Scenario for details on how to extend existing web scenarios with additional steps.
  • Recording Clicks in a Text Input Field (for example, in a Calendar Widget): See Recording Clicks for Calendar Widgets.
  • Completing Forms: To complete forms, enter the values directly into the GUI controls as if you were actually navigating the site. For instance, type in your username and password, select radio buttons, check or clear check boxes, and so on. As you record sessions, please note:
    
    • Google Toolbar's Auto Fill feature is not supported.
    • A "type" action may not be recorded if you type the beginning of a term into a field, but then click on a suggestion from a dropdown.
  • File inputs on Chrome: SOAtest does not currently support filling out file inputs in web applications in Chrome.