| Attribute Name |
Attribute Description |
| scenarioname |
The optional name of the scenario. If this attribute is not present the name will be set to the
'UnnamedScenario'. This name will appear on the console log and will also form part of the log file name. |
| runname |
The optional name of the scenario run. This name is appended as a suffix to the
scenario name to form full name of the scenario run (This name which appears on the console log and forms the
part of the log file name). Suffix is used to specify additional important feature of the particuar
scenario run. For example scenario 'SearchForClients' can have two runs: 'OnCORBA' and 'OnJ2EE'. If this attribute is not present it is simply omitted. |
| scenariopath |
This mandatory attribute contains list of one or more directories
(accepting : and ; as path separators. relative path names will be interpreted as relative to the project's basedir).
This is where scenario files will be read from. The directories will be read from left to right, but the test case files
in each directory will be picked up and executed in the ascending alphabetical order. |
| includepath |
This optional attribute contains list of zero or more directories
(accepting : and ; as path separators. relative path names will be interpreted as relative to the project's basedir).
This is where include scenario files will be read from. The directories will be searched from the
left to right and the first file with matching name will be included. |
| classpath |
Alternatively to the classpath subelement or classpathref attribute,
the classpath can be specified using this attribute with the single string containing one or more
directories or files (accepting : and ; as path separators. relative path names will be interpreted as relative to the project's basedir).
See the classpath subelement documentation below for more details. |
| classpathref |
Alternatively to the classpath subelement or classpath attribute, the classpath can be specified
using this attribute using path reference id of the path defined elsewhere. See the classpath subelement documentation below for more details. |
| clientclasspathdir |
THis optional attribute must point to the root directory of the client classpath tree. The invocation of every servicemodule
can be done using dedicated classpath. For example when HatMaker.CRM.MarketingQueries servicemodule is invoked
the classpath is build from the following components:
- All jarfiles located in the ${clientclasspathdir}/HatMaker.CRM.MarketingQueries directory, if it is present.
- All jarfiles located in the ${clientclasspathdir} directory, if it is present.
- All classes defined in the classpath subelements of this element.
Note that this feature is very advanced and is used mainly in the big testing installations where many systems
built on separate technologies are tested toghether. |
| failonerror |
The optional boolean flag which tells scenario runner whether to fail or not
if the test scenario run itself has failed. Default is true, which means the scenario runner will
fail if any of the tests will fail. |
| logperformance |
The optional boolean flag which tells scenario runner whether to log the performance
data or not. Default is true, which means the scenario runner will log performance data. |
| specimenfile |
The optional path and name of the file where the original specimen log should be obtained from.
If this is attrribute is given, the regression analysis will be performed at the end of the test. If this attribute is
not given - the regression analysis will not be performed. |
| rundir |
The optional path and name of the directory where to run the scenario runner from.
If this is attrribute is not given, the project's base directory is used. |
| logdir |
The optional path and name of the directory where the logs should be stored.
If this is attrribute is not given, the directory where scenario runner is running from is used.
This directory will be created if required. |
