Working with Synthetic external script test profiles
This section covers the following topics:
Preparing a script for an external script test
Create a script containing the external test and store it in any directory for easy access. Use any scripting language that is supported on the test engine machine on which the script will be deployed, including Visual Basic, Python, Perl, and JavaScript.
Examples of Selenium Tests are located on NetIM core in the following directory:
<install_dir>/input/SynTestScripts
The script must return zero to be considered a success. The test engine interprets a non-zero exit code as a failure.
Using the wizard for an external script test
To create, clone, edit, or delete a Synthetic external script test profile
1. Log in to the UI as a user with administrative privilege.
2. Choose Configure > All Settings > Monitor: Synthetic Testing.
3. On the Choose Action page, select a radio button to specify whether you will Create, Clone, Edit, or Delete a Synthetic Test Profile.
– If you are creating a Profile, click Next.
– If you are cloning or editing a Profile, highlight the name of an existing profile in the list below, and click Next.
– If you are deleting a Profile, highlight the name of an existing profile in the list below, click Next, and then typically click Finish.
4. On the Test Details page, check Active. In the Name field, enter a unique name for this Profile. In the Test Type drop-down, pick External Script. In the Test Frequency field, set how often this test will run, or accept the default of 300 seconds. Set Timeout to the number of seconds that this test must wait for a response before giving up.
If this test is associated with the performance of one or more applications, enter the Application name(s) here. Also set the name of a Device under test, if applicable. Device can also be the name of a region, business group, or other designator. These properties are passed to downstream Riverbed products for identifying and organizing Synthetic Test results.
5. Click Next.
6. On the Test Configuration page, enter the full path to the script file or browse to it.
Then enter the Command that should run the script as you would if you were at the command line on a test engine machine:
cscript <scriptname> “Riverbed Test Engine” %URI%
%URI% will be replaced by the URIs (if any) that you specify on the Test Targets page.
Optionally, enter the Working Directory from which the script must be run.
Optionally, enter as many Environment Variables as the script requires.
7. Click Next.
8. On the Test Sources page, select one or more test engines from which this test should be run, and click Next.
9. On the Test Targets page, enter the URL or IP address of one or more devices or applications to be tested, and then click Next. These URIs are later substituted into the %URI% variable (if any) that you entered in the Test Configuration page.
10. On the Summary page, verify all settings. Click Previous to go back and modify, or click Finish to save the profile.