[
http://jira.codehaus.org/browse/JBEHAVE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-490:
---------------------------------
Description:
This could well be an issue in core around exceptions being thrown (wrapped by
UUIDExceptionWrapper).
1) Apply the attached patch to Etsy (it makes everything fail).
2) Run regular build (no saucelabs): mvn clean install
3) Open Navigator or reports page and click through to the HTML page for the
failing story.
4) Click the screenshot icon (see that it 404s)
5) Otherwise check the screenshots directory, and observer that it has only one
screenshot, instead of one for each failed story.
was:
This could well be an issue in core around exceptions being thrown (wrapped by
UUIDExceptionWrapper).
1) Apply the attached patch to Etsy (it makes everything fail).
2) Run regular build (no saucelabs).
3) Open Navigator (or the older results page) and click through to the HTML
page for the failing story.
4) Click the screen-shot icon (see that it 404s)
5) Otherwise check the screen-shots directory, and observer that it has three
screenshots.
Fix Version/s: web-3.4
Assignee: Mauro Talevi
Summary: Screenshots for failing scenarios are taken but not
correlated with the story HTML output hyperlink (was: Screen-shots for failing
scenarios are being taken, but are not correlated with the story-results HTML
output's hyperlink.)
> Screenshots for failing scenarios are taken but not correlated with the story
> HTML output hyperlink
> ---------------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-490
> URL: http://jira.codehaus.org/browse/JBEHAVE-490
> Project: JBehave
> Issue Type: Bug
> Components: Web Selenium
> Reporter: Paul Hammant
> Assignee: Mauro Talevi
> Fix For: web-3.4
>
> Attachments: screenshots404.patch
>
>
> This could well be an issue in core around exceptions being thrown (wrapped
> by UUIDExceptionWrapper).
> 1) Apply the attached patch to Etsy (it makes everything fail).
> 2) Run regular build (no saucelabs): mvn clean install
> 3) Open Navigator or reports page and click through to the HTML page for the
> failing story.
> 4) Click the screenshot icon (see that it 404s)
> 5) Otherwise check the screenshots directory, and observer that it has only
> one screenshot, instead of one for each failed story.
--
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
