eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Summary
This page describes the steps to set up a load test with [for this example] five user accounts.

1. Modify Original Script
   Begin with your original script, which records and plays using a specific username and password. To parameterize this script you will be changing the username to $NAME and the actual password to $PASS.

   Later, during the eValid load test run, instances of these parameters in the functional test script (shown in bold for clarity) will be filled in with values assigned to them in the LoadTest script file (shown in bold for clarity), as illustrated below.

   Functional Test Script: login.evs

   # Recording by eValid(TM) V9 # Recording made on: Microsoft Windows 2000 ProjectID "Sample" GroupID "Group" TestID "Login" LogID "AUTO" ScreenSize 1280 1024 FontSize 2 DeleteCache DeleteCookies InitLink "http://www.MYSITE.com/index.html" Wait 19528 ElementClick 0 208 "" "» Login to MYSITE" "" Wait 8112 # Original recorded command is here. The parameterized command is below it. # InputValue 0 222 "TEXT" "txtUserName" "tech1" "" "" InputValue 0 222 "TEXT" "txtUserName" "$NAME" "" "" Wait 5258 # Original recorded command is here. The parameterized command is below it. # InputValue 0 226 "TEXT" "txtPassword" "grants" "" "" InputValue 0 226 "TEXT" "txtPassword" "$PASS" "" "" Wait 170 SubmitClick 0 229 "" "LOGIN" "" NAV Wait 12345 ...rest of script... # End of script.

   In the eValid singleton functional test script above:

   • The test starts by navigating to www.MYSITE.com.
   • Two recorded lines are show as comments because they are the prototype for the parametric command immediately below them.
   • The txtUserName field is fed a value from the run-time value of $NAME.
   • The txtPassword field is fed a value from the run-time value of $PASS.
   • After the login is complete (the SubmitClick command finishes) the script waits 12345 msec (12.345 sec) before continuing to the rest of its work.

2. Load Test Script
   You can use the scenario editor and/or a text editor to create the 5-user eValid LoadTest script. Note that the values are passed from the LoadTest_5.evl file to the login.evs files on a one by one basis via the lines in the LoadTest script.

   LoadTest Script: LoadTest_5.evl

   # eValid(TM) V9 # (c) Copyright 2012 by Software Research, Inc. # LoadTest Scenario created on: Microsoft Windows 2000 Service Pack 3 ProjectID "Illustrations" GroupID "Group" TestID "LoadTest_5" LogID "AUTO" Serve FULL LoadType FULL _eValid "login.evs" "" 8 "$NAME=username-1 $PASS=password-1" "-pm 1.0" 1 Wait 1000 _eValid "login.evs" "" 8 "$NAME=username-2 $PASS=password-2" "-pm 1.0" 1 Wait 1000 _eValid "login.evs" "" 8 "$NAME=username-3 $PASS=password-3" "-pm 1.0" 1 Wait 1000 _eValid "login.evs" "" 8 "$NAME=username-4 $PASS=password-4" "-pm 1.0" 1 Wait 1000 _eValid "login.evs" "" 8 "$NAME=username-5 $PASS=password-5" "-pm 1.0" 1 Wait 1000 # End of script...

   In the above LoadTest script:

   • There are 5 lines so there are five eValid sub-browsers running.
   • There are 5 separate users signed in, using 5 separate passwords, shown in bold above.
   • Each on runs a total of eight (8) times. Successive eValid runs in each playback track are launched automatically.
   • There is a 1000 msec (1.0 sec) delay between launch of each of the launches to assure that the five simulated users are behaving in a realistic way.
   • The playback multiplier, as specified in the area for command line switches, -pm 1.0 is set to 1.0 for each eValid sub-browser. This corresponds to "real time" [what was recorded].

3. Run LoadTest
   Make sure the LoadTest_5.evl is the script loaded into eValid, then press Play to run the LoadTest scenario.