Help on Data Transfer and load testing

Hi - I do a lot of load testing where I work. I don't have scenario like yours... but, Is there a reason you seperate Login & GetTagsForDisplay in it's on TestCase? Why not put them all in one?

This might be a hard one to diagnose without the XML
Like is what is the relationship between the API's?
> Login - provides a token which I assume the "Sharing Properties" all need the token?
> TagID - obviously transfers also to "Sharing Properties" for the API's to use?

Apparently you have some successful runs - so it's working... but I usually tail the log on the server to see what's happening in the responses during my performance runs.

Just a side thought - Looking at your min/max - something is going on if you're only sending 2 threads w/ Randomization and it's taking 23.6 seconds max to "getToken", 16s for "instant", 10.8s for "hourly", that's pretty long for 2 threads. Could the host have timeout set low? Other traffic on the host while testing?

Rob

Ok, here goes nothing...

I try to put them altogether and guess what?... same problem.

I am sending you the xml file in hope for help.
The problem is, if I can get this to work as I hope it works, the company will not allow the tool purchase.

Cheers,
Suzy

Yellow,

anyone?.....

I looked at your xml and it looks basic and should work, but one question...

RefreshToken (sounds self explanatory - but you use the same token in the next API GetTarrifSimulationMeo). Why does the token get refreshed and then get used GetTarrifSimulationMeo?

Hi,

thank you for the reply.

That method it's for a keep alive connection mechanism.

I tried to run the full set of request wihtout that one and still does not work for more then 1 thread.

I really don't understand if I doing somenthing wrong or if the variables get messy between the threads.

Cheers
Suzy

It appears you are storing your properties at the TestCase level. I believe this is the problem. Read more here:
http://www.soapui.org/Load-Testing/load ... ution.html

Specifically...

The underlying TestCase is cloned internally for each configured Thread and started in its own context; scripts, property-transfers, etc.. will access a unique "copy" of the TestCase and its TestSteps which avoids threading-issues at the TestStep and TestCase level (but not higher up in the hierarchy; if you TestCase modifies TestSuite or Project properties, this will be done on the common shared ancestor objects).

Try storing your token and tag properties at a higher level like TestSuite or Project level.

Hi,

I've tried out several alternatives, including the ones you just sent.

The results ends up to be always the same. Just one thread and it works out just fine but if I change to 2 threads then errors in all the services. Just Login works well.

I'm sorry to bother so much but this is really important.

Cheers

Suzy

Hi!

What kind of errors are you getting from your services? Are you sure they are thread-safe?

regards,

/Ole
eviware.com