Execute Request Items
After you have added request items to the project, you can execute them and review results. You have several options to execute request items:
- Executing all selected request items; use menu option 'Run/Execute Selected Items' or press 'Ctrl+F5'.
- Executing all project request items; use menu option 'Run/Execute All Items' or press 'Ctrl+Shift+F5'
- Executing opened request item only; if particular request item is opened for editing and you want to execute only this item, click its corresponding action button and select option 'Execute' or press 'F5'.
- Executing items from execution group (only available in Professional Edition); if you have created execution groups, you can execute only particular execution group and all request items that are part of the execution group will be executed. To execute particular group, use menu option 'Run/Execute Group' or press 'Ctrl+(group_number)'. Group numbers are assigned automatically according to the order set for each execution group.
In execution window you can specify authentication data that should be included with the execution.
If you have specified authentication data in project properties, it will be set and used automatically.
You can, however, change this default authentication data here and it will be used for all further executions.
Changing authentication data in execution window does not affect authentication data specified in project properties
Default order when executing multiple request items
When executing multiple request items, you can select the order in which you want to execute them. The following options are available:
- Current sort order used in the main window; this will always execute selected request items in the order in which they are currently displayed in the main window.
- Specified 'Execution order' value; this will always execute selected request items in the fixed execution order value set for each request item. This option
guarantees that selected request items will always execute in the same order unaffected by the current sort order used in the main window.
Start executing immediately after the execution window is opened
Execution of the selected request items is performed in the special execution window where you have the option to start the execution, stop the execution, view results, etc. If this option is turned on,
the execution of the request items will start immediately after the execution window is opened. If turned off, you will have to start execution manually inside the execution window.
Execution window commands
The execution window contains a special execution toolbar. The following commands require further explanation:
- Specify authentication data; this command can be used to
specify authentication data if you are executing against secured
internet resources. If you would like to include authentication data with the requests, click 'Authentication' button and specify authentication data. The following options are available:
Note that authentication data can also be specified in project properties and will be automatically used when you will execute request items contained in the project. In such a case, you won't have to specify
authentication data manually in the execution window.
- Do not include authentication data.
- Use default credentials; Windows credentials of the user running the application will be used.
- Use the following credentials; credentials specified manually will be used.
Save execution data of selected request items to a file (only available in Professional Edition);
with this command you can export execution data to HttpMaster execution file (hmex extension) which can later be reopened in HttpMaster.
Multiple request items can be selected and exported to the same file. To open stored hmex file in HttpMaster, use menu option 'Open Execution File' available in main HttpMaster window.
Create PDF report with execution data of selected request items;
with this command you can export execution data to PDF. Multiple request items can be selected and exported to the same file.
If you would like to export only single execution to PDF, open execution details of the request item, select desired execution in the list and use export option available in the execution data toolbar.
Export execution results of selected request items to XML or JSON;
with this command you can export execution results to XML or JSON. Note that exported data does not contain complete execution data, but only information about particular execution outcome (succeeded/failed).
For more information on data model used for the export, check corresponding help topic.
Show previous 1000 requests; this command can be used for paging requests when request items has generated more than 1000 requests.
Show next 1000 requests; this command can be used for paging requests when request items has generated more than 1000 requests.
Stopping or pausing current execution
The execution of request items will continue running until all requests are
completed and will not stop even if the particular request is considered
unsuccessful (for example, the host name cannot be resolved or specific
validation has failed). This is useful if
you want to test particular requests that you know will fail and you want to
verify this. The execution of requests will be stopped only in the following
You can also pause and/or
resume execution at any time. To pause execution, click start button while the
execution is running; to resume execution, click start button while the execution is paused.
Execution is stopped by the user.
Application error not handled by the execution engine occurs (for example, there
are not enough system resources available to continue running).
Executing large number of requests
Execution engine stores request and response data in a
special temporary file in the application's execution folder (configurable in application options). In such a way, the
memory pressure is greatly reduced and it is possible to execute a lot of
requests during one execution session without consuming a lot of memory.
However, keep in mind that if a very large number of requests is executed and
request/response data is relatively big, the application could consume a lot of
These temporary files are deleted automatically by the application after they are no longer needed.
In project properties you can also specify not to monitor and store execution data. This will perform executions as usual, but
won't create any output files and will thus run much faster, but the execution data won't be available for
Copyright © by Borvid. All rights reserved.