Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-1707

[SDN Backlog] CI

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • SDN Core
    • [SDN Backlog] SDN CI
    • False
    • False
    • To Do
    • 56% To Do, 2% In Progress, 42% Done
    • Undefined
    • 0
    • 0

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      Epic Goal

      • Every SDN feature should have a corresponding e2e test
      • Some fixes should have regression tests

      Why is this important?

      • We want to catch new bugs before they merge, rather than only finding out about them when QE finds them
      • e2e tests run in a variety of environments and may catch bugs that QE testing does not

      Acceptance Criteria

      • Every SDN feature has an e2e test, ideally as part openshift-tests, but possibly in some other test suite if it's not possible to test them in a stock environment
      • Release Technical Enablement - N/A

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              jluhrsen Jamo Luhrsen
              dwinship@redhat.com Dan Winship
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: