Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In The Grinder, the script context includes a thread number, a process number, and a run number. I believe the thread number identifies a thread within a group of threads spawned by a worker process. The process number identifies a worker processes created by an agent. What is the run number? To put it another way, what actions result in a new run number?

share|improve this question
up vote 2 down vote accepted

From my experience with JMeter, when you run the load test the Virtual Users execute the same script over and over again for either the specified time period or the specified number of loops.

I would assume that each time the user (thread) executes the script (loop), it is counted as a run.

share|improve this answer
Yes, that agrees with what says about the grinder.runs property. – user246 Apr 19 '12 at 23:18

to be more precise, this is the number of times that call method has been called by grinder agent.

For example, line 16:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.