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

Establish e2e tests for Projected Resource CSI driver


    • 5
    • OCPSTRAT-475 - Enable sharing ConfigMaps and Secrets across namespaces [Tech Preview]
    • Sprint 195

      User Story

      As an OpenShift stakeholder, I would like to have automated e2e testing of the projected csi driver function.

      Acceptance Criteria

      • Existing manual tests documented in the readme are ported to automated e2e's

      Docs Impact


      Launch Checklist

      Dependencies identified
      Blockers noted and expected delivery timelines set
      Design is implementable
      Acceptance criteria agreed upon
      Story estimated


      CI doc on how to test OLM operators build with operator SDK: https://docs.ci.openshift.org/docs/how-tos/testing-operator-sdk-operators/

      Guiding Questions

      User Story

      • Is this intended for an administrator, application developer, or other type of OpenShift user?
      • What experience level is this intended for? New, experienced, etc.?
      • Why is this story important? What problems does this solve? What benefit(s) will the customer experience?
      • Is this part of a larger epic or initiative? If so, ensure that the story is linked to the appropriate epic and/or initiative.

      Acceptance Criteria

      • How should a customer use and/or configure the feature?
      • Are there any prerequisites for using/enabling the feature?


            gmontero@redhat.com Gabe Montero
            adkaplan@redhat.com Adam Kaplan
            0 Vote for this issue
            1 Start watching this issue