PureTest GUI
PureTest 5.2 January 2015	http://www.pureload.com support@pureload.com

• The PureTest GUI
  • Starting
  • Overview
  • Menu Bar
  • Tool Bar
• Tool Properties
• Save and Load PLC Files
  • Save a PureLoad Configuration File
  • Open a PureLoad Configuration File
  • Import a PureLoad Configuration File 
• Tools

The PureTest GUI

The PureTest graphical user interface (GUI) is used to design scenarios and the main part consists of the Scenario Editor, i.e. the editor used to manage scenarios, task parameters and parameter generators as well as test and debug created scenarios. This is described in detail in the Scenario Editor chapter.

Starting

How to start the GUI depends on the operating system you are using:

• Windows
  Locate the PureTest sub menu in the Start menu and select the PureTest entry in the sub menu.
• Linux/Unix
  Open a shell and change directory to the PureTest installation directory. Execute the bin/puretest program.
• Mac OS X
  Double click on the puretest application.

Overview

When PureTest is started the scenario editor is displayed:

In addition to the the Scenario Editor, PureTest also includes various controls to load and save configuration files, starting other tools etc.

Menu Bar

The menu bar groups all operations in menus. Most of them are context sensitive and are enabled depending on the current state in the GUI.

File menu

The file menu includes operations to load and save PLC (PureLoad Configuration) files.

Edit Menu

The edit menu includes operations to alter the current context. I.e cut/copy/paste objects, create new objects and to reorganize object. Objects here differs from the current context; scenarios, sequences or tasks.

View Menu

The view menu is used to show debug info etc.

Task Menu

The task menu is used for operations on tasks, not included in edit or view menu.

Tools menu

Use the Tools menu to start the tools included: HTTP Recorder and Web Crawler.

Help Menu

The help menu includes functions to browse the documentation and related information.

Tool Bar

The tool bar contains a subset of the menu bar operations that are frequently used. These buttons are context sensitive and generally adopts the behavior (functionality) according to the current state.

Tool Properties

The Tool Properties dialog is displayed by selecting the File->Properties menu choice. This dialog is used to control a few settings that are saved to a file on disk between invocations of PureTest.

The properties are:

Look and Feel

Look and Feel of the user interface. Not all options may be valid on your platform. I modified the console must be restarted for all Look and Feel settings to be applied.

Debug Destination

Where system debug and error messages will be displayed. Normally and the recommended setting is to use the default setting Debug Window to allow debug information and error messages being displayed in the debug window.

Save and Load PLC Files

A PureTest configuration contains definitions that may be used to repeat tests between sessions. The configuration saved into a PureLoad Configuration (PLC) file with .plc as the suggested file extension.

The PLC file is a XML file that is common between the tools in the Pure Performance Suite. This mans that any test scenarions you have created using PureTest can be used both in PureLoad and the command line utility for running Scenarios (read more about Scenario Runner).

The PLC file includes the following information:

• Task Types
  Save any custom task types.
• Scenarios
  Save the scenarios that have been set up in the scenario editor.
• Parameter Generators
  Save the task parameter generators.

Save a PureLoad Configuration File

There are two options to save a configuration file:

• File->Save As menu choice or the button in the toolbar
  Save the current configuration as a new file or overwrite an existing file.
• File->Save menu choice or the  button in the toolbar
  Save the current configuration in the currently loaded file (the file name is shown in the window title bar of the PureLoad Console) or the same behaviour as Save As if there is no current file.

This dialog is displayed independently of which save option that is used.

Specify here the pieces of the session that shall be saved into the file.

Open a PureLoad Configuration File

There are two ways to load a PLC file:

• File->Open menu choice or the  button in the toolbar.
• File->Open Recent where the recently loaded files are listed.

This operation loads all parts of a PureLoad session that has been previously saved. It is not possible to select what parts (Workers, Task Types, Scenario or Parameter Generators) to load. The name of a successfully loaded PLC is presented in the window title of the PureLoad Console. The indicated file is the current PLC file and it is in this file that any succeeding File->Save operations will be done. In the case when no PLC file is loaded (or none has been saved in the current session) the PureLoad header will show a [No file loaded] message.

The file menu will list the latest loaded PLC files with the most recently used listed first. If a PureLoad session is saved then the newly saved PLC file will be listed first in the menu.

Import a PureLoad Configuration File 

The following dialog is displayed when importing an existing PLC file:

The import dialog first checks the specified file and then only lists those items available in the file.

Tools

The tools menu in PureLoad Console contains choices to quick launch the following applications:

HTTP Recorder

The HTTP Recorder is used to capture HTTP requests between a web browser and a web application in order to easily create PureLoad scenarios. See Testing Web Applications for more information.

Web Crawler

The Web Crawler is used to examine a static web structure and present errors and various statistics. PureLoad scenarios can be created from the resources that are found. See Testing Web Applications for more information.