From: Steve L. (JIRA) <ji...@sm...> - 2009-03-20 16:25:11
|
[ http://jira.smartfrog.org/jira/browse/SFOS-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved SFOS-1121. ---------------------------------- Fix Version/s: 3.17.x (was: 4.01.x) Resolution: Fixed done. the WaitFor and EvaluateCondition components both extract this cause and add it to their attributes before running any failure actions > subclass Condition interface with one that provides a reason for a condition failing > ------------------------------------------------------------------------------------ > > Key: SFOS-1121 > URL: http://jira.smartfrog.org/jira/browse/SFOS-1121 > Project: SmartFrog > Issue Type: Improvement > Components: .sfCore > Reporter: Steve Loughran > Assignee: Steve Loughran > Fix For: 3.17.x > > > The TestCompound and Waitfor both skip actions when a condition fails/is not reached in a period of time. for both of these, it would help users if the reason for failure were included in an error message. > -the Condition interface could be extended with a ConditionWithCause interface that returned an explanation (and optionally, an exception?) > -the standard conditions could explain their failure, the web page condition would return the error code and failing page, etc. > -the not/and/or would return the nested causes with the relevant boolean logic operations applied. > The WaitFor and TestCompound components would include the reason when failing -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |