Advanced Options

Help Topics
Advanced request item data can be managed in the 'Advanced' tab of the request item properties. You can specify the following options:
  • URL encoding of parameter/chaining values; with this option you can define how you want to URL encode values of used parameters and chainings. You can enable URL encoding, disable URL encoding or inherit the value from project properties. For more information, see corresponding topic.
  • Include specified authentication data with executions of this item; with this option you can define whether any authentication data that was specified in execution window will be included with all requests of this item. In short, this option enables/disables authentication for the request item.
  • Include item when executing selected/all/group in the main window; with this option you can include/exclude particular item from execution in the main window. This options only affects execution of selected items, all items, or group items; you can still execute item separately when it is opened for editing ('Execute Opened Item' menu option).
  • Include item when executing project with command line application; command line application does not allow user to specify which project request items should be included with execution; with this option you can include/exclude particular item for command line execution.
  • Order of request item executions; if request item is using project parameters that produce multiple values, then request item will be executed multiple times. For example, if you have created project parameter 'parameter1' that produces values 1 and 2 and use it as query string parameter value in URL of request item, this request item will be executed twice; once with the value 1 and once with the value 2. If you are using multiple parameters that produce multiple values, then request item execution count will be determined according to the cartesian product value (e.g. two parameters with three values will produce nine executions). Also, when using multiple parameters with multiple values, the order of processing each parameter values matters and the following options are available:
    • Start with the first used parameter and continue to the last used parameter.
    • Start with the last used parameter and continue to the first used parameter. This is default for each new request item.

    Example
    We define two project parameters 'parameter1' and 'parameter2' that produce the following values:
    • parameter1 produces 1 and 2.
    • parameter2 produces 3 and 4.

    Now we include both parameters as query string parameter values in request item URL:
    www.httpmaster.net?x={parameter1}&y={parameter2}

    When executing this request item, four requests will be executed, but the order of used parameter values will differ according to the parameter execution order setting:
    • When set to 'Start with the first used parameter and continue to the last used parameter', execution order will be the following:
      • www.httpmaster.net?x=1&y=3
      • www.httpmaster.net?x=2&y=3
      • www.httpmaster.net?x=1&y=4
      • www.httpmaster.net?x=2&y=4
    • When set to 'Start with the last used parameter and continue to the first used parameter', execution order will be the following:
      • www.httpmaster.net?x=1&y=3
      • www.httpmaster.net?x=1&y=4
      • www.httpmaster.net?x=2&y=3
      • www.httpmaster.net?x=2&y=4

    This setting is not relevant if request item produces only a single execution or if request item execution count is manually set. For more information, see Manage Execution Count topic.

  • Pre-execution action; specify external action that will be executed before execution of request items will start. For more information, see corresponding topic.
  • Post-execution action; specify external action that will be executed after all executions of request items will complete. For more information, see corresponding topic.