Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4619

[Test execution] - Operator upgrade and KUTTL Tests | OCP 4.12

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Testing
    • GitOps Release - Sprint 3256

      Upgrade the operator from previous version and run Kuttl tests as part of 1.10.5 validation.

      Test Steps:

      If you are upgrading to a previously released version of gitops, just use some older channels to install the operator. Once they have reached the highest version in that particular channel, switch the channel. If you are testing the IIBs, follow the below instructions for the upgrade

      1. Clone https://gitlab.cee.redhat.com/gitops/gitops-components-automated-testing 
      2. Checkout to the master branch
      3. Install and upgrade the operator by running $ make operator-upgrade after setting QUAY_USER, NEW_VER and IIB_ID

      For running the kuttl automation pipeline, use this pipelinerun template on the bootstrap cluster with appropriate parameters 

      If you want to run the kuttl tests locally:

      1. Clone https://gitlab.cee.redhat.com/gitops/operator-e2e/-/tree/master/gitops-operator 
      2. From master branch and directory to gitops-operator run
        1. kubectl kuttl test ./tests/sequential --config ./tests/sequential/kuttl-test.yaml
        2. kubectl kuttl test ./tests/parallel --config ./tests/parallel/kuttl-test.yaml

      For running a particular test, pass the test name along with --test flag 

      More info: https://gitlab.cee.redhat.com/gitops/operator-e2e/-/blob/master/gitops-operator/README.md 

      Acceptance Criteria:

      • Upgrade tests have been performed
      • Both Sequential and Parallel suites are executed 
      • Results have been logged

              mbhalodi@redhat.com Meha Bhalodiya
              asaleh@redhat.com Adam Saleh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: