Execution Groups And Conditional Execution

Help Topics
Execution groups enable advanced execution scenarios with only selected set of project request items and also support conditional execution. Each project request item can be member of multiple execution groups.
Important
Do not confuse execution groups with display groups.

Create execution group

To create execution group, use menu option Project/Manage Execution Groups or press Ctrl+G and then follow this procedure:
  • Add new group in the left list and type its name.
  • Click Add button in the toolbar located above the right list; list of all project request items is opened.
  • Select and add all project request items that should be part of the group.
  • Optionally, change order of request items in the group with arrow buttons located in the toolbar above the list.
  • Click OK button to save group data to the currently open project.

Create execution group in the main window

Alternatively, you can create execution group directly in the main window with the following procedure:
  • Select request items that you would like to add to the new execution group.
  • Right click and select menu option Add Selected Items to Execution Group.
  • In the window that is shown, you have the following two options:
    • Create new group; if you would like to create new group, type its name in the corresponding field.
    • Add request items to an existing group; if you would like to add request items to an existing group, select desired group from a drop down list. If particular request item is already member of the selected group, it will be ignored.

Execute selected group

To execute particular group, use menu option Run/Execute Group in the main window menu or press Ctrl+(group_number). Group numbers are assigned automatically according to the order set for each execution group.
Important
Request items inside the group are always executed according to their order inside the group and are not affected by the current order of project request items in the main window or their specified execution order. Setting Execute request items in the main window by available in application options also does not have any effect when executing particular group.

Conditional execution

Conditional execution of request items enables execution of particular request item based on the execution result of some other request item in the same execution group. After you have created group of items and specified their order, you can set their execution condition and monitored items (if applicable). The following execution conditions are available:
  • ALWAYS execute; this option assures that item will always be executed. This is the default option and is automatically set when new request item is added to the group.
  • NEVER execute (skip); this option assures that item will never be executed, execution engine will always skip it.
  • Execute if monitored item SUCCEEDED; this option assures that request item will be executed only if some other (monitored) item was executed successfully. This option requires that monitored item is also specified from the list of other items in the group.
  • Execute if monitored item FAILED; this option assures that request item will be executed only if some other (monitored) item was not executed successfully. This option requires that monitored item is also specified from the list of other items in the group.
  • Execute if monitored item was SKIPPED; this option assures that request item will be executed only if some other (monitored) item was skipped during the execution. This option requires that monitored item is also specified from the list of other items in the group.
Important
When specifying monitored item, make sure that all monitored items will be executed before the items that are monioring them. For example, if you have specified that item 'X' should monitor item 'Y', assure that item 'Y' will be executed before item 'X' in the group. HttpMaster will notify you of such errors when you will try to save group data.

Conditional execution and chaining data

If some item is skipped during the execution and next item should use skipped item's data for chaining, data of the last executed item will be used instead. For example, assume that you have three items in the execution group and third item should use some data from the second item. If during the execution second item was skipped (but first item was executed), third item will use data of the first item to obtain chaining data because second item (that should normally be used) was skipped.

Open all group request items in the basic request window

To open items from particular execution group in the basic request window, click Tools/Open Group Items As Basic Request menu option or press Ctrl+Shift+(group_number) and basic request window will be opened with the execution data of group items (each group request item will be opened in its own tab). Additional project items can also be opened when basic request window is already open. To open additional project request item as basic request, double-click the desired item in the list available in the right part of the window. New tab will be created with the execution data of the selected request item.