-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base 64 generated for Screenshot is not decoded while doing the rendering #85
Comments
Can you try,
Also, try to update |
If I try to use
I am getting below error from selenium
I will try to upgrade to 0.5.2 and let you know |
Recently below piece of code worked fine for me with latest cucumber-html-reporter After(function(scenario, done) { |
There was an issue with combination of Cucumber V2 & Selenium 3, which is fixed in the PR #95 |
fix published with v2.0.2 👍 |
When we are taking a screenshot from the driver and attaching it to the scenario, after generating the report the screenshot is not rendered inside the report.
environment details
browser: chrome Version 58.0.3029.110 (64-bit)
nodejs: 7.10.0
cucumber: 1.0.0
cucumber-html-reporter: 0.5.0
selenium-webdriver:3.4.0
chromedriver: 2.30.0
The reason for that is that when we are attaching the screenshot using below code
It has been encoded twice in base 64. Once when driver is taking the screenshot and second when cucumber is attaching it.
While generating the report we need to decode it as we are doing it in the case of text.
Changing the reporter.js under lib at line 223 from
to
fixes the problem.
The text was updated successfully, but these errors were encountered: