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

GitOps 1.12.4,1.11.6,1.10.7 Release Test Execution

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Testing
    • GitOps 1.12.4,1.11.6,1.10.7 Release Test Execution
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Track the test execution effort for the release related to the Redis security settings{}

      Why is this important?

      • We need to validate the release to ensure the quality of the shipped software.
      • It will provide evidence of test coverage and measure total effort.

      Scenarios

      • OCP regular on AWS/GCP/PSI.

      Acceptance Criteria (Mandatory)

      • Stories for each permutation to be covered will be created and linked to this story.
      • Each story has sizing points
      • Each story will be linked to this epic
      • The release candidates have been properly validated.
      • QE team agrees to the release and is confident about that.

      Dependencies (internal and external)

      • The support matrix is updated
      • The release candidate has been delivered according to the support matrix with updated CRDs
      • Builds are attached to the erratas and are moved to the QE state
      • The test plan has been reviewed by all stakeholders
      • Acceptance criteria are met
      • All stories are set to done.
      • Any gaps will be listed in the "Details and Support matrix".

              rhn-support-vab Varsha B
              mbhalodi@redhat.com Meha Bhalodiya
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: