JBehave
  1. JBehave
  2. JBEHAVE-490

Screenshots for failing scenarios are taken but not correlated with the story HTML output hyperlink

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: web-3.3.3, web-3.4
    • Component/s: Web Selenium
    • Labels:
      None
    • Number of attachments :
      1

      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.

        Activity

        Mauro Talevi made changes -
        Field Original Value New Value
        Summary 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
        Assignee Mauro Talevi [ maurotalevi ]
        Fix Version/s web-3.4 [ 17279 ]
        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).
        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.
        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.

        Hide
        Mauro Talevi added a comment -

        This is caused by JBEHAVE-472, fixed from core 3.4-beta-2.

        Show
        Mauro Talevi added a comment - This is caused by JBEHAVE-472 , fixed from core 3.4-beta-2.
        Mauro Talevi made changes -
        Fix Version/s web-3.3.3 [ 17366 ]
        Mauro Talevi made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]

          People

          • Assignee:
            Mauro Talevi
            Reporter:
            Paul Hammant
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: