Forum Discussion
JimL
15 years agoContributor
Hi,
I think that I've figured out why I was seeing the same "Id" for several test case runs in a load test.
It was because I had "Threads" in the load test set to 20. That would cause 20 requests to have the same "Id".
When I set "Threads" to 1, I got unique "Id" values.
This does, however, reduce the overall TPS of the load test.
I'm guessing that in a load test, the test cases are running in individual thread, and that the properties for each thread are separate from each other. Since the properties my Groovy script is using are all test case properties, I get the repeated "Ids".
I'm wondering if there's another 'level' where I could put the properties (e.g., the test suite level) that would allow all the threads in the load test to use the same properties, so that I could have more than 1 in the "Threads" setting, but still get unique Ids?
I'm guessing that the answer to that is "no" because then ALL of the properties that my Groovy script uses would be shared among all the threads in the load test, and things would get messy (i.e., it would break things)??
Jim
I think that I've figured out why I was seeing the same "Id" for several test case runs in a load test.
It was because I had "Threads" in the load test set to 20. That would cause 20 requests to have the same "Id".
When I set "Threads" to 1, I got unique "Id" values.
This does, however, reduce the overall TPS of the load test.
I'm guessing that in a load test, the test cases are running in individual thread, and that the properties for each thread are separate from each other. Since the properties my Groovy script is using are all test case properties, I get the repeated "Ids".
I'm wondering if there's another 'level' where I could put the properties (e.g., the test suite level) that would allow all the threads in the load test to use the same properties, so that I could have more than 1 in the "Threads" setting, but still get unique Ids?
I'm guessing that the answer to that is "no" because then ALL of the properties that my Groovy script uses would be shared among all the threads in the load test, and things would get messy (i.e., it would break things)??
Jim