Previous Topic: Stress Tests

Next Topic: Report Viewing

Thread Control Files

A thread control file determines the number of repetitions and threads the Test Tool runs in the Advanced Playback mode. It contains multiple instruction lines in the Test Tool's own scripting language and comments, indicated by the # symbol at the beginning of a line.

The basic instructions are in the format: <script file name>, <number of script repetitions>, <number of threads>.

For example:

# c:\temp\test_data.txt, 8, 6

This line indicates that:

The Test Tool writes the output of the test to a file. The output file name is the name of the input file with _out# appended to it, where # is the incremented thread number. For example, the output files for the test above are c:\temp\test_data.txt_out1 to c:\temp\test_data.txt_out6.

The Test Tool scripting language includes the commands in the following table to control the script file output. See the following figure for a sample thread control file.

Command

Description

.report

Generates a final report (as an output file) summarizing the test results. The report does not include the status of each server request. This is the default.

.output

Generates a final report (as an output file) summarizing the overall results including the status of each server request.

.viewstats

Displays final statistics in a text editor.

.verbose

Generates output files containing the details of each server request.

.brief

Generates output files containing the brief results of each server request. This option is only valid when used with the .output command.

.sleep

Lets the Test Tool pause for a specified amount of time (in milliseconds). This simulates intermittent server requests.

.connect <setting_file>

Initializes the Test Tool using information from the settings file to set up a multi-threaded test with one simulated Agent. The default multi-threaded test comprises multiple simulated Agents with one simulated Agent per thread. You can also set up a test with one simulated Agent and multiple threads by using this option.

.disconnect

Un-initializes the Test Tool to indicate the end of one simulated Agent multi-threaded test.

.output
.brief
c:\temp\test_data1.txt, 2, 3
.verbose
.sleep 5000
c:\temp\test_data1.txt, 2, 2
.brief
c:\temp\test_data1.txt, 3, 4
.connect smtest.ini
c:\temp\test_data1.txt, 5, 6
.disconnect


Copyright © 2010 CA. All rights reserved. Email CA about this topic