OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Continuing Test Assertion and TestCase review - section 6

Continuing with Section 6; I'm looking at SCA_Assembly_Test_Assertions_16.odt, SCA_Assembly_TestCases_22.odt and the CD03 assembly spec.

25) TA-6001, 6002, 6003 seem to be testable. I note that ASM_5016_TestCase and TA-5016 are similar.

26) nit Service1SuperSet.wsdl is missing line breaks in the schema section - I checked in the fix for this

27) TA-6011 - the test case ASM_6007_TestCase references TestComposite21.composite but the composite reference in there does not use a superset interface. I also think you should expand the test to include multiple promotions (similar to ASM_6006_TestCase but as a positive test).

28) TA-6012 - the test case ASM_6007_TestCase references TestComposite22, but according to ASM60013, I think the test should work (the runtime should use the Service1SuperSet interface for the composite reference). The TC document declares 6007 as a negative test.

29) TA-6014 and ASM_6032_TestCase are good - I'd like us to consider an additional test for ASM60010, where there are two components, each with a reference that is promoted to a single composite ref but where the component refs have MUX intents.

30) ASM_6017_TestCase actually has two possible outcomes. The runtime could have chosen TestComponent3 and therefore the expected response would be altered. "ASM_6017 request service1 operation1 invoked third operation1 invoked"

Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]