ws-rx-implement message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ws-rx-implement] off-line testing made easy
- From: Doug Davis <dug@us.ibm.com>
- To: Paul Fremantle <paul@wso2.com>
- Date: Mon, 27 Feb 2006 10:29:47 -0500
Actually, one thing I'd also like to
include is a unique ID for each scenario - then a server can optionally
include some kind of UI that would allow the client to examine the logs
(or soap messages) associated with that particular test. There have
been times when it was only thru looking at the RMD's soap messages that
I was able to determine what was going on - and it would be nice if someone
could do that kind of debugging (of their side :-) without having
to wait for me to check my email. Obviously, all of this is optional
but I think it might provide some value.
thanks,
-Doug
__________________
That can work too - but to be honest I get annoyed when
I have to go searching around for all of the various URLs that one particular
impl has up - its a lot easier when I can just point my test client at
one url and let it go. Now, if we could all agree on using the query string
part of the URL to pass these flags then that would be ok too :-)
thanks,
-Doug
Paul Fremantle <paul@wso2.com>
02/27/2006 10:02 AM
|
To
| Doug Davis/Raleigh/IBM@IBMUS
|
cc
| ws-rx-implement@lists.oasis-open.org
|
Subject
| Re: [ws-rx-implement] off-line testing made easy |
|
Doug
How about having multiple configured versions of the
same service
deployed with unique URLs?
Paul
Doug Davis wrote:
>
> For some of the scenarios we're looking at testing
during the interop
> it might be hard for us to test them off-line
without some kind of
> manual involvement. For example, how is
the RMD supposed to know if
> it should accept or reject the Offered sequence?
I'd really like for
> us to be able to test all of the scenarios automatically
w/o requiring
> people to manually change some config setting.
Off hand I can think
> of two options:
> 1 - include some SOAP header that indicates the
scenario # and then
> the RMD/Server can then act accordingly
> 2 - include some "testing directives"
in a SOAP header. Similar to #1
> but aren't tied to our scenario doc.
> Any other ideas?
>
> I'm partial to #2 then people can try scenarios
that may not be
> included in our scenario doc. So what do
people think of defining a
> SOAP header (just for our testing purposes only)
that include
> directives like:
>
> <RMDirectives>
> <acceptOffer> true|false </acceptOffer>
> <useOfferedSeq> true|false </useOfferedSeq>
<!-- even when > Offered/Accepted, RMD creates its own seq -->
> </RMDirectives>
>
> Are there other options people can think of passing
along? I'm
> thinking that these may need to be passed along
on every message (and
> not just the createSeq) so that people have the
most flexibility in
> their implementations.
>
> Thoughts?
>
> thanks,
> -Doug
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://feeds.feedburner.com/bloglines/pzf
paul@wso2.com
"Oxygenating the Web Service Platform",
www.wso2.com
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]