| Info |
|---|
As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files |
| Table of Contents |
|---|
Overview
The Document Query Spec Version testing TestSuite is designed to hit both versions of the Document Query and verify the response send by mock-response (DQ Adapter).
...
verify successful Document Query spec version (2.0
...
, 3.0)
...
Test Detail
The Bimodal tests are designed to hit service in standard and passthrough by calling the JMX console to switch the service mode with exchangeInfo version configuration g1 and g0. Bimodal test suite, test the service in both standard and passthrough and will call the JMX in the test case to switch service mode between standard and passthrough without application server restart.
The scenarios are identical, the test data is being verified in the SOAP Request and Mock Response.
Scenario 1
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (2.0)
Assert documentId (mock.scenario1.case1)
Mock Response (mock.scenario1.case1)
Case 2
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (3.0)
Assert documentId (mock.scenario1.case2)
Mock Response (mock.scenario1.case2)
Scenario 2
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (2.0)
Assert documentId (mock.scenario2.case1)
Mock Response (mock.scenario2.case1)
Case 2
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (3.0)
Assert documentId (mock.scenario2.case2)
Mock Response (mock.scenario2.case2)
Scenario 3
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (2.0)
Assert documentId (mock.scenario3.case1)
Mock Response (mock.scenario3.case1)
Case 2
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (3.0)
Assert documentId (mock.scenario3.case2)
Mock Response (mock.scenario3.case2)
Scenario 4
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (2.0)
Assert documentId (mock.scenario4.case1)
Mock Response (mock.scenario4.case1)
Scenario 5
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (2.0)
Assert documentId (mock.scenario5.case1)
Mock Response (mock.scenario5.case1)
Scenario 6
Case 1
Update Config
Clear Correlation Table & Add Correlation
Clear AA Mapping Table & Add Mapping
SOAP: Document Query (3.0)
Assert documentId (mock.scenario6.case1)
Mock Response (mock.scenario6.case1)
Scenario 7
Case 1
...
Update Config
...
Clear Correlation Table & Add Correlation
...
Clear AA Mapping Table & Add Mapping
...
SOAP: Document Query (3.0)
Assert documentId (mock.scenario7.case1)
...
g0: exchangeInfo PD only entity version 2.0
g1: exchangeInfo PD both entity version 2.0, 3.0
g1only: exchangeInfo PD only entity version 3.0
TestCases Detail for standard and passthrough
The test case with both DQ spec version 2.0 and 3.0 will match the exchangeInfo_g1, test case with DQ spec vesion 2.0 will match the exchangeInfo_g0 and test case with DQ spec version 3.0 will match with exchangeInfo_g1only.
case# by scenario#: the test case will match it document id by it mock adapter value (mock.scenario#.case#)