Design, debug, and run your test cases using the PureTest Console.
From the intuitive graphical user interface of the PureTest application you create, execute, and analyze your test cases (test scenarios).
No programming skills are required!
Scenarios can be automated and/or re-used for building traffic in load test.
The console is designed to be intuitive and easy to use.
The console has three main tabs. The Scenario Editor, Task Types, and Parameter Generators.
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.
PureTest 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. All tasks are described under the tab "Task Types".
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.
Using our API you can write your own custom tasks. The custom tasks will be seamlessly integrated with the system tasks.
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.
Scenarios are often designed so that they can be parameterized and repeated many times with different data. The parameter generator mechanism makes this possible. Each task parameter value can refer to parameter generators to have the actual value generated during the test.
There can be internal parameters that are used within a scenario and external parameter files that can be used for test automation.