-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
3
-
None
-
None
-
CORENET Sprint 273, CORENET Sprint 274, CORENET Sprint 276, CORENET Sprint 277, CORENET Sprint 278, CORENET Sprint 279, CORENET Sprint 280, CORENET Sprint 281, CORENET Sprint 282, CORENET Sprint 283, CORENET Sprint 284
We can remove tests that are duplicates. there is a test-ci-mapping repo I think we can use to map the tests that are coming in from upstream.
If there is a reason not to remove the duplicate (maybe slightly different test coverage) there should be no harm as long as it does not have an identical name. The new tests using OTE will have a new label that
origin tests will not have, so I think names will be unique.
This work will need to be done for each bucket of tests that are added over time, but this story is only for
the initial NetworkSegmentation tests coming in from 2461
ANY tests that are not de-dupicated will need to have the informing label applied