Re: [ebxml-iic] Test Framework Question

Serm,

 

    What particular sectio of the 
spec are you reading?  The answer is:  yes, one Test Requirement may 
have multip;e Test Cases to verify that an implemenatation satisfies that 
requirement.  For instance, 

a Test Requirement that states that all ebXML 
extension elements MUST have a "soap:mustUnderstand" attribute present.  
This may require multip;e Test Cases to verify that an implementation does 
this.

(one Test Case for SyncReply, one Test Case for 
Acknowledgment testing, one Test Case for MessageStatus 
testing...etc...)   So, each of those Test Cases would point to that 
single Test Requirement, and ALL of them must 

pass successfully for an implementation to say that 
it satisfies that requirement.

 

   A Test Driver identifies which TCs 
satisfy a requirement by examining the TC's "requirementReferenceID".. which is 
a pointer (via ID) to that particular TR.  A Test Driver then executes all 
TC's that "point" to a particular TR.

 

Regards,

Mike

 

  

  
----- Original Message ----- 

  
From: 
  Boonserm (Serm) 
  Kulvatunyou 

  
To:  
  

  
Sent: Monday, September 27, 2004 11:24 
  AM

  
Subject: [ebxml-iic] Test Framework 
  Question

  

  
Jacques and Mike et.al,

  
 

  
I looked over the TF doc and have a question. In 
  the test material, Test Profile is an aggregation of Test Requirements. Test 
  Driver takes a Test Profile and searches for associated Test Cases and 
  execute them. 

  
 

  
However, in one section the it is describing that 
  a TR may have multiple TCs associated as one may have multiple ways of 
  validating the TR. The question is how the Test Driver can identify a specific 
  TC for a TR that has multiple TCs associated or I am missing 
  something?

  
 

  
Thank you,

  
Serm