ThreadIndex
ThreadIndex in soapUI and loadUI is not the same. soapUI (3.6.1) starts with 0, loadUI (1.0.1) starts with 1. i think... scripts aren't working correctly because of this.
Forum Discussion
We can work around the fact that the loadui threadIndex starts at 1 in our loadtest code for now.
When distributing a load test to multiple loadui agents, how does the threadindex vary? Does it go from 1 to N, n being the number of loadui agents there are? This is the expected behavior. If it doesn't act like this, how can you (from a context. variable) determine which loadui agent you are on?
Thanks!
When distributing a load test to multiple loadui agents, how does the threadindex vary? Does it go from 1 to N, n being the number of loadui agents there are? This is the expected behavior. If it doesn't act like this, how can you (from a context. variable) determine which loadui agent you are on?
Thanks!
