Next in thread → Next in month →

RE: [ebxml-iic-interop] Interop spec V0.8 consolidated with testscripts

From
Jacques Durand <>
Date
2003-02-11T01:23:47+00:00
ID
Thread
RE: [ebxml-iic-interop] Interop spec V0.8 consolidated with testscripts
Title: Interop spec V0.8 consolidated with test scripts

Thanks 
for comments Eric, 

 

Only 
answering 4.1.x here:

 

Steve: 
do you think we should "parametrized" more explicitly our test 
suite,

e.g. 
we define some "suite parameters" for the entire test suite:

$protocol = {HTTP, SMTP,...}

$protocolversion = "1.1"...

 

So we 
use these when we specify the CPA data, as well as inside the test 
case:

So instead of saying , in synchronous test 
cases:

"This test case is for synchronous transport 
only (HTTP)."

we could 
say:

"This test case is for synchronous 
transport only (e.g. $protocol = 
"HTTP")."

If we 
do so, then we can give a parameterised name to our suite MS-BIP($protocol, 
$protocolversion)

and we 
would talk of MS-BIP(HTTP, 1.1) instead of 

MS-BIP-HTTP like we 
do now.

 

Thoughts?

[Jacques Durand] 

 -----Original 
Message-----
From: Eric VanLydegraf 
[mailto:]
Sent: Wednesday, February 05, 2003 1:29 
PM
To: ''
Subject: RE: 
[ebxml-iic-interop] Interop spec V0.8 consolidated with test 
scripts

  
A 
  quick read through - sorry :( didn't study the tests themselves but here are 
  some comments.

  
 

  
line 
  25 - like Test Framework recommend a placeholder URL so that when we do have 
  an Errata to go with the document we don't need update this document 
  itself.

  
 

  
line 
  87 (Section 1.1.3)

  
Recommend [STANDARD] format style used in many OASIS 
  standards documents e.g. [MIME]

  
 

  
Section 4.1.x - Protocol should be a variable instead 
  of 'HTTP 1.1' 

  
The 
  previous section spoke of parameterized BIP for SMTP,HTTP

  
 

  
Appendix A.

  
Is 
  "Point-to-Point" or "Hub" test harness specific to ebXML Messaging 
  interoperability or should this be moved

  
to 
  Test Framework as implementation options of Test Driver in "interoperability" 
  mode ?

  
    
-----Original Message-----
From: Jacques Durand 
    [mailto:]
Sent: Monday, January 27, 2003 
    3:23 PM
To: ''
Cc: 
    ''
Subject: [ebxml-iic-interop] Interop spec 
    V0.8 consolidated with test scripts

    
All: 

    
Here is a consolidation of latest spec draft with 
    minor edits + the test scripts that Mike sent out 
this morning. I will get it posted on our site. 

    
The main update I see that is needed: enhance the 
    CPA data sets (see 4.1.2): should reflect set-up for 
each party, as pointed out in earlier mail (e.g. like in 
    "miniCPA"). 

    
Mike: 
- I 
    reformatted the script table to fit in Word doc, and put configuration data 
    (moslty, CPA refs) 
in each Test Case 
    header. 
- I aligned CPA names with those 
    in spec. 
- Test Case #4: some corrections 
    suggested (see comments [JD]) 

    
Nevertheless, I'd like to send out the draft to 
    external reviewer eBES group 
in Europe, 
    next week, for review, assuming there is no opposition to this. 
    
eBES has already helped review an earlier 
    version of TestFramework before, and they are 
gearing up to organize interop testing rounds soon. 

    
Regards, 

    
Jacques 
<<BIP_suite_V08.zip>>
Next in thread → Next in month →