Uploaded image for project: 'ZATS'
  1. ZATS
  2. ZATS-19

Exceptions in ZK life cycle do not affect test status

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.1.0
    • Fix Version/s: None
    • Component/s: Mimic
    • Environment:

      ZK 6.5.2, ZATS 1.1.0, JUnit 4.11

      Description

      If an exception is thrown in the ZK life cycle during a ZATS test, the exception does not affect the test. I would expect such errors to be within the scope of the test suite as they indicate the page is not functioning well. Such errors include problems in the ZUL file, exceptions thrown while initializing the Composer (normally throwing a 500 status code) or errors in the AJAX life cycle (normally displaying the ZK error window).

      Preferably, by default, these errors would bubble up to the test case as a normal exception would. There, exceptions could be caught/handled/expected as appropriate.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            connollyst connollyst
            Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated: