Overview

The Document Query Spec Version testing; design to hit both version of the Document Query and verify the response send by mock-response (DQ Adapter).

• Document Query Spec Version (2.0) implement prior to July-2011 specs

• Document Query Spec Version (3.0) implement July-2011 specs

Test Detail

The Bimodal test are design to hit service in standard and passthrough, by calling the JMX console to switch the service mode without application server restart.

The scenario are identical, the test data is being verify in the SOAP Request and Mock Response.

Scenario 1

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (2.0)

   • Assert documentId (mock.scenario1.case1)

5. Mock Response (mock.scenario1.case1)

Case 2

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (3.0)

   • Assert documentId (mock.scenario1.case2)

5. Mock Response (mock.scenario1.case2)

Scenario 2

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (2.0)

   • Assert documentId (mock.scenario2.case1)

5. Mock Response (mock.scenario2.case1)

Case 2

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (3.0)

   • Assert documentId (mock.scenario2.case2)

5. Mock Response (mock.scenario2.case2)

Scenario 3

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (2.0)

   • Assert documentId (mock.scenario3.case1)

5. Mock Response (mock.scenario3.case1)

Case 2

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (3.0)

   • Assert documentId (mock.scenario3.case2)

5. Mock Response (mock.scenario3.case2)

Scenario 4

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (2.0)

   • Assert documentId (mock.scenario4.case1)

5. Mock Response (mock.scenario4.case1)

Scenario 5

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (2.0)

   • Assert documentId (mock.scenario5.case1)

5. Mock Response (mock.scenario5.case1)

Scenario 6

Case 1

1. Update Config

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query (3.0)

   • Assert documentId (mock.scenario6.case1)

5. 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)

...

Test Suite is to verify successful Document Query (DQ) spec version (2.0 and 3.0) with exchangeInfo version configuration g1 and g0.

Bimodal tests are executed in both (Standard, PassThrough) modes and required JMX enable at the server level for SoapUI to successfully switch between Standard and PassThrough.

• 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 version 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#)