The following requirements are necessary in order to install loadIT.
One Client Test Environment
The following requirements are necessary to run the loadIT client (controller) on one computer. The client (controller) can be used for recording test cases, creating test plans, running debug tests or small load tests.
Multiple Client Test Environment
The following requirements are necessary to build up a multiple client test environment. In this case there are multiple loadIT agents which are controlled by one loadIT controller one a master client. About one computer for 200 simulated virtual users is recommended
Installation and configuration
The following steps need to be done once in preparation to use loadIT.
- loadIT is distributed as zip archive. This needs to be extracted to a location of your choice.
- After extracting the zip Archive you should have following directory structure.
The loadit folder contains the loadIT application itself. All files which belong to load tests can be found in the load-tests workspace folder. DataPoolGenerator is a software that can help you to create text files to be used as data pool from SQL queries. The folder BIRT contains the reports that can be used to display load tests results that were saved in a database.
- On the download page you were able to ask for a free license. You'll receive the license via email. Please copy it into the subfolder "loadit\lic".
- To configure loadIT you have to open the jmeter.properties file which is located in the loadIT’s bin directory. The format is a java properties file. Special characters like backslashes need to be escaped.
All the following properties should be reviewed and maybe adjusted to you system.
host name of the server that will be used as default for recording
port on which this application server listens
Default URL extension of nt_default_server
Variables with which the test plan will be pre-populated.USER and PASS should match the user you are mainly using for testing. You can add own variables that will be added to the test plan by default, separated by commas.
The default time in milliseconds that two groups of requests will be delayed when running the test.
The default duration in seconds of a test case loop, when using the runtime controller.
This path points to the directory of your test cases. This directory will be used as default in test case save and open dialogs.
These are the default URL patterns that will be ignored when recording with loadIT. The patterns are separated by commas. The goal is to filter static content like images or style sheets, that usually is cached by the browser and that does not trigger a lot of logic in the application server.
Timeout duration for global synchronization timer.
Percentile value for report. In Case of 95 it will show the highest of the 95% smallest values form 100%. This helps to filter out some extraordinary values.
Percentage of the NFR reached until the table cell is shown as yellow in the report.
Percentage of the NFR reached until the table cell is shown as red in the report.
functional requirement type, X is a continuous index starting with 1. Content is in format name,average NFR in seconds,percentile NFR in seconds
Index of the functional requirement to be used for the "Total" row in the aggragate report. If nothing is specified, there is no NFR for the "Total" row.
Name or path of the file containing the use cases and their business areas to be displayed in the drop down box of the Workbench Controllers. The format of a line in the file is expected as: id,use case name,business area.
Strings indicating unsuccessful responses, to be added in the default global assertion.
unknown error has occurred,
The default populated step names when recording with the proxy server. This usually are the login and logout steps, where the specific steps of the use case to be recorded will be pasted in the middle. As line ending character "\n" is to be used.
Values true/false whether to populate the workbench when starting loadIT.
This test plan will be opened at startup
If this value is set on a loadIT agent’s properties file, it will copy its log file (jmeter-server.log) after finishing the test to the specified destination under the name jmeter-server-[hostname]-[date_time].log. The value can be an UNC network path. Similarly, copy_server_log_precommand and copy_server_log_postcommand allows executing commands before copying, e.g. to map network drives.
Pattern to replace volatile strings in “compare with recording”. Matching elements will be replaced by the content of the setting comp_replace_intoX. With comp_replace_restrictstepX it is possible to use this replacing rule only if the action name (transaction controller or sampler name) matches the provided value. X is a continuous index starting with 1.
The JDBC connection url to be used when exporting test executions into a database. The database is expected to contain the correct schema (see 6.1).
Class of the driver to use for database access (drivers for MySQL and Oracle are already included, for other databases the jar files need to be put into the lib directory).
db_user and db_password:
Credentials for accessing the database.
If you want to create Tables with unique names you can use a prefix.
Additional Configuration for a multiple client test environment.
On the controller computer, you can now run loadIT by executing the file StartLoadIT.cmd (Windows) or StartLoadIT.sh (Linux/Unix) located in the directory loadit. It might be easier if you create a shortcut to this file on the desktop or in the start menu.
The file jmeter-server.bat / jmeter-server.sh in bin needs to be executed on the agent computers to run loadIT in server mode. Depending on how you use these computers, it might be a good idea to add a shortcut to the startup start menu folder, so that the server will be started every time the computer is run, or to add a windows service, using autoexnt for example, see http://support.microsoft.com/kb/243486.