Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-4216

Add E2E tests on upstream Paac to integrate with results and chains

XMLWordPrintable

    • pipelines-components-integrations-testing-on-paac-upstream
    • False
    • None
    • False
    • To Do

      Epic Goal

       

      we are increasingly relying on results and chains from PaaC. We need some e2e tests between two to check that things are not broken.

      I'ts currently done manually between releases and it's badly done.

       

      Parr of this epic we want to define what are the outcome of those tests and what we are testing.

      Upstream paac run on kuberntes and not on openshift so operator/console integration is out of scope in this integration testings.

      Note: To add e2e tests which intercats with multiple components best place would be to add it in Operator

      The goal of the epic is to add e2e in Operator which covers integration of PAC and results

      Why is this important?

       

      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):

      Open questions::

      •  

      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

              Unassigned Unassigned
              cboudjna@redhat.com Chmouel Boudjnah
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: