Script Manager

Script Manager records the script, manages and applies parameterization and correlation. User can further insert transactions in the script and can verify by putting checkpoints.

Script

A Script represents a typical session of web application’s user interaction. It has a well-defined structure and keeps documentation of web application user actions. NetStorm executes a script to emulate a web user activity. A script can be executed several times during a test.

Virtual User and Session Count

Virtual User

Virtual users or Vusers are the conceptual users which emulate human users interacting with application executing a test script. Virtual user is the software simulation of real world user and a session represents what it does. Each group consists of a number of virtual users executing a test script.

Session Count

A session represents a sequence of page navigation by a user. Session count is the number of occurrence of sessions. It depends on number of pages a user is accessing and total number of users.

Fixed Session Rate and Fixed Concurrent User

Fixed Session Rate

Fixed Session Rate or FSR indicates that while running a scenario, session rate is fixed.  Once a Vuser is removed from the system, the connection is closed. User injects in the system as per the need. To achieve session rate as defined in the scenario, users come in the system. Scenarios on FCUs are of following types:

  • Simple Scenario Based
  • Simple Group Based
  • Advance Scenario Based
  • Advance Group Based
Fixed Concurrent User

Fixed Concurrent User or FCU indicates that while running a scenario, number of users is fixed before start of the test.  Scenarios on FCUs are of following types:

  • Simple Scenario Based
  • Simple Group Based
  • Advance Scenario Based
  • Advance Group Based

Think Time

It is really un-realistic for any real user to just keep clicking the pages one after the other without pausing to look at it. The user spends some time in viewing the pages that are downloaded. The average viewing time depends upon the page contents & the user’s familiarity of the page. Each page may be assigned a think time. If a think time is not associated with a specific page, default page think time would be used for such pages. Page Think Time is also called the Page View Time (after a page is downloaded).

Script Types

There are following types of Scripts:

  • WebLegacy (HTTP/HTML): This protocol is used to record scripts which are ‘C’ language syntax based functions using NetStorm APIs. User can either use only Internet Explorer/Mozilla etc. for recording these scripts.
  • WebC (HTTP/HTML): This protocol is used to record scripts which are ‘C’ language syntax based functions using NetStorm APIs. User can either use NetStorm Browser or Internet Explorer/Mozilla Firefox for recording these scripts. These scripts are recorded as flow files per user session.
  • WebClickAndScript: This protocol is used to record scripts which are ‘C’ language syntax based functions using NetStorm APIs. Default browser available for these types of scripts is NetStorm Browser. These scripts are also recorded as Flow files which contains NetStorm API’s per user interaction with different input fields such as input box, radio button etc.
  • WebJava (HTTP/HTML): This protocol is used to record scripts which are ‘Java’ language syntax based functions using NetStorm APIs. User can either use NetStorm Browser or Internet Explorer/Mozilla Firefox for recording these scripts. These scripts are recorded as flow files per user session.
  • WebServices: This protocol is used to record scripts which are C language syntax based functions using NetStorm APIs same as WebC protocol.

Script Structure

A Script consists of list of files – flow.c, init_script.c, exit_script.c, registrations.spec, and runlogic.c.

Script

The detailed description of each file of Script structure is provided below:

flow.c

  • This file contains main URLs, headers and embedded URLs.
  • It contains the main execution loop & the URLs that are accessed by NetStorm.
  • Transaction and CAPI is added from flow.c file.
  • Parameters and Checkpoint can be added from flow file of script. After adding checkpoint and Parameter, API is added in registrations.spec file.

init_script.c

  • Any initialization can be done here.
  • Any relevant NS C API can be used in this file.
  • This file is internally called by NetStorm.

exit_script.c

  • When user completed execution of flow then c file is called.
  • This file is internally called by NetStorm.

registrations.spec

  • Checkpoint and Parameters are added in this file.
  • Parameters and Checkpoint can be added from flow file of script. After adding checkpoint and Parameter, API is added in registrations.spec file.
  • Default spec file is hidden and user can display it after clicking the Show/ Hide registrations.spec file option in View menu.

runlogic.c

  • RunLogic allows user to create a custom flow to be executed by NetStorm.
  • Flows of the scripts can be ordered here.
  • With RunLogic –
    • All pages/flows can execute as per requirement
    • Good control over execution of pages or on the group of pages (Blocks)

Directory Structure

A Script consists of list of directories – Dump Directory, and runlogic.c. The detailed description of Script Manager Directory structure is provided below:

Dump Directory

It contains: –

  • Header file: It contains the request and response of each page.
  • list: It contains URL’s of all the pages.
  • Pages.html
  • PagesList.html

Temp Directory

It contains: –

  • changed_url.txt: This file contains the URL whose names are parsed.
  • logs:  This file contains Script Recorder_debug.log and script_Recorder_error.log.