HAR Options

Scenario Builder – HAR Options Usage

Appvance Scenario Builder provides some options which can be used in order to get different data or results when the user executes a HAR test scenario. These settings can be set and located in the "Options" panel of the Appvance Scenario Builder.

Below are the different options:

• Connection resets marks the whole Test Case as a failure.

• Mark each request as a step.

• Validate response code against original HAR response code (Otherwise usual status codes will be expected).

• Show headers, requests, and responses in each Test Case execution output.

• Execute all HAR calls (even after a failure).

These options will allow you to establish some parameters settings different from standard Test Cases executing a HAR script. Users may find these options useful depending on what kind of test is being executed. i.e. If the user is testing a website, the user may want to have the default settings (unmarked options) for a HAR test, on the other hand, for a web service the user may find it useful to mark every single request as a step or validate the response code against the original HAR script.

Connection resets marks the whole Test Case as a failure

This option has to be used carefully depending on the desired results. The name of this option it's self-explanatory, it's used to mark the whole Test Case that's being executed as a failure when the connection resets.

Mark each request as a step

When this option is enabled, every single request retrieved from the HAR test is is being marked as a step–request key set instead of marking every request as a single request.

Also please make sure that this option is not used along with Autocorrelation.

Validate response code against original HAR response code

When enabled, the response codes received from the text case execution are going to be validated against the original HAR script response codes, otherwise, the usual response code for a request is passed as valid. Appvance Scenario Builder shows the response code for every request at the Test Case Execution tab in the results displays window as follows:

Show headers, requests, and responses in each Test Case execution output.

Meaning that for every request, exists a "parent" step with the same name of the request contained in that step. In the results display you may see these changes, the step has the timing for the request and the step request has the request size.

Execute all HAR calls (even after a failure).

Checking this option will let the HAR script run even if it encounters an error in any step.