• Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Interview folks (P/Z QE + P/Z CI + Trevor)
      Make an article about what is covered, what runs where, etc

      The goal of these discussions can be to find consensus around

      • CI
        • What is the minimum viable investment in infrastructure for continuous integration?
          • what is the minimum test coverage for release controllers
          • what is the minimum test coverage for periodics
          • what jobs to add for tech preview testing
          • what are the needs for EUS/sustainability
          • how do we handle feature gate testing
          • Can we isolate or create a test suite that will have the greatest signal of coverage for detecting issues that are architecture-specific?
        • Long term: how do we see component readiness
      • QE / test automation
        • how does OAP QE (to take an example) validate next releases of External Secrets Operator on Power/Z (post-enablement)?
        • What other tools/resources are needed by ART, CRT, TRT, DPTP for P/Z testing?
          ** Can IBM Polarion/Jenkins be
triggered by RH QE?
          • How can IBM Polarion results be shared?
      • CD (Konflux)
        • What is the minimum viable investment in infrastructure for continuous delivery?
        • Is there a need for automatic testing of day2 operators on P/Z from Konflux? (where day 2 operators are built?)
      • Overall coverage: CI + RH QE + IBM QE: how do we evaluate the overall test coverage?

              skhoury@redhat.com Sherine Khoury
              skhoury@redhat.com Sherine Khoury
              Brian Cogan
              None
              None
              ocp-multi-arch-ibm-partners
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week, 2 days
                  1w 2d