A test plan
defines the probes and
the injectors to be used, with their parameters, and where to deploy
them. Remember that injectors and probes are uniformly designated as
"blades". Note that the test plan is no more editable when a test is
deployed.
Blade id is a unique identifier for
the injector or probe to be deployed. A default id is automatically set
when adding a new blade, but it may be freely changed by the user as
long as it remains unique within current test plan.
Server offers a choice between
available CLIF servers, where the blade is to be deployed. The list of
CLIF servers may be updated using the refresh button.
Role specifies whether the blade is
a probe or an injector.
Blade class is where the user sets:
either the Java class to be
instantiated as a load injector (fully package-qualified name, without
trailing .class extension). For exemple, for a classic ISAC scenario, use "IsacRunner"
or a family name in case of a
probe. Available families are: cpu, disk, memory, network, jvm, rtp.
Blade argument is an argument line
that will be passed as an argument to the new blade instance.
Comment is an arbitrary user comment line.
Test plans may
be saved and restored using options in
the File menu.
CLIF
tree view
The editor view shows blades by type. Tree view shows
the same blades
but organized by server. User can copy/paste or delete blades from
this view.
NB : Only blades can use copy or delete. You can't use this action on
server object.