Website testing: Load,
Stress and Performance testing

Editor - Source

The Source tab provides the advanced users with the ability to manually edit the settings of a single test. It is actually a view to the resulting .TST file. The syntax of a .TST file is similar to .ini files – that is, it consists of sections (names of sections in square brackets). General syntax of most settings used in the file is like this: <name>=<value>. You can start a line with a semicolon character to write comments or to temporarily disable some lines. Empty lines are ignored and can be used for formatting.

Each test should contain a [General] section and a set of requests. Optionally, the sections [InitSeq], [TestSeq], [FinalSeq], [Includes] and [Headers] can be defined.

• [General] section defines the global test parameters, default values for requests and various settings for controlling the behavior of virtual clients and the output files format.
  
  
• [InitSeq] section defines the sequence of requests to be run once before the main [TestSeq] sequence.
  
  
• [TestSeq] section defines the sequence of requests for the main testing cycle.
  
  
• [FinalSeq] section defines the sequence of request to be run once after completion of [TestSeq].
  
  
• [Includes] section lists external .TST files to be used within the current test. If you use external tests, the settings from their [General] section can override the settings of your file, but only if the [Includes] section is located below your [General] section). The same is true for [InitSeq], [TestSeq] and [FinalSeq] sections.
  
  
• [Headers] section allows to define additional fields in the HTTP request header (UserAgent etc.).

[InitSeq] and [FinalSeq] are considered empty by default. If the [TestSeq] is not explicitly declared, then all the requests defined in the file are considered to compose the [TestSeq] (in the order they appear in the file). These three test sequences are composed of request names, one per line.

You can redefine settings of a specific request within a sequence. List modified settings (using the <name>=<value> pairs) in round brackets immediately after the request name, separating pairs with commas. If <value> contains a comma inside, enclose the whole <name>=<value> pair in double-quotes (“).

Example:

[TestSeq]

request1

request1($method=get,"static=this,is+a+test",combined=yahoo!)

You can as well redefine certain global request parameters – using, e.g., $uri, $delay etc.

Example:

[request1]

$uri=/scripts/test/params.pl

$method=post

$port=8001

You can concatenate multiple functions to compose a single request parameter using the & character.

Example:

CombinedParam=Hello&$Nrand(10,99)&$Arand(5,10)

Click here to continue

Help Contents