Uploaded image for project: 'Network Edge'
  1. Network Edge
  2. NE-582

[Tech Debt] [Testing+CI] Review OCP 3.11 documentation and identify gaps in test coverage

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • [Testing+CI] Review OCP 3.11 documentation and identify gaps in test coverage
    • Proactive Architecture
    • False
    • False
    • To Do
    • OCPPLAN-7878 - NetEdge - Maintainability and Debugability & Tech Backlog
    • OCPPLAN-7878NetEdge - Maintainability and Debugability & Tech Backlog
    • Undefined
    • 0
    • 0

      As the team that maintains ingress- and DNS-related components for OpenShift,

      I want test coverage for the features for which we are responsible,

      so that breaking changes are quickly identified.  

       

      I recent releases, we have discovered several gaps in test coverage.  Some of these gaps are related to tests that were written but are currently skipped (see NE-494).  Some of these gaps are related to functionality that we implemented but for which we neglected to add tests.  

      A recent example of a skipped test is the idling code.  Examples of features for which we are missing test coverage entirely include an ipfailover-keepalived and the egress routers.  

      We need to review the components for which we are responsible, our past work reviewing the OCP 3.11 documentation, possibly our product docs sketch, and our past analysis of OCP 3 router customizaations and review our existing tests in openshift/origin to identify gaps.  

      Once we have identified the gaps, we can create additional stories for implementing tests to cover these gaps.  

              Unassigned Unassigned
              mmasters1@redhat.com Miciah Masters
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: