Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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

Overview

The Document Query Spec Version testing is designed to hit both versions 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 tests are designed to hit service in standard and passthrough by calling the JMX console to switch the service mode 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

  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

  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.scenario7.case1)

  5. Mock Response (mock.scenario7.case1)

  • No labels