Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space FUNCTDEV and version SOAVIRT_9.10.5_CTP_3.1.1

Info
titleConfiguring 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, seeConfiguring Kerberos Authentication in Virtualize.

  1. Right-click your project and choose Add New> Provisioning Action (.pvn) File...

  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. 


    PVNs must be stored in a project named "ProvisioningAssets."

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


    Scroll Table Layout
    widths40%,60%

    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 scenarioChoose this option to record a new scenario from scratch.
  5.  Complete the next Record Web Scenario wizard page.

    Scroll Table Layout
    widths30%,70%

    Action Suite NameSpecify the name of the action suite that the scenario should start from
    Action Suite Reference / Start Recording FromIf 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 TestsEnable 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.
    BrowserChoose 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 Virtualize can detect that a page load occurred.
       

      Info
      titleRecording Clicks in a Text Input Field (e.g., in a Calendar Widget)?

      See Recording Clicks for Calendar Widgets for tips.

      Tip
      titleTip- 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 user name and password, select radio buttons, check or clear check boxes, and so on. 

      As you record sessions, please note:

      • Password recall and auto-completion in Internet Explorer’s Internet Options Advanced settings 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. When you are finished recording, click Stop Recording. A new 

...