 REVIOUS |
OME |
EXT
 |
Test Hierarchy
Operative
An operative is an agent responsible for initiating a selection of test cases against a particular product. The operative knows exactly which product it will target, but the test cases it must carry out against that product may change from one run to the next. The operative knows how to interpret the properties provided by the test case in order to set up the environment for the test. The operative also knows exactly how to interpret the commands that are provided within the test case.
Agency
The agency is the place from which individual operatives of a particular type
are obtained. An agency is an implementation of the Factory pattern, in
that it can create new instances of operatives on demand, but it can also be
configured to supply the same operative instance to all consumers.
Kinds of Test Objects
The Blitz environment includes several test objects that are hierarchically related to each other. Three of these are classes that are instantiated and used by Blitz during test execution:
• a TestCase comprises one or more commands that are to be carried out
by an operative;
• a TestSuite comprises one or more test files, each of which
represents either a TestCase or another TestSuite;
• a TestScenario is very much like a TestSuite, except that it
provides global-level attributes to the testing environment.
The following diagram shows the inheritance relationship among these objects:
XML Specification
Test objects are specified externally using XML, according to a schema
defined in a special file called BlitzSchema.xsd. This file defines the
permitted elements (including their number and order) as well as any
restrictions or constraints that must be observed.
|
REVIOUS |
OME |
EXT
|