sandy-adi / protractor-jasmine2-screenshot-reporter Goto Github PK

Reporter for Protractor that will capture a screenshot after each executed test case and store the results in a HTML report. (supports jasmine2)

The protractor-jasmine2-screenshot-reporter is available via npm:

$ npm install protractor-jasmine2-screenshot-reporter --save-dev

In your Protractor configuration file, register protractor-jasmine2-screenshot-reporter in jasmine:

var HtmlScreenshotReporter = require('protractor-jasmine2-screenshot-reporter');

exports.config = {
   // ...

   onPrepare: function() {
      jasmine.getEnv().addReporter(
        new HtmlScreenshotReporter({
          dest: 'target/screenshots',
          filename: 'my-report.html'
        })
      );
   }
}

Output directory for created files. All screenshots and reports will be stored here.

If the directory doesn't exist, it will be created automatically or otherwise cleaned before running the test suite.

jasmine.getEnv().addReporter(new ScreenShotReporter({
   dest: '/project/test/screenshots'
}));

Filename for html report.

jasmine.getEnv().addReporter(new ScreenShotReporter({
   filename: 'my-report.html'
}));

Default is report.html

When this option is enabled, reporter will not create screenshots for pending / disabled specs. Only executed specs will be captured.

jasmine.getEnv().addReporter(new ScreenShotReporter({
   ignoreSkippedSpecs: true
}));

Default is false

When this option is enabled, reporter will create screenshots only for specs that have failed their expectations.

jasmine.getEnv().addReporter(new ScreenShotReporter({
   captureOnlyFailedSpecs: true
}));

Default is false

Function used to build custom paths for screenshots. For example:

jasmine.getEnv().addReporter(new ScreenShotReporter({
   pathBuilder: function(currentSpec, suites, browserCapabilities) {
      // will return chrome/your-spec-name.png
      return browserCapabilities.get('browserName') + '/' + currentSpec.fullName);
   }
}));

By default, the path builder will generate a random ID for each spec.

Function used to build custom metadata objects for each spec. Files (json) will use the same filename and path as created by Path Builder. For example:

jasmine.getEnv().addReporter(new ScreenShotReporter({
   metadataBuilder: function(currentSpec, suites, browserCapabilities) {
      return { id: currentSpec.id, os: browserCapabilities.get('browserName') };
   }
}));

By default, the runner builder will not save any metadata except the actual html report.