Table of contents
3.3. Import and open an existing
test plan
5.5.
The results of executions
CLIF is
a Java framework for performance testing of any kind of system. Typical targets
include but are not restricted to web sites, LDAP directories, databases, application
servers... CLIF makes it possible to generate traffic by deploying and
controlling load scenarios through a set of networked computers, while both
storing and monitoring information about response times, error occurrences...
It also supports the deployment and control of probes, giving information about
computing resources (http://clif.ow2.org/).
CLIF supervision console is used to control CLIF
system with an Eclipse plug-in.
CLIF needs Java 1.4.2.
Console is built for Eclipse 3.x with JFace and SWT libraries.
Usual Eclipse plug-in set up.
Open archive
CLIFConsole.zip and copy plugin/CLIF Console Plug-in directory in Eclipse plugin directory.
Open Eclipse with CLIF Console plug-in.
A new CLIF menu and a new toolbar
button appear in the workbench.
Execute Start CLIF Console menu
command or button command.
Workbench perspective change into CLIF Console perspective.
Figure 1 � Eclipse after
plug-in has been installed
A new
menu CLIF and a new button appear in the
toolbar.
Figure 2 �� CLIF menu
Execute
the Start
CLIF Console command. You
can click either on the menu or on the button.
A configuration
wizard is launched in order to start CLIF in background. However this wizard can�t be opened if the console has
already been configured and started.
Figure 3 �� The configuration Wizard
Host name :� the host where the console will be run.
Port number : the
port number for the console embedded code server.
Click Finish to switch to perspective CLIF Console.
Figure 4 �� Confirmation
Click OK, Eclipse is now in perspective CLIF Console.
Figure 5 - CLIF Console perspective
It�s
located on the top left of the perspective. Navigator view allows to manage
test plan.
This
view offers the same functionalities as the classical Navigator view. It can
create new projects, documents and import existing documents as well as
classical Navigator view. You only need to use Eclipse�s File menu or
Navigator�s contextual menu :
-
Create a new projetct : New -> Project� ;
-
Create a new document : New -> Other� ;
- Import an existing document : Import� -> File system.
It�s located on the bottom left of the
perspective and allows to get information about the selected file in the Navigator view. It is the same as the Properties
view of Resource perspective.
The
center part is dedicated to the test plan editor. A file with the extension
".prop" will be opened with a test plan editor.
When a
test plan is run, a window is openend to monitor the test.
Monitor
Windows are added on the right of properties view.
Performing
test needs to create or import test plans.
You must
create a new project in the Navigator view.
Create a
new Simple
Project (select Simple ->
Project in the creating
projects dialog box).
Figure 6 � A new
project is created in the navigator
Now, you
can create a new test plan.
Create a
new file as in section 2.1
Select CLIF -> New
Test Plan in the dialog
box.
Figure 7 � Creation
of a new test plan
A
creation wizard is opened and we have to enter the project where the test plan
with the file name will be added.
Figure 8 � The new test
plan creation wizard
Container : the project where the file
will be created (the project must exist).
File name : the file name. The file must
not exist and must have the extension .prop. If you don�t specify an extension, .prop will be set as default extension.
Click Finish. Test plan is created and opened in
the test plan editor.
Figure 9 � Test plan is
created and can be seen in the navigator
See
section 2.1 to import an existing test plan in a selected project.
Now, the
test plan appears in the Navigator. Nevertheless, the import makes a copy of
the test plan. If you change this file it won�t change the original test plan..
Open the
test plan by selecting it in the navigator and press the enter key. You
can also click it twice in a
row.
Figure 10 � The opening of an
imported test plan
The test
plan editor is composed of two tabs:
-
An Edit tab which
can edit a test plan ;
-
A Test tab which
can execute some tests from a test plan.
The
edition area is composed of two parts :
-
An Injectors and probes part where we can choose elements to edit ;
-
A Properties part
where we can edit the selected element.
Users
can change the layout of these parts.
The test
plan edition consists of creation or suppression of blades and probes.
There
are three main functionalities :
Add : add a
probe or injector ;
Remove :
remove selected probe or injector ;
Remove All :
remove all probes or injectors from the test plan.
When you
add a new element to the test plan, the editor adds a probe or an injector of
the same kind of that printed in the open tab.
Figure 11 � Addition of a
SYSTEM probe
If the
test plan is empty and no opened tabs, a CPU probe is added by default.
When you
remove a probe or an injector, the editor removes the selected element of the
open tab. If this element is the last of a blade class the tab is removed.
Figure 12 � Suppression of a SYSTEM� probe
When you
delete all blades a confirmation message appears. If you click OK all blades will be removed from the
test plan.
Figure 13 � Suppression of all injectors or
blades
To Edit
a blade, you must select it in the Injectors and probes area. Then, its properties will appear in the Properties part. So, you just have to modify
these properties.
The mandatory
properties are referenced by (*). An error message appears if you try to save
erroneous modifications, the modifications will not be submitted and will be
lost.
The Id property must be unique. An error
message appear if there is already an existing blade in the test plan with the
same
The Class property involves sorting the blade
in a particular tab. The modification of the class property involves the modification
of the tabs.
If an
existing blade has the same Class than the fresh modified blade, the modified
blade will appear in the same tab
-
If the selected element is the last of its class, the tab will be
removed;
-
If the new class does not exist yet a new tab is created.
The
default view has an horizontal layout. However, you can switch to an horizontal
layout for a better vision of Injectors and probes part. To switch the editor�s layout, you have to
use the editor�s top right commands.
Figure 14 � horizontal
arrangement of the editor
The test
parts provide a similar representation of the test plan and they also allow to
select the blades to see the state of each probe or injector and the global
state of the execution.
Figure 15 � Test part of the
editor
This
part can command the execution of the test plan. It contains the requisited
commands:
-
Deploy : deploys the blades on the servers ;
-
Initialize : initializes deployed blades ;
- Start : starts the tests ;
-
Suspend/Resume : suspends/resumes the tests. The title
of the button changes according to the global state of the execution ;
- Stop : stops �the tests ;
-
Collect : collect the result after the test have
been stopped.
These
commands respect the blade�s life cycle within the context of tests. We can
access the commands only if the global state of the execution allows it.
The
Monitoring functionalities are provided in the View � MonitorView �. By default, this view is empty at
the console starting.
Figure 16 � Monitoring window
Figure 17 � Starting
Monitoring view
The monitoring of the plugin provides the same
functionalities than the stand-alone console and some new ones. Now, we can
navigate among several executions of test plans.
The
various .executions are arranged by tabs. The figure18 shows the test plan
execution � koala � 1 mai 2005 10:11:45 �.
Each
execution has a unique
Figure 18 � �Execution tab of a test plan
The
selected blades for deploying are arranged according to their class.
The next
figure shows cpu blades arranged in a homonymous tab..
Figure 19 � Deployed cpu blades
Figure 20 � Configuration du monitoring des lames
Contrary
to the classical console which displays checkbox this console just shows true or false. Nevertheless, that�s rather simple :
true means that the column option is activated
false means . the opposite
For
instance, the blue line of the figure 20 means that blade number six that it
must be displayed but its results must not be collected anymore.
To
modify these options,. you just have to click the cell you want to put to true or false.
Figure 21 �status bar and
control bar
The functionalities
of this bar are the same as the classical console.
Polling Period : This field allows to put an new polling period. You must enter an integer value. If
a non integer value is entered it will be set to 1 second.
Drawing timeframe: it deals with the scale of the display.
Reset : remove all the points from the screen
Stop : stops drawing
Set/Draw : starts drawing of the graphic or set the
changes claimed by users..
Figure 22 � Tableau de suivis des r�sultats
This table has been created to display points of the normal graphic. Each lige represents a point, with the hour (millisecond), the blade id which generates the data to make the point. There are at least the point�s coordinates � x , y �.
To update CLIF Console, you need to download last
distribution of CLIF system. Console is integrated in the distribution.