Best Practices and Examples

Upgrade of a released service and OSD are critical for Managed Services. 

These tests should validate that the service under test is able to continue running as new versions of OSD (the .x and .y streams) are available. Also, tests should validate that new versions of the service can be installed/upgraded. For example code see:

RHOAM Automated OSD Upgrade Tests

These tests are run by a nightly pipeline that provisions OSD and installs RHOAM on it and then it triggers the OSD upgrade. Running of the actual test suite (the automated functional tests) is optional and for nightly executions it is skipped. We are only interested in measuring the downtime of RHOAM components.

The pipeline is here:

https://master-jenkins-csb-intly.apps.ocp-c1.prod.psi.redhat.com/job/Nightly/job/managed-api-openshift-upgrade/

RHOAM Automated Component/Release Upgrade Tests

These tests are run by a nightly pipeline that provisions OSD and installs RHOAM on it and then it triggers the RHOAM upgrade. There is a lot of prep work because the pipeline actually runs the RHOAM upgrade from current GA to current master so it has to create that “master” release first. Full functional test suite is executed after the upgrade.

The pipeline is here:

https://master-jenkins-csb-intly.apps.ocp-c1.prod.psi.redhat.com/job/Nightly/job/managed-api-upgrade/ 

(Corresponding RHOSAK OSD and Component upgrade tests are WIP as of May 2022.)