The contents and structure of a Job will depend on the type of test to conduct, the nature of the targeted system and the goals of the performance test. In its simplest form, a Job can consist of just one Task Group running a single Collector or a Script. However, to produce a fully automated performance test that accurately simulates the desired test scenario, as well as producing the results data required, it is usually necessary to develop a more detailed Job structure.

Script and Collector Tasks are contained within Task Groups in a job. Task Groups let you control when Tasks run and how they operate during a Job-run. A Job can include one or more Collector-based Task Groups, one or more Script-based Task Groups or a combination of both, depending on whether an HTTP/S load test or a production monitoring test is being developed. Add Scripts to generate the HTTP/S load levels required against target systems during a Job run. Add Collectors to monitor and record performance data from Hosts.

The Task Groups that make up a Job can be enabled or disabled, before or during a Job run. Disabling the Script-based Task Groups means that no load is generated when the Job is run. This gives the ability to use the same Job within both load test and production monitoring scenarios and lets the performance of a target system within these two environments be directly compared. The Job is ready to run after the necessary Scripts and Collectors have been added and the required Task Group settings have been applied.

Jobs can be run using networked computers on remote Hosts to execute the Task Groups that comprise a Job. Distributing Task Groups across a network lets you use the processing resources of multiple networked computers. It is then possible to run HTTP/S load tests that generate realistic heavy loads simulating the activity of many users. In order to do this, HTTP/S Load must be installed on each Host and the AgileLoad Daemon must be running and configured to specify the Repository Host for the Job. For more information on configuring the AgileLoad Daemon to run a distributed Job, see Distributed Jobs.

Go back to the Learning center:

Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap