Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2317

Author new QE tests and move existing QE tests from private to upstream repos

XMLWordPrintable

    • Icon: Initiative Initiative
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • Quality / Stability / Reliability
    • None
    • 0% To Do, 100% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None

      Goal

      Objective 4, KR-2:  KR-2:  shared automation repos and standardized testing execution to establish an unified quality signal across Eng &QE in component readiness dashboard which enables data driven release readiness assessment

      QE has long had discussions around making our test cases/automation "open" and not putting them behind a private repository.  As part of this OKR there is an active effort to add QE tests to upstream repositories and to have their results unified with development CI test results (Sippy, Component Readiness, etc).

      Each QE team should create a child story for this initiative in their own Jira repository and begin this work in 2025.  A suggested start to this is to begin automating all new tests upstream in the appropriate repo.

      Resources:

      Problem Statement

      Unified Automated Testing

      OpenShift Tests Extension Integration Guide

       

              mifiedle@redhat.com Mike Fiedler
              mifiedle@redhat.com Mike Fiedler
              None
              None
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: