![](bg2.png)
is also composed of a module, called WebMonitor,
that will help in this task. This module, in a interactive
and simple way, makes quickly and reliably possible
the editing of a test case. Succinctly, this work con-
templates (1) the possibility of realizing distributed
and synchronized tests, (2) the automatic creation of
the test plan by the WebMonitor module, (3) the uni-
fication of the logs generated by each solicitant com-
puter in the case of distributed tests and (4) a method
of the monitoring and analysis of results.
2.1 The WebTeste Architecture
During the WebTeste development some problems
have been identified and some changes have been nec-
essaries.
The WebTeste consists of a distributed and ordered
architecture composed of four components (Figura 1):
Supervisors (A)
HTTP/Requests
(D)
(D)
(D)
Web Environment (B)
Connections
Computer with Web
Application
Log (C)
Figure 1: WebTeste Architecture.
• Set of Supervisors (A): Component responsible
for the management process of all test. It sends
the test plan to the other participants of the test and
puts together the logs created by them, generating a
centralized log, that is stored in XML format. This
allows to guarantee the synchrony among all tests
by the supervisors. This component establishes the
flow of tests to the web environment;
• Web environment (B): It can be composed of sev-
eral elements (e.g. firewalls, web servers in clus-
ter, application servers etc.). The web application,
used to the validation of the WebTeste architectural
model, is placed in this component;
• Log (C): It represents the centralized log that is
generated by the set of supervisors during the sim-
ulation of the requests to the web environment;
• HTTP/Requests (D): This component corresponds
to the requests to the web environment.
2.2 WebTeste Requirements
WebTeste is composed of functional and no-functional
requirements. Functional requirements consist of a
set of information (i.e. Creation of Test Plan, Con-
figuration of distributed test and Unification of logs)
based on three XML files (i.e. testplan.xml,
config.xml, logs.xml).
On the other hand, no-functional requirements are
composed of the following five elements: Creation of
Test Plan, Distributed Object Remote Method Invoca-
tion (RMI), Web Request Framework - HTTPUNIT
framework, Algorithm of Synchrony based on New-
top algorithm (Ezhilchelvan et al., 1995) and Test En-
vironment.
3 SIMULATIONS
Several simulations have been carried out. In this pa-
per, the configurations of some of them are presented.
These configurations have taken into account three
test plans (i.e. three specific tasks run in a web ap-
plication), two scenarios (i.e. homogeneous and het-
erogeneous laboratories, in which the distributed tests
have been performed), and one centralized test that
does not depend on the type of the laboratory, but
the computer configurations and the network connec-
tions.
• Test Plans have been created by the WebMonitor
and used in the scenarios #01 and #02 (Figures 2,
and 3, respectively). The test plan used in the sim-
ulations represents a purchase in a virtual shop and
consists of two, ten and twenty requested links to-
wards the purchase conclusion or while the user
navigate in web application;
• The main goal of the proposed types of tests is
to demonstrate the saving of response time when
the test is performed in a distributed way with re-
spect to the centralized test, avoiding the stress in
the computers that generate the requests:
– The centralized test is performed from a com-
puter that simulates all defined requests to web
server;
– The distributed test is performed from two or
more computers to web server; each one sim-
ulating the half or less of all defined requests.
Distributed tests are organized in two categories
with respect to the configuration of the comput-
ers used in the test: homogeneous and heteroge-
neous laboratories.
For this, both centralized and distributed tests have
been performed in the two simulation scenarios
(Figures 2 and 3) taking into account different
quantities of threads in blocks from 100 (minimum
quantity) to 2000 with an increment of 100, and
from 2500 to 10000 (maximum quantity) with an
increment of 500.
WEBTESTE: A STRESS TEST TOOL
247