Table of Contents
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
| Child pages (Children Display) | ||||
|---|---|---|---|---|
|
...
|
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:
Child pages (Children Display) depth 10 page Admin GUI Testing excerptType simple
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.
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|