Versions Compared

Key

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

...

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

...

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

Child pages (Children Display)
depth10
pageValidating CONNECT Installation
excerptTypesimple
 

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

...

Child pages (Children Display)

...

Direct Testing

The Direct test plan consists of three test categories:

Direct Testing

...

depth10
pageAdmin GUI Testing
excerptTypesimple

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

...

Child pages (Children Display)

...

depth

...

10

...

page

...

Regression Testing

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

NIST Edge Testing Tool (ETT)

...

excerptTypesimple