Parallel execution of multiple scenarios

gatling
Hans Holzbart picture Hans Holzbart · Dec 5, 2016 · Viewed 17.8k times · Source

What ist the best practice for parallel execution of multiple scenarios? For example 30% Users execute scenario1 and 70% users scenario2.

Is the code below the right way or is it better to have one scenario with contional executions of REST calls?

class MySimulation extends Simulation {

  val userIdsData = csv(userIdsCSV).queue



  ...



  val scenario1 = scenario("Scenario 1")

    .feed(userIdsData)

    .get(...)



  val scenario2 = scenario("Scenario 2")

    .feed(userIdsData)

    .get(...)

    .post(...)



  setUp(scenario1.inject(rampUsers(30) over (ramp seconds))

      .protocols(HttpConfig.value(baseURL)),

    scenario2.inject(rampUsers(70) over (ramp seconds))

      .protocols(HttpConfig.value(baseURL))

  )

}

Answer

Pritam Banerjee picture Pritam Banerjee · Dec 5, 2016

Whatever you are doing is absolutely fine.

The way you are running the setup you will see that the requests are running in parallel.

Related questions

Gatling - Log body of request in simulation.log or console

I would like to see what is in the body of the post that I am sending in my script. In fact, I would like to see the request, request body and response. From looking at the docs and the …

Read More
Parsing a Json response returned to Gatling

I am trying to parse a json response returned to gatling by the server. My response from server is: SessionAttribute( Session( GetServices, 3491823964710285818-0, Map( gatling.http.cache.etagStore -> Map(https://api.xyz.com/services -> ), gatling.http.…

Read More
Modularising scenarios to run in sequence using Gatling

I'm trying to modularise a series of performance tests in Gatling. Several of the tests execute the same initial path through the pages, so I thought that I could break them down into a series of scenarios, each scenario being …

Read More