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

GitOps 1.13.0 Release Test Execution

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • 1.13.0
    • 1.13.0
    • Testing
    • GitOps 1.13.0 Release Test Execution Clone
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Track the test execution effort for the 1.13.0 release test plan

      Why is this important?

      • Will provide evidence of test coverage and measure total effort

      Acceptance Criteria

      • Stories for each permutation to be covered will be created and linked to this story.
      • Each story have sizing points
      • Each story will be linked to this epic

      Done Checklist

      Any Gaps will be listed in

      • Al stories are set to done.
      • Any gaps will be listed in the "Details and Support matrix" 

      Epic Goal

      • To test GitOps 1.13.0 before releasing it to the market.

      Why is this important?

      • We need to validate the release to ensure the quality of the shipped software.

      Scenarios

      1. OCP regular on AWS/GCP/PSI.
      2. OSD, ROSA, Hypershift
      3. Disconnected env

      Acceptance Criteria (Mandatory)

      • The release candidate for 1.13.0 has been properly validated.
      • QE team agrees to the release and is confident about that.

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)

         

            mbhalodi@redhat.com Meha Bhalodiya
            mbhalodi@redhat.com Meha Bhalodiya
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: