Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Regression testing for CONNECT Gateway Release 4.7 consists of SoapUI tests found in the RegressionSuite directory , Direct testing, located at "\CONNECT\Product\SoapUI_Test\RegressionSuite", System Administration Module testing, X12 testing and Large Payload testing. The regression tests are designed to ensure that previously existing functionality still works in the current release.

In Release 4.7, Regression projects are updated with JMX scripting to support WildFly application server.  Event Logging Regression projects are re-written to validate some of JSON elements for each service: Event Logging - Standard and Event and Event Logging - Passthrough

Some Direct QOS test cases were automated and the automated test cases are denoted in the /wiki/spaces/CONNECTWIKI/pages/24576016. Automated Direct test cases are run as part of the CONNECT nightly CI but were also manually executed as part of 4.7 release testing. 

NOTE: Since Bluebutton trustbundle got expired, Direct tests are limited to Trust Anchor and Anchor test cases.

...

SoapUI

...

SoapUI Regression Test Suite

The regression suite testing can be performed in batch mode using Maven or it can be executed in soapUI. Most of the regression test suites are run as part of automated testing in the CI nightly job on WildFly-8.2.1. There are many manual test cases which needs the user intervention and need to run manually.

NOTE: When running test in batch mode using Maven, be sure to include -DtestDirect=false so that automated Direct tests will not be executed\.

Info
titleJMX error

Occasionally when executing manual regression tests, we see "JBREM000200: Remote connection failed: java java.io.IOException: An established connection was aborted by the software in your host machine" in server.log first time when we manually executes jmx project.  This only happens when soapUI terminates the JMX connection client before the server sends a response. It is an environment issue and not code related and doesn't affect CONNECT functionalities. The only remedy is to wait for few mins after the server starts before executes any JMX projects.

Regression suite test results

The table below is color coded only to group tests by Testing Mode. 

...

In Nhin Outbound message <To> tag as below:
<To xmlns="http://www.w3.org/2005/08/addressing">https://localhost:8181/Gateway/DocumentSubmission/2_0/NhinService/XDRRequest_Service</To>

In Nhin Inbound message <To> tag as below:
<To xmlns="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonymous</To>

Verified and the above entries are as expected.

...

System Administration Module (SAM) Testing

The SAM has been regression tested for the CONNECT 4.7 release by executing the /wiki/spaces/CONNECTWIKI/pages/24576018

SAM test results

...

PASS

...

PASS

...

Direct Testing

As described on the /wiki/spaces/CONNECTWIKI/pages/24576016, some Direct tests have been automated. The following is an aggregate listing of all Direct test results.

 Basic test results

...

Unable to see following events:

...

END_INBOUND_MDN_DISPATCHED

Highlight
Used .net and .org pollers to run this test and I was able to see both Begin/End inbound MDN Dispatched event.

...

Unable to see following events:

...

END_INBOUND_MDN_DISPATCHED

Highlight
Used .net and .org pollers to run this test and I was able to see both Begin/End inbound MDN Dispatched event.

...

  • BEGIN_INBOUND_MDN_DISPATCHED
  • END_INBOUND_MDN_DISPATCHED

QOS test results

...

1

...

Large Payload and X12 Testing

X12 has been regression tested for the CONNECT 4.7 release by executing the /wiki/spaces/CONNECTWIKI/pages/24576043.  Tested Large Payload by following the configuration steps at:https://connectopensource.atlassian.net/wiki/x/KwB3AQ

Large Payload Test Results

...

X12 Test Results

...

Related Documents

Child pages (Children Display)
depth10
excerptTypesimple