I would be interested in hearing what others may be doing to load test
WSE enabled web services. I have been searching most of the morning,
and seems to have found a few options, none of which I am completely
sold on yet.
The first answer seems to be use Parasoft soa test. In fact, searching
the newsgroups thats the only real hit that comes up on load test wse
that I could see. This is certainly an option, but I would rather try
to use tools we currently have access to first.
My next thought was ACT/Whidbey load testing. From what I'm seeing, we
could turn off replay detection, and relatively quickly get ACT testing
the web services. With whidbey, we might even be able to get the WSE
proxy class to work, and do load testing against a direct "fixture".
The whidbey option seems like the most attractive right now.
Other thoughts were to create a simple web or windows app that will
work as a fixture, and then have automated tools consume those
wrappers. That's probably the last option I would want to exercise as
the numbers would be obviously skewed.
Does anyone have any input on this? What are people currently doing
that they are happy with?
Thanks in advance for any input!
Aaron Junod
tranqy at gmail i dont want spam dot com
Aaron Junod - 20 Jul 2005 18:48 GMT
Although I'd still be very interested in others input, I think we have
worked out a solution that will at least get us the metrics we are
looking for now.
If possible, I wanted to use the Whidbey testing tools, since that is
where we are going, and it's easier to suggest moving forward.
Of course, wse2 sp3 isn't directly supported by whidbey. I have read
they can work together, but the samples I saw were from the server
side. I was looking for the client side. My first attempt was to bring
my existing proxy class into my new project. The existing proxy class
did not want to compile in 2.0, though, since it seems a few references
may have moved (honestly, I didn't do much analysis here. Once the
proxy class didn't build, I moved on as I didn't want to alter the
proxy class if I could avoid it).
The next attempt worked well, though. 2.0 has no problem making calls
into 1.1 assemblies, so I simply made a wrapper around a couple
services, and called the wrapper from a whidbey unit test. Golden.
Now load testing. I run through the wizard which is cake. The IDE lets
you choose a unit test to load test. When I tried to run the test I got
an error about a missing DB, though. The msdn that ships with beta2
didn't seem to have this content yet, but msdn2 had the links on
setting up the db (links below). Once I did that, my first load test
was running away.
I really like this solution since we have complete control. No static
list of messages, my unit test makes the call. I plan on implementing a
special unit test that will make the calls with a round robin set of
params from a config file. And best of all, I don't need to ask my
manager for more money for a testing suite.
Setting up the test db
http://lab.msdn.microsoft.com/searchbeta/Redirect.aspx?title=How+to%3a+Configure
+SQL+Server+for+your+Results+Store&url=http://msdn2.microsoft.com/library/ms1826
00(en-us,vs.80).aspx
Setting up the IDE to use that new store
http://lab.msdn.microsoft.com/searchbeta/Redirect.aspx?title=Saving+and+Publishi
ng+Test+Results&url=http://msdn2.microsoft.com/library/ms182498(en-us,vs.80).asp
x
Aaron Junod
tranqy at gmail I don't like spam any more then before dot com