...

CONNECT testing is performed on three levels:

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

...

The validation suite is executed as part of almost 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 following configurations need to be set in order for the validation suite to be executed successfully: GatewayPropDir must be set to the full path of the local CONNECT properties directory of your container server

Validating CONNECT Installation

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

...

Direct Testing

The Direct test plan consists of three test categories:

Direct Testing

• Smoke Testing: Typically executed whenever Direct code is introduced or modified. Consists of one outbound and one inbound test.
• Basic Testing: Consists of three tests to verify CONNECT's ability to direct inbound and outbound Direct messages to an XDR adapter as opposed to an email client.
• QOS Testing: Consists of nine test cases (executed in six different scenarios) to verify CONNECT's compliance with Direct QoS guidelines.

...

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 previous CONNECT fixes and improvements continue to function as designed with each release.

Regression Testing

...

...

...

...

...

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

NIST Edge Testing Tool (ETT)

...