Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-3370

Update 'Failed suite-rerun' for release testing pipeline (xml)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • Testing
    • None
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • GITOPS Sprint 3245, GITOPS Sprint 3246, GITOPS Sprint 3247

      Story (Required)

      As a QE trying to carry out release testing I want to be able use the failed-tests rerun feature in the release testing pipeline (and execute reruns based on generated xml reports)

      Currently our rerun-failed-tests feature only accepts pre-generated json reports. An update for xml will allow us to utilise the rerun as part of release testing. 

      Background (Required)

      Currently our rerun-failed-tests feature only accepts pre-generated json reports. An update for xml will allow us to utilise the rerun as part of release testing. 

      Out of scope

      Clean up before rerun
      Any pre-req for suite testing

      Approach (Required)

      Update the existing feature to rerun failed tests to accept and parse xml reports to determine any failed tests and execute them indiviudally and generate relevant 're-run' reports

      Acceptance Criteria (Mandatory)

      Failed suite tests can be re-run provided a suitable json or xml report is provided. 

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              trdoyle Triona Doyle
              trdoyle Triona Doyle
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: