Nightwatch: Screenshots of the FAILED type are not included in the .xml report

Created on 11 May 2017  路  8Comments  路  Source: nightwatchjs/nightwatch

Hey guys!

I'm currently facing the problem that I don't see screenshot files of the _FAILED_ type been picked up in the report.

Eg:
Report:




[[ATTACHMENT|/Users/user/Bitbucket/qa-webui/screenshots/smokeTest/platformFeatures/C60-C61-C62-C63-C64-C65-/C62---Global-Knowledge-Base---Admin---Add-new-KB-item---Article_ERROR_May-11-2017-101551-GMT+0200.png]]
at checkIfItemExistsInCollection (/Users/gwenbleyen/Bitbucket/qa-webui/pages/obSettingsKnowledgeBase.js:90:27) at Object.client.element (/Users/gwenbleyen/Bitbucket/qa-webui/pages/obSettingsKnowledgeBase.js:142:29)
[[ATTACHMENT|/Users/user/Bitbucket/qa-webui/screenshots/smokeTest/platformFeatures/C60-C61-C62-C63-C64-C65-/C62---Global-Knowledge-Base---Admin---Add-new-KB-item---Article_ERROR_May-11-2017-101553-GMT+0200.png]]



=> Two _ERROR_ type screenshots are picked up in the report

Actual screenshot folder (Three screenshots, including one _FAILED_ type screenshot)

  1. C62---Global-Knowledge-Base---Admin---Add-new-KB-item---Article_ERROR_May-11-2017-101551-GMT+0200
  2. C62---Global-Knowledge-Base---Admin---Add-new-KB-item---Article_ERROR_May-11-2017-101553-GMT+0200
  3. C62---Global-Knowledge-Base---Admin---Add-new-KB-item---Article_FAILED_May-11-2017-101553-GMT+0200
    => Screenshot 3 ins't picked up in the report. Which is odd because that particular screenshot actually visualizes the error #on the failed step.

Thus, when I'm using a reporter like nightwatch-html-reporter I'm not able to attach the screenshot to the failed step.

Thanks!!

enhancement

Most helpful comment

+1

All 8 comments

+1

Hi guys, is there any update with this issue, I am facing with the same issue now.

@SiyuYan -- No, no updates of which I'm aware

When can we expect this to get fixed?

This issue has been automatically marked as stale because it has not had any recent activity.
If possible, please retry using the latest Nightwatch version and update the issue with any relevant details. If no further activity occurs, it will be closed. Thank you for your contribution.

We're facing the same issue. Any update on this?

Any workarounds maybe ?

Any workarounds maybe ?

Still none

Was this page helpful?
0 / 5 - 0 ratings

Related issues

manjero picture manjero  路  4Comments

jvlaar picture jvlaar  路  4Comments

gary5 picture gary5  路  4Comments

davidlinse picture davidlinse  路  4Comments

MateuszJeziorski picture MateuszJeziorski  路  3Comments