Using this reporter, sometimes Protractor exits before the takeScreenshot() promise is resolved. This causes the last test to occasionally not have a screenshot generated.
My guess would be that _teardownEnv() or the driver's quit() are not chaining onto the last browser action's promise, but I'm unsure. Do you have any ideas why this would happen?
It seems to be a race condition. It only happens sometimes and I've only seen it happen with Firefox (I've tried with Firefox and Chrome)
Using this reporter, sometimes Protractor exits before the
takeScreenshot()
promise is resolved. This causes the last test to occasionally not have a screenshot generated.My guess would be that
_teardownEnv()
or the driver'squit()
are not chaining onto the last browser action's promise, but I'm unsure. Do you have any ideas why this would happen?It seems to be a race condition. It only happens sometimes and I've only seen it happen with Firefox (I've tried with Firefox and Chrome)