Jagger Instrument Structure
Main goal of the chapter to describe hierarchy of Jagger instrument and give short overview of all components involved.
Order of blocks is inverted on purpose to go from general to particular
Test engine which is compiled together with your test project. Jagger task is to start test suite(s) defined by you, collect measurement results, monitor system under test parameters. Details: Jagger Operation Modes
Settings are defining all user configurable properties of Jagger. Details in Properties. If some properties are not defined default values will be taken from /configuration/basic/default.environment.properties
Suite is defining system under test, access method to this system, expected return values as well as load that will be applied to the system. Also defines connection to custom components.
How to write XML files you can see in Configuration files.
Hierarchy of test suit and execution order of test suit methods you can see in Test suite structure.
Can override several test suit methods with user defined code.
Execution order of test suit methods you can see in Test suite structure.
How to create custom components you can see in Custom component
Custom component(s) - Test suite(s): Connection to custom classes to override different test suit methods can be included to XML files. For details see Custom component
Test suite(s) - Jagger settings: Connection is defined by configuration name.
Test suite(s) XML defines different test configurations. See description of configuration tag in Configuration files.
In Jagger settings you can select what configuration to use by setting chassis.master.session.configuration.bean.name property equal to some defined configuration name. Details in Properties.
###Blocks 3-4 Jagger settings - Jagger: When Jagger is launched, properties file is passed as input argument (see how Jagger is launched in Getting Started section). Properties can be also defined with use of -D option.
###Blocks 4-5 Jagger - System under test: All information about system under test connection is defined in Test suite(s) XML files (where to connect, how to connect, what information to transfer and monitor, what load to apply, etc.)