You create, edit, debug, and run scenarios (test cases) in the Scenario View.
From the console's intuitive graphical user interface (GUI), all actions required to set up the environment, define scenarios and control the load execution are performed. The console is the single point of control in a PureLoad runtime environment.
The console is designed to be intuitive and easy to use. Its layout using tabs ("Views") guides a tester from setting up the execution environment, defining the task scenario(s) of tasks that shall be executed, to the final stage where the actual results can be analyzed.
The console has four tabs for setting up and analysis of:
Use the console to setup your load servers and create virtual clients (worker threads). This is further described in the chapter "Workers View".
Results are presented in real-time during execution and are also displayed after execution in the console. Results can be saved and reused for comparison in a later run using the same environment variables. This is further described in the chapter "Results View".
The Monitor view is used to control what servers and resources that are being monitored. PureLoad supports monitoring of servers resources during the execution of a load test. This is further described in the chapter "Monitor View".
Here scenarios (test cases) are created using the GUI. It includes a full blown scenario debugger having single step, break points and response introspection. No programming skills are required to build test cases! Lets dig into this part a bit deeper!
The Scenarios view is central for defining and executing your tests. The scenario view contain a graphical user interface with functionality for writing and debugging test cases (scenarios), for putting on load distribution as well as executing tests.
PureLoad comes with support for a large set of standard operations, called tasks. The tasks have a number of set protocol parameters that can be set, which minimizes the risk of coding errors during the test design.
There are three types of standard tasks.
The first is basic tasks, like setting variable(s), extracting data from a response, verifying response, setting sleep time, etc.
The second is web (HTTP) tasks for operations like sending HTTP GET, POST, PUT, DELETE, setting arbitrary HTTP header values or cookies. Encryption using SSL/TLS is supported as well.
Dynamic Web applications can be handled using the third type of tasks. These are extract tasks that operate conditionally on textual results or outputs from previous tasks. For example, extracting data from an XML, can be used to handle dynamic features of a web application. Standard session handling techniques, such as cookies and URL-rewriting are supported too.
A scenario is more or less equivalent to a test case.
In the scenario editor you group a number of tasks to perform actions, for example opening a browser – reading a web page – choosing a product in a web store, etc.
Scenarios are often designed so that they can be parameterized and repeated many times with different data. Each task parameter value can refer to parameter generators to have the actual value generated during the test.
A scenario is the lowest level of what a virtual user (thread) executes.
There is a scenario debugger included to quickly test and verify each individual task in a scenario.
This is done by single stepping through each task in a scenario. Detailed execution results and execution log is shown for each task.
From the scenarios tab you also choose from six distribution types (example burst and linear increase) for your scenario, for how long and with which intensity it should run, and also start monitoring and the execution of the scenario. With this you can easily put together a traffic mix that simulates the traffic patterns in your environment.