I am running a recorded Test Plan in which, I have assigned 5 different users to the Thread Group, with a Ramp-up period of 5 and Loop Count of 1.

This is what happens after executing the script:

The test runs without errors and when I verify the results in 'View Results Tree' listener, I find all users got successfully executed without any error, but when I verify the same in system; only 2 or 3 users got registered. I deleted the registered users and ran the script again, and this time too only 2 or 3 users got registered (this time different 3 users out of 5 got registered) i.e. user selection for registration is random, but count remains only 2 or 3 out of 5 users.

I don't understand

  1. What can be the possible reason for this behavior of my test?
  2. Why my Test Plan is not registering all the 5 users?

I've checked the resource utilization on my machine too, but they were fine, no problems with that.

  • Try once more but this time add a Timer (Constant Timer) in between the user register requests. This should make your script register all 5 users. jmeter.apache.org/usermanual/…
    – Dhiman
    Commented Mar 8, 2016 at 14:17
  • I've had a similar issue in the past. Bear in mind that jMeter will succeed if the message is sent successfully, it doesn't check to ensure that the message is correctly processed. It could be that the request is being sent but something further down the line is failing, this will be invisible to jMeter. It may be possible to queue up your tests - "Create user / Check for user creation" to catch this kind of issue. Just keep in mind what a jMeter "Pass" is telling you, don't assume a pass is always a success.
    – Dave M
    Commented Apr 7, 2016 at 15:52

2 Answers 2


This may have to do with the way your application is built. Apparently, your application doesn't throw an error (validation error) when the duplicate credentials are used to register. Ideally, there should be an error (4xx) in such cases. Just because your script got executed and there is all green in the View Results in Tree listener doesn't mean Users got registered. Do check the request and response in the View Results in Tree listener.

Alternatively, you can try hitting the same endpoint (URL) using a Rest Client tool like POSTMAN. If the endpoint gives 200 or 201 on use of duplicate credentials for registration, then ask the developer to fix it!



It really depends on what queries you are executing to create those users. If the queries are creating the same user all 5 times, using 5 threads, then the threads could over-run each other. I think as long as you are careful to track which thread is doing what, you shouldn't have a problem.

  • I'm using 5 diferent users and 5 thread. I include a Debug Sampler and each thread is getting the right user and password...
    – karina
    Commented Jan 26, 2015 at 14:32
  • There isn't really a way for anyone to give a good answer to your question. One thing is for sure, if you packet traced your tests using Wireshark, then you'd probably discover what the issue is.
    – djangofan
    Commented Jan 26, 2015 at 15:40
  • thanks @djangofan I'll try with Wireshark and let you know about...
    – karina
    Commented Jan 26, 2015 at 17:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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