This may already exist, but if not we definitely need a concise process documented and scripted for performing automated install-and-upgrade tests of CRW 2.y to 2.y+1

One suggested path forward here is to use a Subscription to the nightly CRW application in Quay, but point to an older release, eg.,

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: codeready-workspaces
  namespace: crw
spec:
  channel: latest
  installPlanApproval: Automatic
  name: codeready-workspaces
  source: crw
  sourceNamespace: openshift-marketplace
  startingCSV: crwoperator.v2.2.0

For testing updates from one RELEASED GA version to another:

apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: codeready-workspaces
  namespace: crw
spec:
  channel: latest
  installPlanApproval: Automatic
  name: codeready-workspaces
  source: redhat-operators
  sourceNamespace: openshift-marketplace
  startingCSV: crwoperator.v2.1.0

then

 oc apply -f subscription.yaml

Additional notes:

Here are the application registries in Quay to use in your Subscriptions. Note that the VERSIONS to not align to anything in reality, so 9.0.0 = 2.2.0, and 9.9.* = CI/nightly

• official CRW releases: https://quay.io/application/redhat-operators/codeready-workspaces
• nightly: https://quay.io/repository/crw/crw-2-rhel8-operator-metadata?tag=latest&tab=tags -> https://quay.io/application/crw/codeready-workspaces
• nightly including CVE respins: https://quay.io/application/rh-osbs-operators/codeready-workspaces