SmarteLoad Detailed Capabilities

Seamless Integration
SmarteLoad easily transitions and streamlines functional, performance and load testing with SmarteScript and other functional testing tools. SmarteLoad scripts can be generated by executing existing SmarteScript scripts or other functional testing tools that play back on Internet Explorer, Firefox or Chrome browser (for example, WinRunner, QTP or other tools).

Grid Visualization System
During recording or script importing, SmarteLoad automatically creates a data grid which tracks and drives the test case flow. The grid contains static and dynamic data variables, data types as well as URLs, headers, forms and the type of actions to perform.

Automated Multi-level Grid-driven Testing
No programming is required. SmarteLoad is the industry’s first fully integrated tool. SmarteLoad parametizes and automatically correlates dynamic data and parameters received from servers upon client requests. Correlation of dynamic data is the industry’s most difficult, complex, and tedious tasks in load testing. User can undo specific or all correlation with a click of a button.

Ease of Use
Performance test engineers may specify the required Transactions and SyncPoints for the test without tedious script changes or programming. Transaction measurements and SyncPoints are added within the synopsis with a mouse click and are viewable at any time in the Synopsis grid.

Remote Server/Agent Installation
SmarteLoad is the industry’s first load testing tool that enables remote Host Generator Agent recognition, connection and remote agent installation on servers and hosts. The Host Management tool empowers users to easily and rapidly configure the testing environment without the need for manual installation or involving system administrators in this process.

Recording and Protocol Support
SGM is able to record HTTP/HTTPS traffic from any application, including Internet Explorer, Chrome, or Java applications. SmarteLoad also supports automatic decoding of Java Object Stream data.

Scripting, Debugging and Logging
SmarteLoad scripting is highly flexible. Playback logic and correlation algorithms can be changed by users. This means SmarteLoad can be customized to address unique customer needs, without waiting for a new software build.

SmarteLoad also has a very detailed logging mechanism. After execution of a synopsis in the Controller, you can analyze request-responses of any action for any SimUser.

SGM also provides fine grained batch mode comparison of Recording and Execution data simplifying script debugging.

Add Compound Dynamic Variables
Each type of dynamic variable has it’s own view. Some examples: compound variable view, Left Boundary Right Boundary (LBRB) dynamic variable view, and RegExp dynamic variable view.

Compound Variable Syntax
Compound variable can use data and dynamic variables and escaped text. Choose from a variety of methods to access data variables including first, next, random.

Compound Variables in Headers
Each header name or value is treated as a compound variable so all compound variable rules will apply to the header name and header value.

Random Fixed or Different
You can alter SmarteLoad Default Settings to select Fixed order (the same each time the script is launched) or Randomized. Fixed order is recommended to run regression tests for SGM.

Correlation.js
A correlation JavaScript file provides flexibility in handling correlation between selected actions or to correlate a single variable or dynamic variables including defining rules for handling found dynamic variables.

Player.js
This JavaScript file defines logic to play a single SGM action. You can override the default player at the script level. SGM will execute Player.Play() method for each action according to script logic. To debug overriding player use Microsoft Script Debugger and SetBreak() function. User can set verbose level in SGM options.

All as Compound Variable
All action data (url, headers, post data) is contained in one compound variable. All known variables from post data are in action vars grid. Double click on the variable value to change it value. Dynamic and data variable types are special cases of Compound type.

Compound Variables Calculation Order
All Compound Variables are calculated before each action starts in the order in the Dynamic Variables dialog list.

Variables Substitution Order
1) Action url.
2) Headers.
3) Post data.

Example: data variable dataVar with values 1,2,3 will change its value each occurrence.

Action url: http://some.com/[dataVar]/index.htm => http://some.com/1/index.htm
Headers: Accept: */*
Header: someParam=[dataVar]
=> Accept: */*
Header: someParam=
2
Post data: a=12&b=[dataVar] => a=12&b=3

Scripting Updates
You can find all supported functions in the Player object. You can also add your own functions to it to extend functionality.

Compare Files with Different Application
Use the ‘Write Files For External Compare’ option: if set to ‘True’ – SGM will sort files after record and execution to a special folder. SGM attempts to sort files with logic during record. If the user changes the logic after record, the execution logic structure will differ from the recording version.

Dynamic Variables Import/Export
Your can save dynamic variables to disk for further use in other scripts. Export writes all dynamic variables in a list to a file. Import will read all variables from the file and append to existing variables. This function is useful when creating sets of scripts using the same variable data.

Testing Webservices
The webservice can be called up via XML with a Soap envelop (and header created by the user) over HTTP, bypassing the Soap and webservices protocols by using an XML envelope to send the webservice request which runs on HTTP.

Security Certificate
If your web site is using an un-trusted security certificate, the SmarteLoad Agent may not register any traffic. The SmarteLoad Agent works without additional configuration with self-signed certificates and with certificates signed by a well known trusted authority. If a certificate is not self-signed and signed with un-trusted CA then additional configuration must be done. You will need to install appropriate security certificates in JRE supplied with SmarteLoad Agent according to http://java.sun.com/javase/6/docs/technotes/tools/windows/keytool.html

SmarteLoad Minimum System Requirements

Controller and SGM: In order to successfully run the SmarteLoad Controller and SGM, users need the following minimum system configuration:

