Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-5353

Hypershift Automation Backlog

XMLWordPrintable

    • Hypershift Automation Backlog
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 48% To Do, 0% In Progress, 52% Done

      Epic Goal

      Develop a set of automated regression test to cover all scenarios in ACM that make use of Hypershift and cover the following testcases:

      https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitems/testcase?query=casecomponent.KEY%3Ahypershift%20AND%20NOT%20status%3Ainactive

      Why is this important?

      Hypershift is a tech-preview feature in ACM 2.8 but will go GA as part of ACM 2.9 (most likely). QE should have a stable regression suite to cover the test scenarios.

      Scope

      1. Daily pipeline to check the health of hypershift add-on
        1. SD-Hypershift (aka ROSA Hypershift) deployment method of hypershift add-on is not in scope.
        2. Only local-cluster (aka official ACM supported way) hypershift-addon is in scope.
      2. E2E tests will revolve around HyperShift add-on for AWS/kubevirt. BM to be tracked separately by Eco QE team.
      3. add-on e2e tests should test the functionality of hypershift cluster lifecycle: creating, maintaining (upgrades, node scaling), and destroying
      4. Created hypershift clusters need to be hooked into the full ACM E2E pipeline to test ACM add-ons on hypershift hosted clusters

       

      Repo:

      https://github.com/stolostron/hypershift-addon-e2e-tests/tree/main/e2e-go 

              rhn-support-dhuynh David Huynh
              rhn-support-dhuynh David Huynh
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: