Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-4962

UITests should immediately fail if an expected element is not around

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Critical
    • 5.0
    • 5.0
    • integration tests
    • None
    • Iteration 2013-14, Iteration 2013-15

    Description

      When calling AbstractMagnoliaUITest#getElementByPath(String) we don't know whether the element is actually expected to be around or not. That's why that method cannot be strict. This makes it very hard to realize what's happened in case of failures.

      We should support both - failing immediately when an expected element is not around as well as continuing when an element is expected to not be around. This would dramatically speed up uitests in case of unexpectedly missing elements.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              dlipp Daniel Lipp
              dlipp Daniel Lipp
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD