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

Global Hub 1.6.0 Regression Testing

XMLWordPrintable

    • Global Hub 1.6.0 Regression Test Plan
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do

      Epic Goal
      Execute comprehensive regression testing for Global Hub 1.6.0 across 13 test scenarios covering regression, upgrade, sanity check, stage, and post-publish testing to ensure version compatibility and feature stability.

      Why is this important?
      Global Hub 1.6.0 introduces critical updates that must be validated across multiple ACM (2.13-2.15) and OCP (4.16-4.20) version combinations. This comprehensive regression testing ensures backward compatibility, upgrade path reliability, and advanced configuration features (BYO, Hosted, Brownfield, FIPS) function correctly across the supported version matrix.

      Scenarios

      Test Scenarios - Environment Matrix

      a b
      Col A1 Col A2

      Regression Test Scenarios (6 scenarios):
      1. Priority 1 - Automation: ACM2.15/OCP4.20 → ACM2.15/OCP4.19 (BYO + FIPS)
      2. Priority 2 - Automation: ACM2.15/OCP4.20 → ACM2.14/OCP4.19 (Brownfield)
      3. Priority 1 - Full: ACM2.14/OCP4.19 → ACM2.15/OCP4.20 (Hosted + Brownfield + FIPS)
      4. Priority 2 - Automation: ACM2.14/OCP4.18 → ACM2.13/OCP4.17 (Basic)
      5. Priority 2 - Automation: ACM2.13/OCP4.17 → ACM2.14/OCP4.16 (BYO + Hosted + Brownfield)
      6. Priority 2 - Automation: ACM2.13/OCP4.16 → ACM2.13/OCP4.16 (BYO + Brownfield + FIPS)

      Upgrade Test Scenarios (2 scenarios):
      7. Priority 1 - Full: ACM2.14/OCP4.19 → ACM2.15/OCP4.19 + ACM2.13/OCP4.17 → ACM2.14/OCP4.18 (Hosted + Brownfield) - 1.5.1 → 1.6.0
      8. Priority 2 - Automation: ACM2.14/OCP4.17 → ACM2.15/OCP4.18 (Basic) - 1.4.2→1.5.1→1.6.0

      Sanity Check Test Scenarios (2 scenarios):
      9. Priority 2 - Automation: ACM2.15/OCP4.20 → ACM2.14/OCP4.19 (Hosted + Brownfield + FIPS)
      10. Priority 2 - Automation: ACM2.14/OCP4.19 → ACM2.15/OCP4.18 (Basic) - For upgrade: 1.4.1 → 1.5

      Stage Test Scenarios (2 scenarios):
      11. Priority 1 - Automation: ACM2.13/OCP4.18 → ACM2.14/OCP4.19 (Hosted + Brownfield + FIPS)
      12. Priority 1 - Automation: ACM2.13/OCP4.18 → ACM2.13/OCP4.17 (Basic)

      PostPublish Test Scenarios (1 scenario):
      13. Priority 1 - Automation: ACM2.15/OCP4.20 → ACM2.15/OCP4.20 (Brownfield)

      Version Compatibility Matrix

      • Global Hub Version: 1.6.0
      • ACM Versions: 2.13, 2.14, 2.15
      • OCP Versions: 4.16, 4.17, 4.18, 4.19, 4.20

      Configuration Features to Test

      • BYO (Bring Your Own): 4 scenarios
      • Hosted Mode: 5 scenarios
      • Brownfield: 8 scenarios
      • FIPS: 5 scenarios

      Acceptance Criteria

      • [ ] All Priority 1 test scenarios completed successfully (6 scenarios)
      • [ ] 95% pass rate for Priority 2 scenarios (7 scenarios)
      • [ ] No critical or high-priority bugs introduced
      • [ ] Version compatibility matrix fully validated
      • [ ] Advanced configuration features working properly (BYO, Hosted, Brownfield, FIPS)
      • [ ] Performance metrics within acceptable baseline
      • [ ] All test execution documented with evidence
      • [ ] Test results reviewed and signed off by QE team

      Dependencies (internal and external)

      • Global Hub 1.6.0 release candidate availability
      • Test infrastructure provisioning for all ACM/OCP version combinations
      • Required certificates and security configurations for FIPS scenarios
      • Access to all required ACM versions (2.13, 2.14, 2.15) and OCP versions (4.16-4.20)
      • Test automation framework updates for new version combinations

      Previous Work (Optional):

      • Global Hub 1.5.x regression testing
      • ACM 2.14 and 2.15 compatibility validation

      Open questions:

      • Are there any specific performance benchmarks for the 1.6.0 release?
      • Do we have confirmed availability dates for all required test infrastructure?
      • Are there any known issues with specific ACM/OCP version combinations that need workarounds?

      Done Checklist

      • [ ] CI - CI is running, tests are automated and merged.
      • [ ] Release Enablement
      • [ ] DEV - Upstream code and tests merged:
      • [ ] DEV - Upstream documentation merged:
      • [ ] DEV - Downstream build attached to advisory:
      • [ ] QE - Test plans in Polarion:
      • [ ] QE - Automated tests merged:
      • [ ] DOC - Doc issue opened with a completed template. Separate doc issue opened for any deprecation, removal, or any current known issue/troubleshooting removal from the doc, if applicable.
      • [ ] Considerations were made for Extended Update Support (EUS)

      🤖 Generated with Claude Code

              clyang82 Chunlin Yang
              huichen@redhat.com Hui Chen
              Yaheng Liu Yaheng Liu
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: