mrooding / gulp-protractor-cucumber-html-report Goto Github PK

From the cucumberjs README, I used these in an 'after scenario' hook:

        scenario.attach('Some text');
        this.After(function (scenario) {
            scenario.attach('{"name": "some JSON"}', 'application/json');
        });

The otherwise lovely HTML report renders 'After undefined'.

e2e-report.zip

If you're using Protractor in combination with CucumberJS there currently is no way to save the CucumberJS JSON output to a file.

The ticket to which that text links is closed as 'done'.

Certainly using the excellent protractor-cucumber, adding resultJsonOutputFile to the config does produce JSON as expected.

Not able to view preety HTML report and embed Screenshots for failed Steps while using protractor-cucumber. Please find out a solution to resolve or give me the steps. I configured gulp protractor plugin but in vain. Codebase is attached.

https://drive.google.com/file/d/0B7rmR9NSjcYtUjNZUkNnTUVRdUE/view?usp=sharing

The "save screenshot" code needs changing. Node conversion from image to base64 was getting corrupted. Not entirely sure why, but it's related to newer version of Node. If you remove the mime type prior to base64 conversion, and omit the conversion to binary, it works fine. The following code works (tested!).

this.After(function (scenario, callback) {
        if (scenario.isFailed()) {
            browser.takeScreenshot().then(function (png) {
                var decodedImage = new Buffer(png.replace(/^data:image\/(png|gif|jpeg);base64,/,''), 'base64');
                scenario.attach(decodedImage, 'image/png');
                callback();
            });
        }
        else {
            callback();
        }
});

It seems cucumber.js is now doing the encoding themselves when attaching pngs. I therefore had to decode twice to get the screenshot ending up viewable in the report:

browser.takeScreenshot().then(function (stream) {
        //double decode the image to workaround the double encoding that cucumber.js+report does
        scenario.attach(new Buffer(new Buffer(stream, 'base64'), 'base64'), 'image/png', function (err) {
          callback(err);
        });
      });

More discussion on this here: cucumber/cucumber-js#275

Here are the relevant packages I'm using:

"cucumber": "^1.2.1",
"gulp-protractor": "^2.4.0",
"gulp-protractor-cucumber-html-report": "^0.1.2",
"protractor": "^4.0.0",
"protractor-cucumber-framework": "^0.6.0",

I'm not sure which tool is doing the wrong thing here, as I don't understand Cucumber's conventions on how to encode embeddings...

Currently , If a scenario outline having examples failed for multiple data rows then screenshot for the last data is captured only and it overwrites the previous files.

Please include possibility to add different screenshot for each Example that failed in Scenario outline

While generating report Data Table not displayed in HTML report. While investigating the problem, I found that JSON generated by cucumberjs is different than expected in gulp-protractor-cucumber-html-report.

The Step function is expecting step.rows, however, cucumber js giving format as
step.arguments[i].rows. Therefore, data table not displayed in the report.

Get Step function -

/**

• Return html code of step element based on step template
• @param step - object which contains step data
• @returns string
  */
  function getStep(step) {
  var template = fs.readFileSync(templates.stepTemplate),
  compiled = lodashTemplate(template.toString());

return compiled({
  status: step.result ? step.result.status : '',
  errorDetails: step.result ? toHtmlEntities(step.result.error_message) : '',
  name: step.keyword + (step.name ? step.name : ''),
  **dataTable: step.rows ? step.rows : ''**
});

}

CucumberJS Generated JSON -

{
"arguments": [
{
"rows": [
{
"cells": [
"user",
"password"
]
},
{
"cells": [
"dcadmin",
"dcadmin"
]
}
]
}
],
"keyword": "And ",
"name": "I enters credentials as below",
"result": {
"status": "passed",
"duration": 6060613
},
"line": 7,
"match": {
"location": "E:\Deployment_Center\Cucumber\Protractor\step_definitions\LoginStepDef.js:21"
}
}

The report now probably does not work well for running protractor with multipleCapabilities. Verify current behaviour and possible add proper support for this

It would be very useful to add a sample screenshot to readme.md to provide an early feedback about the capabilities of this package.

I follow the usage docs by making a gulp task:

gulp.task('cucumber-report', function () {
gulp.src('features/reports/cucumber_report.html.json')
.pipe(protractorReport({
dest: 'reports/'
}));
});

And then I run this task through the command line:
gulp cucumber-report

But it gives this error:
ReferenceError: protractorReport is not defined

What is "protractorReport" supposed to be? I thought this module was supposed to allow me to point to the output json file from cucumberjs and then it generates a nice html file. Is that true?

it fails if the report directory does not exist. either check and create it or remove

I have two features each with 2 scenarios. With format: 'json' and the code snippet (without fs-extra) I noticed that my file gets overwritten and only the last run output survives.

I am using cucumber-tsflow

What can be causing the problem ?