Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3712

Create test strategy for operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • Sail MVP1
    • None
    • Project Sail
    • None
    • Sprint 6, Sprint 7, Sprint 8, Sprint 9, Sprint 10, Sprint 11

      • Which tests should be run and when?
        • when to write a unit test vs when to write an integration test
        • how are integration tests executed
      • What platforms will they be run on? (kind + OCP?)
      • Can we reuse existing istio tests? (integration tests, docs tests)
        • if we can replace the istio install with our operator install, we could potentially reuse all integration tests
        • problem is that would likely require downstream changes
      • where (OpenShift CI/Jenkins) are which tests (unit, integration) run?
        • pre-release builds from brew are not available in OpenShift CI, so we'll need Jenkins
        • we need to strive to not duplicate testing code!

        1.
        		 Document how to write tests during development (unit vs integration) Sub-task Closed Undefined Daniel Grimm
        2.
        		 Paragraph on running on kind vs running on OCP Sub-task Closed Undefined Unassigned
        3.
        		 Paragraph on reusing Istio integration tests Sub-task Closed Undefined Matthew Mahoney
        4.
        		 Paragraph on OpenShift CI vs Jenkins Sub-task Closed Undefined Matthew Mahoney

            Unassigned Unassigned
            dgrimm@redhat.com Daniel Grimm
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: