This replaces the current fork + cucumber-js API approach with directly spawning a new process that shells out to cucumber-js. This way, if cucumber-js ends for any reason (crash, regular test failure, etc.) we'll still detect the process has exited and handle it properly.
midniteio
commented
8 years ago
@midniteio @efokschaner @vsiakka
This replaces the current fork + cucumber-js API approach with directly spawning a new process that shells out to cucumber-js. This way, if cucumber-js ends for any reason (crash, regular test failure, etc.) we'll still detect the process has exited and handle it properly.