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

XMLWordPrintable

    • Type: Patch
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: seleniumhq-plugin
    • None

      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).

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

              Created:
              Updated:
              Resolved: