Hi
I cant see straight on how this could be solved with threads, what you (for example) could do is a TestCase which contains:
1) A login request
2) A browse request (if it requires a login)
3) An add item request
and then insert groovy steps between these that loop back in X % of the executions (using Math.random() ), thus simulating a increased load on these steps in alignment with your measurements.. ie
if( Math.random() < 0.4))
testRunner.gotoStepByName( ... )
would add another request in 40% of the executions (cumulatively though, so you would probably need to play with these values to get a good balance..)
Hope this helps!
regards,
/Ole
eviware.com