Overview
QEngine's web load test settings section provides you with options
to configure the default play settings before playback of load test
scripts. The following variables can be configured:
How do I get to the Settings screen?
From the web load test UI, select a suite name listed in the
left-side panel and click the 'Settings' link from the screen displayed
on the right side. You can also click the 'Settings' option listed
under the suite name from the left-side tree itself. Both these actions
will take you to the 'Settings' screen. From this screen, you can
configure variables as explained below.
Load Test Settings
Select the 'Load Test Settings' option in the Settings page to open
the 'Load Test Settings' screen.
The following table gives a detailed description of the general and
advanced options available which can be configured before playback of
load test scripts. Also shows the default values of each option.
| Settings |
Description
|
Default/Supported Configuration
|
|
General Settings
|
|
User Agent
|
The user agent to be simulated for the virtual users during
load test. Additional user agents can be added if required.
|
IE. Other options include Firefox, Mozilla, Galeon and Opera.
|
|
Save Response
|
Save each and every page response for each virtual users
during load test.
|
Disabled
|
|
Save Logs for each user
|
Logs each and every page request and response headers,
Parameterization outputs for each and every virtual user separately.
|
Disabled
|
|
Include image, script, stylesheet in page download
|
Downloads all the images, scripts and stylesheets associated
with each and every page during load test. Using this option you can
study how the response time increases upon including the images.
|
Disabled
|
|
Test application on alternate host Host: --- Port: ----
|
Use the same load test by just altering the Host and Port
destination to run the load testing against different servers.
|
Disabled
|
|
Use Http1.0 or Http 1.1
|
Select the User HTTP protocol version that needs to be
simulated, such as HTTP 1.0 or HTTP 1.1.
|
HTTP 1.0
|
|
Use unique data for each request
|
Use this option if your application needs unique data for each
virtual users, such as username and password. If you select this
option, you need to give the sufficient number of data in the
parameterization.
|
Disabled
|
|
Continue test or stop test (if data is not sufficient)
|
You can choose either to stop the load testing or to continue
with the same data, if the configured no of data is not sufficient.
|
Continue Test
|
|
Unique IP for each virtual user
|
Assign unique ipAddress for each virtual user. If your
application contains IP-based session tracking feature, you need to use
this option.
|
Disabled. If enabled, you need to configure virtual IPs using
the batch/shell provided. Please refer to Configuring Virtual Ips for
details.
|
|
Use Think time
|
If this option is enabled, QEngine will wait between the URLs
for the recorded time interval.
|
Disabled
|
|
Multiplication factor
|
Factor to multiply recorded think-times when playing with slow
link speed.
|
1
|
|
Advanced Settings
|
|
Socket Timeout
|
Controls the timeout of sockets opened during load testing.
|
60,000 milliseconds.
|
|
Retries
|
The number of times QEngine needs to retry to get the
connection to the server to send the request.
|
Disabled
|
|
Retry Delay
|
The number of seconds to wait between retry attempts.
|
Disabled
|
|
Repeat Delay Interval
|
The number of seconds to wait between users repetition.
|
0
|
|
Follow Redirects
|
If this option is selected, Load engine follows redirect
(302/303/307) commands received from the host. If selected, specify the
Redirection up to specified number of times.
|
Enabled and level set to 10.
|
Start user randomly
| While starting the load testing instead of starting the user sequentially user will be started randomly to simulate load.
| Disabled
|
|
HTTP Responses
|
Displays the list of response status code indicating the
success status of the URL. You can configure other response codes to
indicate the success status of the URL as per your requirement.
|
20, 300, 301, 302, 303, 304, 307,
401, 403, 404, 407, 408, 41.
|
|
Enable Meta-Refresh
|
QEngine handles the Meta Refresh tag conditions by default and
it will redirect the URL as per the tag values. This option can be
disabled.
|
Disabled
|
| Enable Caching of initialization
data |
QEngine can store the
initialization of previous test execution to use it in future execution
with same set of configurations of usercount, load type etc.
Instead of populating the initialization of data, enabling this option
will use the any of the available initialized data chosen by the user
for test execution. |
Disabled
|
| Logging Level |
Logging level to use for playback
1. Errors only (to errors during play only will be logged)
2. Info (Limited logs showing request and response alone will be
logged))
3. Detailed log (all the logs will be logged)
4. Debug Level (debug level logs will be logged)
5. No Logs (Logs will be shutdown) |
Info
|
Show Request Parameter in Logs
| To enable security of the application the parameters to the URL being printed in the log file is controlled using this setting.
| Disabled
|
Authentication Settings
In this screen, you can configure authentication details for the web
application under testing. By default, QEngine supports Basic, Digest
and NTLM scheme of authentication.
QEngine by default automatically identify the authentication system during playback, based on the response from the application server. If you know the authentication sceme beforehand configure the same in the Configure Authentication Scheme combo box.
You can configure single username and password for all the user or otherwise configure unique username and password for each virtual user. Configuring the username and password is discussed below:
Configuring Single Username and Password
Configure the User name and passowrd in the appropriate text field after choosing single option. If the authentication scheme is NTLM then click on the Advanced Settings and provide the hostname and domain of the system where QEngine is running.
Configuring Multiple Username and Password
Select the multiple option and choose the datasource for the Username. QEngine supports to fetch values from CSV / Database. Configure the appropriate datasource to fetch the data for username and password.
- CSV option - Follow the below steps to complete the CSV configuration
- From the CSV File Name combo select the file source from which the data should be extracted.
- If the desired csv filename does not exist in the combo you can create New csv file , Import CSV file present in the local drive.
- If CSV file has colum name configure the column name after selecting the Use Column Name check box.
- If CSV file does not contain column name provide the column number from which the data should be extracted.
- Database option - Follow the below steps to complete the Database configuration
- From the Database combo choose the database type to use. If the database type of your choice doesn't exist configure the same in Configure Database link.
- Select the connection URL appropriate to the database to use.
- Configure the Table Name and Column Name from which data should be extracted.
If the authentication scheme is NTLM then click on the Advanced Settings and provide the hostname and domain of the system where QEngine is running.
Proxy/Firewall
Settings
If your web application server is hosted behind a proxy or a
firewall, you should configure Proxy/Firewall settings.
Select the connection type to the server from Direct or Proxy. If it
is a direct connection, select 'Direct' option and click the 'Apply'
button. If you are connected through a proxy, select the Use Proxy
option. This will display the Proxy Settings screen inline.Configure the proxy details and click the Apply button to save the configuration
Distributed
Playback
To simulate very high load on the application in the range of more than 1000 virtual user distributed playback option can be used in QEngine. By this the load will be distributed among the QEngine agent and the load testing will be executed. Thus the very high load can be achieved. To execute test in distributed mode follow the below steps:
- Install QEngine in the machines which are going to act as distributed agent and start the agent through Start->All Programs->Manage QEngine WebTest->Start QEngine Agent or invoke the bat file present under <QEngine Home>\bin folder namely StartDistributedAgent.bat/sh.
Go to Settings link present under Suites in the suites tree and select Distributed Load Testing tab.
Select the 'Use Distributed Playback' checkbox.
-
Click the 'Add Agent Details' button. The 'Agent Configuration'
screen will be displayed.
-
In the 'Agent Configuration' screen, configure the Agent IPs,
RMI port and maximum users to be simulated in the distributed play
engines. The maximum user in the agent can be determined based on the machine
configuration. In a 512 MB RAM machine you can simulate upto 250
concurrent users. This is to enable the Test Controller to remotely contact the
distributed play engines to perform distributed load testing.
To know more on the configuring agent follow the below URL:
http://qengine.wiki.zoho.com/Distributed-Play-Engine-Configuration.html
- Click on the "Apply" button in the Settings screen to save the configuration.
- Thus during load test playback the virtual users will be distributed to various agent and will apply the load to the application server.
Email Notification
In this screen, you can specify the email addresses to whom email
notifications are to be sent. Enter the email addresses separated by
comma in the email id field. Select the 'Send Summary Reports' checkbox
if you would like to receive summary reports of the load test.
You can also configure mail server details from this screen. Refer Configuring Mail Server
for detailed steps.
Dataset Configurations
In this settings screen, you can view / add dataset used in the parameterization to dynamically fetch and substitute values either from
a database or csv or Excel file.
Refer Dataset Configuration to know more details.
Load Test
Execution Order
In this screen, you can configure filters for load tests as well as
use the Sequence Editor to change the sequence of created load tests.
Click the 'Filter Configuration' link to open up the Filter
Configurator screen where you can configure filters to execute load
tests matching specific criteria.
Refer Configuring Filters
for detailed steps on configuring filters.
The Sequence Editor helps you configure the sequence in which load test need to be executed. Click the 'Sequence Editor' link to open
the 'Sequence Editor' screen where you can specify the sequence of load test.
Refer Configuring Sequence
for detailed steps to choose the order in which load test are
executed.
Recorder Settings
Click 'Recorder Settings' tab from the 'Settings' page, to open the
'Recorder Settings' page. In this screen, you can filter the requests
for specific extensions. 'Filter Requests' field supports jpg, jpeg,
png, gif, bmp, js, css, mpg, vwa, ico, and swf extensions. Click 'Apply' button to save your changes.
Report Customization
From the left pane in the 'Settings' page, choose the 'Report
Customization' tab to configure Report templates. Report templates
provide a flexible way to customize your report format. You can choose
the specific options to generate the reports and graphs of your choice
after load test execution. Click 'New' button to create a new report
template or select the existing report templates (if any) from the
Report Templates combo and click on the 'Edit' button to edit the
report template.
Refer Customizing Load Test Reports for detailed steps to customize reports.
Variable
Configuration
In this screen, you can configure the suite level variables that are
automatically substituted by QEngine at runtime. Their values cannot be
changed between scripts. Example of environment variables include
$localhost, $localnet, $localip, $date(dd_mm_yyyy), etc. Click the
'Environment Variables Configurator' link to configure environment
variables.
Refer Environmental variable configuration
for detailed steps.
