Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-6837

Use status of test commands instead of suites to determine UNSTABLE/FAILURE/SUCCESS

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Currently if any of the test cases fail the build is marked unstable. This patch changes it so that if any of the Selenium assert* methods, in any of the cases in the suite fail the build will be marked as a failure and if any of the Selenium verify* methods, in any of the cases in the suite fail the build will be marked as unstable.

      This change better reflects the differences between an assertion (an unrecoverable error) vs a verification (something isn't quite right but the test can continue).

        Attachments

          Activity

          trcjr trcjr created issue -
          pascal_martin pascal_martin made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          pascal_martin pascal_martin made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 136932 ] JNJira + In-Review [ 204294 ]

            People

            Assignee:
            pascal_martin pascal_martin
            Reporter:
            trcjr trcjr
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: