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:

Authentication data

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:

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:

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 cases: 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.

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 disk space. 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 review.