Open bentolor opened 10 years ago
i'm not sure if this could really be fixed by the protractor-screenshot-reporter
.
the reporter only calls the webdriver api which completly handles the selenium browser lifecycle.
maybe you can supply more details otherwise?
I read the stacktrace in that way, that Jasmine fails because it receives an Exception on calling ScreenshotReporter.reportSpecResults()
via jasmine.Spec.finishCallback
.
Pretty sure protractor-screenshot-reporter
cannot avoid the failure during taking the screenshot. But I guess it can easily avoid the test failure of Jasmine by simple swallowing Exceptions received byScreenshotReporter.reportSpecResults()
on calling the Webdriver API?
This is hitting our continuous integration - can anyone suggest a workaround ?
I get sporadically the following errors on using protractor-screenshot-reporter:
Obviously the issue is that the Jasmine/Protractor-Tests already are shutting down and therefore the PhantomJS process terminates while the screenshot taking is still in progress.
In my opinition screenshot reporter should fail silently & gracefully instead of pulling the test itself into damnation here.