Release behavior checks guide for repeatable regression testing. This page covers regression baseline confirmation after changes.
Release and Migration Checks

Protect the approved integrated-plant baseline before sharing a release.

Repeat integration, simulation, and testing after code, topology, migration, or behavior changes.

Define the integrated baseline

Record application version, device inventory, .modbussim fingerprint, compressor behavior, I/O map, expected ranges, and required .modbustest scenarios.

Run the complete lifecycle

Recheck communication, compile and activation, startup, load changes, water proof, economizers, alarms, faults, resets, and stopping.

Preserve migration and test evidence

Confirm a failed migration leaves the active plan unchanged, then export reports and record differences, approvals, and unresolved deviations.

Workflow screenshots

Use the localized application views while following this guide.

Release and Migration Checks: Workflow screenshots 1
Release and Migration Checks — 1
Release and Migration Checks: Workflow screenshots 2
Release and Migration Checks — 2