PREVIOUS HOME NEXT

TestSuite

Schema Diagram

TOP

Description

A TestSuite has all of the characteristics of an AbstractTest; in addition, a TestSuite adds the following information:

Element Status Purpose
Execution specifier Optional If used, the execution specifier must be one of the following elements:
  • sequential: indicates that subsequently named tests will be executed in sequential order — i.e. one after the other
  • concurrent: indicates that all subsequently named tests will be executed concurrently — i.e. all at the same time, each test in its own thread of operation

The default mode is sequential.
Looping specifier Optional If used, the looping specifier must be one of the following elements:
  • loopTimes: Specifies exactly how many loops should occur. This must be a positive integer value.
  • loopDuration: Specifies the period of time over which the tests will be run (i.e., each test is executed repeatedly until the specified amount of time has elapsed). The syntax for a time period follows the form "nDnHnMnSnL", where "nD" indicates "n days", "nH" indicates "n hours", and so on ("M", "S", and "L" represent "minutes", "seconds", and "milliseconds" respectively. The letter identifiers "DHMSL" are case-insensitive. The following are valid time periods: "5D30m" represents "5 days and 30 minutes"; "24H" represents "24 hours"; "1d" also represents "24 hours".

The default is to execute each test exactly once.
testFile Required, Repeatable The name of a file containing either a TestCase or another TestSuite. Can be any string that ends with ".tst" or ".ste" (case insensitive). Each test suite is expanded and processed for handling by the specified operative. If the name of the file is not an absolute reference, then the file is expected to be located somewhere in relation to the last defined testFileRootPath, or "." if none is supplied.

TOP

Test Files

All test types (TestCases, TestSuites, and TestScenarios) are defined using XML. The file extension (last four characters) of the XML filename identifies the contents, according to the following mapping:

      
Extension File Contents
.tst TestCase
.ste TestSuite
.sno TestScenario

Case sensitivity is NOT enforced, so filenames may be specified with any combination of upper- and lower-case letters.

While these extension names are not strictly required by the parser for successful execution of the tests, they are useful from the perspective of being able to quickly distinguish between one kind of object and the other, so for this reason, the naming convention is enforced – that is, a file with a particular extension is expected to contain exactly one object of the appropriate type (TestCase, TestSuite, or TestScenario, depending on the extension); if it does not, an error is generated.

TOP

PREVIOUS HOME NEXT