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

Investigate ArgoCD E2E test failures

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Testing
    • None
    • Investigate ArgoCD E2E test failures
    • False
    • None
    • False
    • To Do
    • 73% To Do, 8% In Progress, 19% Done

      Epic Goal

      • Tracking the investigation of test failures from ArgoCD E2E tests
      • Improving the test stability
      • Resolve or mark it as "Known failure" with proper reasoning

      Why is this important?

      • We have been observing these test failures for a long time without debugging

      Scenarios

      1. Z stream and Y stream release testing 

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • All failing tests have a known reason

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …
      •  

      Done Checklist

      • Tests are stable
      • Acceptance criteria are met

              rhn-support-vab Varsha B
              rhn-support-vab Varsha B
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: