Regression Testing

Owned by Tran Tang (Unlicensed)
Last updated: Jul 26, 2019 by Patrick Lobre (Unlicensed)

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 consists of SoapUI tests found in the RegressionSuite directory located at "\CONNECT\Product\SoapUI_Test\RegressionSuite", 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.

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. 

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.

Related Documents