by technology » Tue Jul 08, 2008 1:57 pm
This may be more difficult that you think, but let's try this
idea on for size. If this notion is off the mark, then please
disregard.
You want to validate (presumably from the user perspective)
certain properties of how web services behave, e.g according
to a WS-Notification of WS-Performance description. For
example for WS-Performance that might be the amount of time
(average time) a particular service takes to process a
particular request.
Further, let's suppose you have some web page somewhere that
reflects this notification and/or performance standard
somehow. This could be by (for performance) having a "go"
button and some kind of response page that indicates
completion of the service. It ought to be that you can see
from that page whether or not the required standard is met, or
possibly read values that are of interest.
You might think of this page as the "WS-Performance Test Page"
because it is a kind of "test bed" for the particular service.
So if you can bring out to your web service test page some
facts revealing the data you want to test, then you can apply
well-known web page performance and validation methods to it.
You will have "reduced the problem to on that can be handled
with a previously known solution."
Which leads us to suggest, of course, that you might try the
eValid solution, which can drive, validation, and measure
response times of all kinds of web browser enabled
applications from an instrumented IE-clone browser. Including
your web services testbed page and the information about your
candidate service that it exposes.
eValid Tech Support Team
