|
Each time a script runs the results
are saved to the Results sub folder of the directory from which the
script is loaded. The results are saved in two formats, Extensible Markup
Language (XML) and Comma Separated Values (CSV). A third file,
with the extension log, contains all trace information generated during
the run.
Each of the files has the
following format: -
<Script
Name>YYYY_MM_DD_HH_mm_SS.(xml|csv|log)
Where:
-
YYYY Year
MM Month
DD Day
HH Hour
mm Minute
SS Second
The
log file contains one line per trace entry in the form: -
YYYY/MM/DD HH:mm:SS.Tht <Type> :<Variable>:<Text>
Where: -
YYYY Year
MM Month
DD Day
HH Hour
mm Minute
SS Second
T Tenths
of second
H Hundredth
of second
t Thousandths
of second
<Type> Finest
| Finer | Fine | Config | Info | Warn | Severe"
<Text> The
trace message
An
example of a script log file is TCP
Client.tsr2007_6_2_14_50_57.html
The XML file contains the
results in Extensible Markup Language format. You can double click on
this file to view the results as a web page. An example of a results xml
file for a pass is TCP Client.tsr2007_6_2_14_50_57.xml and a
fail is windowtest.tsr2007_6_3_14_6_31.xml.
As the XML file has a well-defined structure you can use
this file should you wish to create your own results analysis software. If
you are not familiar with XML please checkout the W3schools tutorial at http://www.w3schools.com/xml
before proceeding as the terms
used may not be understood.
The root element of the XML is results which has the
following tags: -
script_name The
name of the script
host_name The
name of the PC that run the script
date The date of
the results (format YYYY-MM-DD)
time The
time of the results (format HH:MM:SS)
node A
node represents a line in the script
Each node element has the following tags:
-
type The type of
the node (e. g. root, comment, assignment)
text The
script text as seen on the GUI
run A
script run with results (zero or more of these)
overall_result The
overall result for this node
node A
child script node (zero or more of these)
Each run element has the following tags: -
result The result for this
run.
timetakensec The
number of seconds taken to execute the script line.
date The
date the script line was executed (format YYYY-MM-DD)
time The
time the script line was executed (format HH-MM-SS)
The Comma
Separated Values (CSV) file provides an easy way of analyzing the results
using a spreadsheet such as Microsoft Excel.
An example CSV results file for a pass
is TCP Client.tsr2007_6_2_14_50_57.csv and a
fail is windowtest.tsr2007_6_3_14_6_31.csv.
The first line provides the name of the PC
on which the script was run plus the date and time of the results.
The top section of the results file
provides the pass/fail counts for each script line including the
percentage pass rate. If there are any failures the time stamp of each
failure is shown in the Failure Times column.
The next section provides the execution
times for each script action that passed including max/min and average
timings. This section does not provide timings for failures as these are
usually simply timeouts and would distort the figures. The data in this
section can be used to see if there are any spurious large PCU usage
spikes etc.
The final section provides the consecutive
pass counts including max, min and average. This can be used to see how
reliable the software/hardware under test is.
|
