Versions Compared

Key

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

...

NOTE: When running test in batch mode using Maven, be sure to include -DtestDirect=false so that automated Direct tests will not be executed\.

Info
titleJMX 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.

Regression suite test results

The table below is color coded only to group tests by Testing Mode. 

...

Admin GUI Testing

...

Admin GUI Testing

The Admin GUI has been completely tested as described on the Admin GUI Testing page on the four supported application servers for the CONNECT 5.3 release

...

...

Direct Testing

As described on the Direct testing page, some Direct tests have been automated. no longer used and work as is from CONNECT 4.7.

...

Large Payload and X12 has been tested for the CONNECT 5.3 release by executing the Large Payload and CAQH Core X12 Testing

Large Payload Test Results

...

X12 Test Results

...

Performance Test Results

WildFly - 8.2.1 To  WildFly-8.2.1

Below metrics captured by configuring AuditRepositoryProxyConfig.xml to auditrepositorynoop, auditrepositorywssecured and auditrepositoryjava with audit on and off modes

...

Related Documents

Child pages (Children Display)
excerptTypesimple

...