Issues with Protractor and `process.uncaughtException`

Hi there,

this is not quite an issue, more of a discussion. Please let me know if there’s a more helpful venue for this

We’ve had some issues on Protractor about removing our usage of process.on('uncaughtException') because it clobbers the cucumber uncaughtExceptionErrorHandler.

This is a bit of a difficult issue because both projects expect to be the “end of the line”. This is similar with other frameworks like mocha. Unfortunately, there seems to be a disconnect with handling certain types of exceptions in cucumber that does not present itself in Mocha.

Is there a way we could work together to figure something out? Ideally both projects could play nicely without compromising the ability to safely recover from errors.

I’m happy to help and coordinate from the protractor side.

[NickTomlin]

After doing some more investigation, this seems to be an issue with the way that protractor-cucumber-framework’s use of Cucumber.Cli handles rejections in promises. I’m not sure if this is actually due to Cucumber itself (since it handles this just fine).

I’m going to go ahead and close this for now and follow up with the protractor-cucumber-framework folks. I’ll re-open and ping you if this does turn out to be something that needs changes in cucumber core.

Thanks!

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.