In this section:
| Table of Contents | ||
|---|---|---|
|
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 in Virtualizefor Tools for additional information.
Right-click your project and choose Add New> New > Provisioning Action (.pvn) File...
- Specify a name and the directory for the file in the wizard and click Next.
Choose Web> Record web scenario and click Next. PVNs must be stored in a project named "ProvisioningAssets."
Choose one of the following options to specify a starting point for the web scenario and click Next.
Scroll Table Layout widths 40%,60%- Record starting from a referenced scenario
- : 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
web scenario
: Choose this option to record a new scenario
.
Complete the next Record Web Scenario wizard page and click Next.
Scroll Table Layout widths 30%,70% 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. If you selected Record starting from a referenced scenario, specify the name of the action suite containing the reference. You can enable the Persist as relative path option, which configures Virtualize to generate artifacts relative to the reference suite. To reference actions in another project, use the
${project_loc} variable.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 Virtualize to generate a report that helps you gauge the maintainability of an action suite. - 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 - 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.
Click Finish and the
Click the Finish button. Thedesignated 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.
- 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.
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 Virtualize can detectthat
a page load occurred.full page loads can be detected.
Info title Recording Clicks in a Text Input Field (e.g., in a Calendar Widget)? See Recording Clicks for Calendar Widgets for tips.
Tip-Tip title 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.
- When
Click Stop Recording when you are finished recording,
click Stop Recording. A new
(Optional) Enable the
Add url variable to your existing environment option
.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.
Action Suite will appear in the Virtual Asset Explorer.