Given a multi-level closed model loadtest can gatling decide to continue or stop after the first level based on the assertions?

Gatling (Open-Source)
1

Suppose I want to a multi-level closed model load-test that will look like this:

image
source

and I have some quality criteria implemented as assertions:

     global.responseTime.max.lt(70000), // any max. response time

      details(scenario1).responseTime.max.lt(calculateReqEngResponseTime().toInt), // sum max. response time
      details(scenario1 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario1 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario1 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario1 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario1 / "action").responseTime.max.lt(responseTimeaction),

      details(scenario2).responseTime.max.lt(calculateBusAdminResponseTime().toInt),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction), // Intland Default Project
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario2 / "action").responseTime.max.lt(responseTimeaction),

      details(scenario3).responseTime.max.lt(calculateLeadEngResponseTime().toInt),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario3 / "action").responseTime.max.lt(responseTimeaction),

      details(scenario4).responseTime.max.lt(calculateTestEngResponseTime().toInt),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),
      details(scenario4 / "action").responseTime.max.lt(responseTimeaction),

      global.successfulRequests.percent.gt(95),
      global.failedRequests.percent.lte(2)

is it possible for gatling to decide to continue to ramp-up onto the next level based on the assertions of the previous level? I presume the assertions are run at the end of the test, and not sure whether they can executed per level.

2

We plan to have a similar feature, but for Gatling Enterprise: something similar to assertions, applied to the last 5s sliding time window, to decide to abruptly stop the test.

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.