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

Introduction
An eValid LoadTest scenario is a description of how an eValid LoadTest run handles emulating a number of users through use of simultaneous eValid browsers playing selected scripts. The Scenario Editor helps you determine what the eValid LoadTest script is supposed to do -- that is, what kind of user experiment you want to perform. Once you have your plan made -- or edited based on your experience -- the Scenario Editor commits your testing plan into the corresponding eValid LoadTest script (the *.evl script).

Scenario Editor Information Flow

General Description
Use this page to plan your LoadTest scenario. Here is a sample LoadTest Scenario Editor page. Using this form you can specify both the project details and then the details of each individual simulated user. There are three parts to this process:

Editing or Creating Scenarios

• New LoadTest Scenario.
  If you want to start a new scenario click LoadTest > New LoadTest or if you want to open an existing LoadTest file click LoadTest > Open LoadTest.

• Edit Existing LoadTest Scenario.
  To edit an existing loadtest file click Window > LoadTest Scenario Window. This will bring up the LoadTest Scenario Editor page.

General Scenario Setup Information
These selections describe the general nature of the scenario, where the results are stored, and how the logfiles are treated.

• LoadTest File Name.
  This is the name of the underlying eValid LoadTest *.evl file. You can have many different scenarios with details stored in multiple *.evl files.

• Working Folder.
  Here is where all of the project results are kept.

• Project Folder. [ProjectID]
  Here is where the specific project results are kept. This project/group/test structure is the same as for regular functional test scripts, and follows the organization expected by eV.Manager.

• Group Folder. [GroupID]
  Here is where the specific test group results are kept. This project/group/test structure is the same as for regular functional test scripts, and follows the organization expected by eV.Manager.

• LoadTest File. [TestID]
  This is the name of the test (this is used in the event logs) This project/group/test structure is the same as for regular functional test scripts, and follows the organization expected by eV.Manager.

• Log Naming Convention. [LogID]
  This is the specification of how the log files are to be named: DEFAULT or AUTO.

• Launch Interval.
  This is the amount of time to wait, during LoadTest startup, between launching individual eValid browsers.

User Descriptions
Each line of the table describes one simulated user; you can have any number of rows in this table. The number of users simulated is often called the "width" of the scenario.

• Move This Row Up.
  

  CLick on this icon in the scenario edit table to move the row up one position.

• Move This Row Down.
  

  Click on this icon in the scenario edit table to move the row down one position.

• Copy This Row.
  

  Click on this icon in the scenario edit table to make a copy of this row immediately below the current row.

• Delete This Row.
  

  Click on this icon in the scenario edit table to delete the row entirely.

• Script File Name.
  This is the file name to be used in this particular playback.

• User Identification Name.
  This is the identification name for this user class. All users of the same identification name have the total playback times combined in the final LoadTest report. This field is optional, and if left blank eValid will fill in default values.

• Load Type [FULL or TEXT].
  This specifies the type of service to be provided in this eValid instance. FULL implies use of the full images, and TEXT implies use of text only.

  Warning: Serving TEXT may reduce server load by a factor of as much as 10:1; such a reduction in workload may inadvertantly give you a false sense of server capacity (i.e. server capacity will appear larger than it will be when pages are served FULL as they normally are).

• Serve Type [FULL or THIN or LITE]. This specifies the specific eValid browser to use. For FULL or THIN, full fidelity playback engine is used. For LITE, the eVlite low-fidelity playback engine is used. See the eVlite Documentation for complete details.
  

• Repetition Count.
  This states how many times the script is to be played back. The repetition count for a scenario is often called the "depth" of the scenario.

• Parameter Values (Name/Value Pairs).
  These are $NAME=value pairs that are to be substituted into this specific script file.

• Additional Paraameters (Playback Switches).
  These are switch variables that are to be applied to playback of the specified script for this particular user.

• Number of Users (LITE Only).
  This specifies the number of parallel users to employ in the eVlite run. This applies to the script file only if the LoadType is LITE. See the eVlite Documentation for complete details.

Creating Your LoadTest Script
The bottom of the form lets you add additional users, or accept the current contents of the scenario.

• Add New LoadTest Line.
  the values you want by typing in the indicated areas. This adds a blank line to the scenario table.

• Save & Load LoadTest Script.
  Using the contents of the scenario table, creates the appropriate eValid LoadTest *.evl script.

• Running Your LoadTest Script.
  Once the loadtest script is ready and loaded simply press the PLAY icon or use LoadTest > Start LoadTest F6 to launch your eValid LoadTest scenario.