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

Tooling for Realistic Upgrade Process Testing

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Testing
    • None
    • Load Bearing Upgrade Process
    • False
    • None
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      Epic Goal

      • We currently test upgrades only on clean installs
      • We should have a process and tooling to test upgrades that would be reflective on the customer's environment.

      Why is this important?

      • We have been seeing issues like

      Definition of Done

      • Investigation is done
        • investigation about our customers environments has been done and representative setups/configurations have been chosen or scripting for setup/configuration generation has been created
      • There is dedicated tooling
        • There is tooling that makes issues as described above easy to reproduce
        • We can use this tooling to anticipate/discover issues proactively
      • There is a process:
        • We implement these as part of our release process

              Unassigned Unassigned
              asaleh@redhat.com Adam Saleh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: