Overview

CONNECT testing is performed on three levels:

• Basic unit testing / validation suite testing during development
• Jenkins CI Nightly testing
• QA testing prior to closing JIRA tickets

This documentation includes references to test plans at the QA level and test results by release. 

Validation Suite Testing

The validation suite is executed as part of every QA test plan to ensure that new code or configuration changes do not adversely affect the current CONNECT services. The test is a SoapUI test project located /CONNECT/Product/SoapUI_Test/ValidationSuite and can be executed by running the g0 and g1 test suites. The GatewayPropDir must be set to the full path of the local CONNECT properties directory of your container server

Validating CONNECT Installation

• SoapUI and the Validation Suite

System Administration Module (SAM) Testing

The SAM test plan consists of a series of manual test cases designed to verify the look and function of each section of the interface. Currently, these sections include:

Admin GUI Testing

• Audit Search
• Login, Gateway Status, Account Management and Exchange Management
• Gateway Properties Editor Testing
• Adapter Properties Editor Testing
• Internal Endpoints Properties Editor Testing
• Audit Properties Editor Testing
• Failure Logging Testing
• Test Data Loader Testing
• Certificate Management Test

Regression Suite Testing

The regression test suite includes four test categories: standard, passthrough, bimodal and manual. Within each category there are several tests, all of which are designed to verify that CONNECT fixes and improvements continue to function as designed with each release.

Regression Testing

• Configuring JMX for Wildfly in SoapUI Regression Test
• Standard Tests
  • Admin-Distribution-Standard
  • AuditLogging-Standard
  • DocQueryErrorCodesStandard
  • DocQueryFanoutTestTarget
  • DocQueryOnDemand
  • DocQueryTestsForUDDI
  • EntityDocQuery
  • EntityDocQuerySecuredInterfaceTest
  • EntityDocRetrieve
  • EntityDocRetrieveSecuredInterfaceTest
  • EntityPolicyEngineTest
  • EntitySendingXDRAsyncReqTests
  • EntitySendingXDRAsyncResponseTests
  • EntityXDRTests
  • EventLogging-Standard
  • ExchangeManager
  • Fanout_Test
  • KeepAliveHeader
  • NHINCPatientDiscoveryMAA
  • PatientCorrelation
  • PatientDiscoveryDB
  • PatientDiscoveryInternalErrorMessageIdTest
  • PDSAMLIssuerWithX509SubjectNameTest
  • TransactionLogging
  • ValidateConnectionManagerForAllService
  • XDRAsyncRequestInboundTest
  • XDRAsyncRequestOutboundTest
• Passthrough Tests
  • AdapterSpringInjectionTest
  • Admin Distribution-Passthrough
  • AuditLogging-Passthrough
  • DocQueryAdditionalStoredQueries
  • DocQueryErrorCodesPassthrough
  • DocQueryRetrieveSelfTest
  • DocQueryXDSErrors
  • EventLogging - Passthrough
  • NHINC Receiving XDRA sync Request Tests
  • NHINC Receiving XDRA sync Response Tests
  • NHINSAMLAttributeTest
  • NHINSAMLSubjectConfirmationTest
  • X12ErrorHandlingTest
• Bimodal Tests
  • AdapterPatientDiscoveryAsyncReq
  • AdapterPatientDiscoveryAsyncReqError
  • AdapterPatientDiscoveryAsyncResp
  • AdapterPolicyEngineSAMLConformance
  • AdapterRegistryErrorListMissingTest
  • DocRegistryAndRepository
  • DocumentRetrieveXDSErrorValidation
  • ExchangeManagerTests
  • ValidateAuditQueryLogService
  • ValidateDQAdapterMultipleEventCodesTest
  • ValidateDQDRMultispecSupportTest
  • ValidatePDCommunicationErrorHandlingTest
  • ValidatePDCountryCodeTest
  • ValidateQDMessageSpecVersionTest
  • ValidateRDMessageSpecVersionTest
  • ValidateSAMLResourceURIAttributeTest
  • XDRAdapterTests
• Manual Tests
  • MustUnderstandSuite
  • ValidateWSAToFieldInSoapHeaderTest
• Regression Suites Artifacts
  • AuditQuery and AuditLogging
  • Transaction Timeout

NIST Testing

NIST testing currently consists of using the NIST Transport Test Tool to test the following:

NIST Edge Testing Tool (ETT)