[jbehave-dev] [jira] Resolved: (JBEHAVE-413) Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports
[ http://jira.codehaus.org/browse/JBEHAVE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-413. -- Resolution: Fixed Fix Version/s: 3.2 Assignee: Paul Hammant Coded. > Failing steps could be assigned a unique failure-context that could to a) > name screenshots, and b) be used in HTML reports > -- > > Key: JBEHAVE-413 > URL: http://jira.codehaus.org/browse/JBEHAVE-413 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > Fix For: 3.2 > > > This affects 'core' and 'web' > Say an element is not found in a webpage, and WebDriver throws whatever > exception it needs, presuming that fails a step, then JBehave could set a > failure-context (lets say that a GUID). > Later, when the FailingScreenShotThing picks up the fact that a step failed, > it could use the failure-context in the name of the screen-shot jpeg. > Later, in the rendering of the reports, the HTML one at least could link to > the jpeg. > Maybe instead of GUID, this could be the Object Identity of the StepResult or > Failed instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-413) Failing steps could be assigned a unique failure-context that could to a) name screenshots, and b) be used in HTML reports
[ http://jira.codehaus.org/browse/JBEHAVE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-413. -- Resolution: Fixed > Failing steps could be assigned a unique failure-context that could to a) > name screenshots, and b) be used in HTML reports > -- > > Key: JBEHAVE-413 > URL: http://jira.codehaus.org/browse/JBEHAVE-413 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > Fix For: 3.2 > > > This affects 'core' and 'web' > Say an element is not found in a webpage, and WebDriver throws whatever > exception it needs, presuming that fails a step, then JBehave could set a > failure-context (lets say that a GUID). > Later, when the FailingScreenShotThing picks up the fact that a step failed, > it could use the failure-context in the name of the screen-shot jpeg. > Later, in the rendering of the reports, the HTML one at least could link to > the jpeg. > Maybe instead of GUID, this could be the Object Identity of the StepResult or > Failed instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
