Change By: Daniel Lipp (09/Apr/13 1:35 PM)
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.

New implementation We  should :
 support both -  provided flag: isExpected
- fail if it's
 failing immediately when an  expected  but  element is  not around
- proceed if not
 as well as continuing when an element is  expected  and  to  not  be  around

. This  will also  would  dramatically speed up uitests in case of unexpectedly missing elements.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira



----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to