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 4 Next »

Version History:

Version#

Date

Modified By

Description of Modification

0.105/26/2017Sovann HuynhMigrated from CONNECT 4.7 release section

Overview

Regression testing for CONNECT Gateway Release 5.3 consists of SoapUI tests found in the RegressionSuite directory, 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 5.3, 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 Logging - Passthrough

Some Direct QOS test cases were automated and the automated test cases are denoted in the QOS test cases table. Automated Direct test cases are run as part of the CONNECT nightly CI but were also manually executed as part of 5.3 release testing. 

The SoapUI regression test suite, SAM and large payload (DS, DR) were successfully executed with CONNECT 5.3.

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\

JMX error

Occasionally when executing manual regression tests, we see "JBREM000200: Remote connection failed: 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. 

Regression Test Project NameNightly CITesting ModeCommentsResult
AdapterPatientDiscoveryAsyncReqYesBimodal
PASS
AdapterPatientDiscoveryAsyncReqErrorYesBimodal
PASS
AdapterPatientDiscoveryAsyncRespYesBimodal
PASS
AdapterPolicyEngineSAMLConformanceTestsYesBimodal
PASS
AdapterRegistryErrorListMissingTestYesBimodal
PASS
ValidateDQDRMultispecSupportTestNOBimodalmanually-testedPASS
ValidatePDCountryCodeTestYesBimodal
PASS
ValidateDQAdapterMultipleEventCodesTestYesBimodal
PASS
ExchangeManagerTestsYesBimodal
PASS
DocRegistryAndRepositoryYesBimodal
PASS
DocumentRetrieveXDSErrorValidationYesBimodal
PASS
ValidatePDCommunicationErrorHandlingTestYesBimodal
PASS
XDRAdapterTestsYesBimodal
PASS
ValidateSAMLResourceURIAttributeTestYesBimodal


PASS
ValidateQDMessageSpecVersionTestYesBimodal
PASS
ValidateAuditQueryLogServiceYesBimodal
PASS
ValidateRDMessageSpecVersionTestYesBimodal
PASS
DocQueryAdditionalStoredQueriesYesPassthrough
PASS
DocQueryRetrieveSelfTestYesPassthrough
PASS
DocQueryXDSErrorsYesPassthrough
PASS
EventLogging-PassthroughYesPassthrough
PASS
NHINCReceivingXDRAsyncRequestTestsYesPassthrough


PASS
NHINCReceivingXDRAsyncResponseTestsYesPassthrough


PASS
AuditLogging-PassthroughNoPassthroughAlso make sure to use dn=localhost as self-sign cert since some tests will use the value to make assertion. Disable JMX call on the AuditLogging when running DDS on WAS8.5PASS
DocQueryErrorCodesPassthruYesPassthrough
PASS
Admin-Distribution-PassthroughYesPassthrough
PASS
NHINSAMLSubjectConfirmationTestYesPassthrough
PASS
X12ErrorHandlingTestYesPassthrough
PASS
AdapterSpringInjectionTestYesPassthrough
PASS
DocQueryErrorCodesPassthruYesPassthrough
PASS
Admin-Distribution-StandardNoStandardtest passed if audit logging doesn't run into timeout-issue; timeout issue is resolved by configuring webserviceproxy.retryattempts and webserviceproxy.retrydelay in gateway.properties  filesPASS
AuditLogging-StandardYesStandard
PASS
DocQueryErrorCodesStandardYesStandard
PASS
DocQueryFanoutTestTargetYesStandard
PASS
DocQueryOnDemandYesStandard
PASS
DocQuerytestsforUDDIYesStandard
PASS
EntityDocQueryYesStandard
PASS
EntityDocQuerySecuredInterfaceTestYesStandard
PASS
EntityDocRetrieveYesStandard
PASS
EntityDocRetrieveSecuredInterfaceTestYesStandard
PASS
EntityPolicyEngineTestYesStandard
PASS
EntityXDRTestsYesStandard
PASS
EventLogging-StandardYesStandard
PASS
ExchangeManagerYesStandard
PASS
KeepAliveHeaderYesStandard
PASS
NHINCPatientDiscoveryMAAYesStandard
PASS
PatientCorrelationYesStandard
PASS
PatientDiscoveryDBYesStandard
PASS
PatientDiscoveryInternalErrorMessageIdTestYesStandard
PASS
PDSAMLIssuerWithX509SubjectNameYesStandard
PASS
ValidateConnectionManagerForAllServicesYesStandard
PASS
XDRAsyncRequestInbound-TestsYesStandard
PASS
XDRAsyncRequestOutbound-TestsYesStandard
PASS
TransactionIDTestYesStandard
PASS
EntitySendingXDRAsyncReqTestsYesStandard
PASS
EntitySendingXDRAsyncResponseTestsYesStandard
PASS
Fanout-TestYesStandard
PASS
ValidationSuiteYesStandardAlso executed test manually. Tester need to switch between standard and passthrough manually.PASS

Admin GUI Testing

The Admin GUI has been /wiki/spaces/CONNECTWIKI/pages/24576018 on the four supported application servers for the CONNECT 5.3 release

Test NameTest Cases CoveredResult
Login, GatewayStatus, Cross-Gateway Query Client, Accountmanagement and ConnectionManagementExecute all the test cases from wiki : Login, Gateway Status, Account Management and Exchange ManagementPASS
Properties ConfigurationExecute all the test cases from Wiki: Gateway PropertiesAdapter PropertiesAudit Properties and Internal Endpoint PropertiesPASS
Audit ViewerExecute all the test cases from Wiki: Audit SearchPASS
Certificate Manager Testing Execute all the test cases from Wiki: Certificate ManagerPASS
Failure Logging TestingExecute all the test cases from Wiki: Failing Logging TestingPASS
Test Data Loader TestingExecute all the test cases from Wiki: Test Data Loader TestingPASS

Direct Testing

As described on the Direct testing page, some Direct tests have been automated. no longer used and work as is from CONNECT 4.7.

Large Payload and X12 Testing

Large Payload and X12 has been tested for the CONNECT 5.3 release by executing the Large Payload and CAQH Core X12 Testing

Large Payload Test Results

Test NameTesting ModeCommentsResult
Document Submission (Deferred)PassthroughTest using 1GB payloadPASS
Document RetrievePassthroughTest using 1GB payloadPASS


X12 Test Results

Test NameTesting ModeCommentsResult
CAQH Core X12 Batch RequestPassthroughTest using 20MB, 200MB and 1GB payloadPASS
CAQH Core X12 Batch ResponsePassthroughTest using 20MB, 200MB and 1GB payloadPASS

Performance Test Results

WildFly - 8.2.1 To  WildFly-8.2.1

Below metrics captured by configuring AuditRepositoryProxyConfig.xml to auditrepositorynoop, auditrepositorywssecured and auditrepositoryjava with audit on and off modes

#ServiceAudit On (Per Min)Audit Off (Per Min)
Noop ImplSecured ImplJava ImplNoop ImplSecured ImplJava Impl
1PD13006002300290016003000
2DQ9006002600180013003100
3DR11006202700270017002900

Related Documents

  • No labels