The definition of the injection profile of users is done with the inject method. This method takes as argument a sequence of injection steps that will be processed sequentially. A simulation can contain only one setUp [/code] method, the setUp method can have multiple inject profiles in it.The definition of the injection profile of users is done with the inject method. This method takes as argument a sequence of injection steps that will be processed sequentially. A simulation can contain only one setUp [/code] method, the setUp method can have multiple inject profiles in it
Define scenario A scenario can be defined as a Scala variable or Scala function. The following scenario is defined as a Scala function which takes a step, pacing, and duration as arguments.
If you arrived at this page directly, please go through this post first. It explains some basics, how to define HTTP protocol configurations and headers which will be used while building the test scenario along with the feeders and HTTP requests described in this post. Step 3: Define Feeders Feeders resemble parameter files in Loadrunner … Continue reading Gatling Simulation from Scratch – Feeders and HTTP Requests (Part 2 of 4)
I had an opportunity to use Gatling for load testing in one of my recent projects. My learning curve for this tool was very steep and I found it very elegant, highly capable and easy to use. So thought I'll share my learnings with everyone. Gatling is an open-source load testing framework based on Scala, … Continue reading Load Testing Using Gatling – Gatling Simulation from Scratch (Part 1 of 4)
Problem statement: Your performance regression scenario contains 20 different Loadrunner scripts. You run this scenario a number of times in a given release.For simplicity, let’s assume that all scripts are developed using web services protocol. There may or may not be any changes to the scripts but version of the service endpoint changes a lot … Continue reading Modify Common Parameters in Multiple Scripts Using Additional Attributes
Transaction per second (TPS) is the number of transactions executed per second. In other words, it can be calculated based on how many transactions are executed over a certain duration of the test and then calculate it for a second. For example, if a vuser executes 6 transactions every minute, then the TPS would be … Continue reading Loadrunner: Understanding Transaction Per Second (TPS)