The only thing I can see that we really need is something similar to threadindex. For example, when we run a 20 thread test as a load test in soap-ui, we use the context.ThreadIndex variable to change some values in the soap requests we're making (for example, say user1, user2, etc)
If we're creating a distributed test for loadui, we usually stick with running one thread per agent (and then we have 20 VMs each running an agent) So, we want to be able to access something to identify the agent number (say context.AgentNumber) which works similarly to the ThreadIndex.
Does this make sense?
Thanks for your response! SoapUI+LoadUI are great!