protractor-screenshot-reporter
protractor-screenshot-reporter copied to clipboard
swissmanu
Reporter for Protractor. Asks Selenium for a screenshot after every test case and stores it along with test case details.
Tests untruly failing if screenshot taking is still in progress during test shutdown (ECONNREFUSED)
I get sporadically the following errors on using protractor-screenshot-reporter: ``` node_modules/protractor/node_modules/selenium-webdriver/http/index.js:136 callback(new Error(message)); ^ Error: ECONNREFUSED connect ECONNREFUSED at ClientRequest. (node_modules/protractor/node_modules/selenium-webdriver/http/index.js:136:16) at ClientRequest.emit (events.js:95:17) at Socket.socketErrorListener (http.js:1547:9) at Socket.emit (events.js:95:17)...
I have had the reporter working for a year with the 2.5 version of protractor. We recently upgraded protractor to use 4.0 and the reporter stopped working.It silently fails to...
Hi! I quickly ported the code to be compatible with Jasmine 2 and added a path builder which stores the screenshot in an os/browser/version/spec_description1_description2.png path.
Jasmine2 changed the way how to interact with matchers and specs quite a bit. #21 did already some changes to make `protractor-screenshot-reporter` capable of handling the new api. as @kmc059000...
Take screenshots after each failed expect than only after a failed spec.
It would be nice to add cucumber js support.
Adds ability to choose whether to take screenshots at runtime. A use case would be to take screenshot only when 'screenshot' appears in the test description.
I need just the `reporter.html` to be generated not the bunch of `json` files for each suite case. Is it possible to have just the `reporter.html` since having a no....
Jasmine 2 changed the interface for reporters. Clearly this would have to be updated to be compatible with jasmine 2.