CPU/Speed: Minimum 1 GHz, Pentium III Processor or faster.

Operating Systems: Microsoft Windows® XP SP2 or higher. Operating systems must be of fresh installation and not an upgrade on top of old installation or Windows XP home edition. Upgraded operating systems carry over incompatible applications and services to the new operating system installed.

Note: for both operating systems, all minimum requirements must be met to run scripts in SGM and a Synopsis in the Controller.

Memory: Controller: Minimum 1GB RAM. For large size applications or for running large size scripts, 1.5GB RAM or greater is highly recommended. For extensive Controller operations, 2GB RAM is required. SGM: Minimum 512MB. For large size applications or for running large size scripts, 1GB RAM or greater is highly recommended.

Hard Disk Space: Minimum 500MB for complete installation. Additional hard drive space must be present to support virtual memory requirements in addition to 1GB for general applications, temp directory and internet dynamic file storage.

Browser: I.E. 6 or higher, Netscape 4.7, AOL Browser, Mozilla 4.0 and FireFox.

Number of Connected Host Generators: Unlimited.

Maximum SimUsers: Depending on the license type, up to 10,000 SimUsers can run on the controller. Special controllers are customized for customers that require larger amount of SimUsers

Notes about the Controller machine

Depending on how many SimUsers will be running in the controller synopsis, the controller will consume more resources during large SimUser executions greater than 100 user simulations.
The controller machine requires more system resources to collect, filter and sort all the statistical data sent from the Host Generator Agent machines.
The use of many groups in the synopsis with different configurations and complex scripts will consume more CPU and Memory resources.
If any scripts are configured in the synopsis to run on the local Host Generator machine (localhost), the controller may run slower as more resources are dedicated to run the script on the host generator agent which resides on the local machine.
The use of the localhost to run any scripts within a synopsis should be temporarily only, to find if the synopsis is running properly with limited quantity of SimUsers on the localhost, before connecting to the Host Generators or for debugging purposes. Once proven, the script should be configured to a remote host generator machine that must be available to execute the synopsis. Running scripts on the localhost agent may skew test results and bottleneck the operations of the controller machine from processing the results properly.
To learn more about how the Synopsis configuration affects system resource consumption, refer to the Runtime Settings chapter in the Controller manual.

Host Generator Agent Minimum System Requirements

CPU/Speed: Minimum 1 GHz, Pentium III Processor or faster.

Operating Systems: Microsoft Windows® XP SP1 or higher, Windows® 2000 SP4.
Operating systems must be of fresh installation and not an upgrade on top of old installation or Windows XP home edition. Upgraded operating systems carry over incompatible applications and services to the new operating system installed.

Note: for both operating systems, all minimum requirements must be met to run scripts in SGM and a Synopsis in the Controller.

Memory: Minimum 1GB RAM. For large size applications, running large size scripts, or large quantity of SimUsers, 1GB RAM or greater is highly recommended.

Hard Disk Space: Minimum 500MB for complete installation. Additional hard drive space must be present to support virtual memory requirements in addition to 1GB for general applications, temp directory and internet dynamic file storage.

Browser: I.E. 6 or higher. Netscape 4.7, AOL Browser, Mozilla 4.0 and FireFox.

Maximum SimUsers: Depending on the license type, up to 500 SimUsers can run on one Host Generator agent machine. If more SimUsers are run per host generator agent machine, it may skew the test results that are sent to the controller.

Notes about the Host Generator Agent Machines

The quantity and balance of SimUsers that will be running on each Host Generator agent machine, will determine how smooth and successful the synopsis will run. User will need to check if the agent machine has the capacity to handle the number of users that are planned to run on it. To learn more about the Host Generator agent checks, please refer to the Host Management chapter in the Controller manual.
In general for a simple script with up to 10 web pages recorded in the script, each SimUser requires about 1 MB of memory.
For complex applications with greater than 20 pages recorded in the script, consider 2 MB+ per SimUser.
To learn more about how the Synopsis configuration affects system resource consumption refer to the Runtime Settings chapter in the Controller manual.

The minimum requirements mean the ability to install and run a simple script without issue, even though it may be slow. If the script is complex (containing many objects and commands) the requirements would be higher.

Please keep in mind that minimum specifications are always created with the intent of a single application running alone, and not several applications running concurrently – such as virus scanners, application utilities running in the background or monitoring tools.

Vanilla system is recommended: As a preferred platform for script development and execution, we recommend Windows® XP Pro, Windows Vista or Windows 7systems with vanilla configuration to minimize resource consumption by other applications. In addition, stop/remove running services that are not necessary during testing (i.e., email/messenger applications) unless email is a part of the testing requirement. Basic Microsoft Office applications compatible with the operating systems may be used. All applications other than AUT (Application Under Test) should be closed during test execution. Additional applications loaded into memory upon system startup that run services (i.e., virus scans, shield, automated system updates, etc.) may impede the test performance. It is recommended that systems being utilized for script development be dedicated to that purpose and not general office computing requirements.

We understand that other tools and application may be needed on your PC, however we recommend keeping it as “Vanilla” as possible. This also has an effect on the memory, for example, the more process and applications are running the more physical memory would be needed, even though the specifications recommend 1GB which would apply on a “Vanilla” System.