off-line testing made easy

[Doug Davis <dug@us.ibm.com>]

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