How is compatibility tested and maintained?

Automated testing

To test whether two releases are completely or partially compatible to each other, a dedicated testing environment exists.

It consists of seven systems:

1. Across Server
2. Congree Control Center
3. Congree Authoring Client
4. Congree Core Server
5. Congree Data Storage
6. Congree Linguistic Server
7. SQL Server

Congree can trigger any version to be updated by any other version. The test covers compatibility testing of Congree Control Center and Congree Authoring Client by executing the installation and by testing behavior after installation.

Result of the test is a list of no longer compatible components and failure when something does not work as predefined.

Example:

A release candidate for Release 044 is available. Congree wants to check how compatible different components of this release candidate are to Release 043 if for example the Client and the Control Center are not updated.

Congree gets this info and can react to it before releasing if there are any issues

Manual testing

It is possible to simulate different Internal Components Versions and run installation tests or runtime tests on any machine.

This can be done by manipulating certain files which will not be specified in public. This tests will allow Congree to follow up on issues and ensure functionality of specific scenarios not covered by automated tests.