Re: [ebxml-iic] your KorBIT comment

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Boonserm (Serm) Kulvatunyou wrote:

> The KorBIT folks say that they cannot exactly identify the point of 
> failure or non-conformance when the test framework relies on the same 
> type of communication both for the Test Action/Command and the test 
> message. My guess is what could happen is when a failure or 
> non-conformance occurs TD cannot exactly sure if the failure occurs at 
> the Test Service level or MSH level b/c of this indirection b/w the TD 
> and TS.
>  
> I am not sure if this makes sense. I think I am trying to expand from 
> little discussion with them here.

mm1: Serm, does this indicate we need: To have error checking on 
interaction points in the testing process that can isolate occurrences? 
Is this handled by an outside adapter or within the test service itself 
(or any other test component for that matter)? Or, could this be handled 
by indirectly by logging functions on execution points within the test 
driver and/or service to assist in troubleshooting if failure occurs? 
Maybe it is both.