Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1164

e2e Automation Infrastructure

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • builds-operator
    • None
    • e2e Automation Infrastructure
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 83% To Do, 0% In Progress, 17% Done

      Epic Goal

      • With Build 1.3 we want the E2E test to be completely automated on Konflux. That said, not all of the scenarios we want to test can be provisioned on Konflux.

      Why is this important?

      • Right now, we have multiple components and we are doing the testing manually.

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              avinkuma@redhat.com Avinal Kumar
              rh-ee-sabiswas Sayan Biswas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: