Run Test Scenarios in Sequence

Products

• BlazeMeter

Issue/Introduction

A YAML file defines multiple scenarios that need to be executed in sequence.  The following section was added to the YAML file to assure that the scenarios are executed sequentially:

 

modules:

  local:

    sequential: true

 

When this YAML file is uploaded to a BlazeMeter API Functional test, all of the defined scenarios are executed in parallel instead of sequentially

Environment

Release : SAAS

Component : BLAZEMETER FUNCTIONAL TESTING

Cause

The sequential option is only valid for local Taurus test executions.  It is not possible to specify this option for a cloud execution (replace local with cloud in the modules section).

Resolution

There are 2 potential resolutions:

1.  Add appropriate delay options to each scenario in the execution section.  The delay values added should account for the time it takes to get all required engines up and running and the start command to be received, as well as any configured think-time added to individual scenarios.  For example:

execution:
  - scenario: SCENARIO_1
    locations:
      harbor-59465fcde4d6a240d97b23c6: 1

    delay: 20s
  - scenario: SCENARIO_2
    locations:
      harbor-59465fcde4d6a240d97b23c6: 1
    delay: 30s
  - scenario: SCENARIO_3
    locations:
      harbor-59465fcde4d6a240d97b23c6: 1
    delay: 1m
  - scenario: SCENARIO_4
    locations:
      harbor-59465fcde4d6a240d97b23c6: 1
    delay: 1m45s

2. Convert each of the individual scenarios in the YAML file to an API Monitoring (Runscope) test, then create an API Monitoring test that executes each of the API Monitoring scenario tests in the desired order.