OCP/Telco Definition of Done

Epic Template descriptions and documentation.

Epic Goal

• Add an E2E test to avoid regressions such as https://issues.redhat.com/browse/OCPBUGS-488 in which we test DNS local endpoint preference.

Why is this important?

• This regression is a major performance and stability issue and it has happened once before.

Drawbacks

• The E2E test may be complex due to trying to determine what DNS pods are responding to DNS requests. This is straightforward using the chaos plugin.

Scenarios

• CI Testing

Acceptance Criteria

• CI - MUST be running successfully with tests automated

Dependencies (internal and external)

1. SDN Team

Previous Work (Optional):

1. N/A

Open questions::

1. Where do these E2E test go? SDN Repo? DNS Repo?

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>