Uploaded image for project: 'OpenShift Storage'
  1. OpenShift Storage
  2. STOR-2413

[TechDebt] Periodic tests visible in Sippy

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • openshift-4.20
    • [TechDebt] Periodic tests visible in Sippy
    • Quality / Stability / Reliability
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • None
    • 1

      Epic Goal*

      Add periodic tests to Sippy. Clean up unused periodics.
      This will be a stepping stone to know when and how the tests run.

       
      Why is this important? (mandatory)

      We have running tests that are not used or not visible to us. This should free up resources and make our tests more visible. We will be able to analyze the tests in Sippy and see the history of ran tests.

       
      Scenarios (mandatory)

      1. All Storage periodics should be visible in Sippy.

      • Research why they are not and how to fix it.
      • Update tests as necessary

      2. Go through unnecessary tests and remove them.

      • Remove "nightly-verify-deps"
      • Look for other unused tests

      3. Add ".config.prowgen" file for periodics which report to slack so they autogenerate to jobs.

       
      Dependencies (internal and external) (mandatory)

      None

      Contributing Teams(and contacts) (mandatory) 

      Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

      • Development - 
      • Documentation -
      • QE - 
      • PX - 
      • Others -

      Acceptance Criteria (optional)

      Periodic tests are visible in Sippy.

      Drawbacks or Risk (optional)

      None

      Done - Checklist (mandatory)

      The following points apply to all epics and are what the OpenShift team believes are the minimum set of criteria that epics should meet for us to consider them potentially shippable. We request that epic owners modify this list to reflect the work to be completed in order to produce something that is potentially shippable.

      • CI Testing -  Basic e2e automationTests are merged and completing successfully
      • Documentation - Content development is complete.
      • QE - Test scenarios are written and executed successfully.
      • Technical Enablement - Slides are complete (if requested by PLM)
      • Engineering Stories Merged
      • All associated work items with the Epic are closed
      • Epic status should be “Release Pending” 

              rhn-support-dfajmon Daniel Fajmon
              rhn-support-dfajmon Daniel Fajmon
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 1 week
                  1w
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 week
                  1w