I'd also be interested in this, and in actually contributing this myself if it doesn't turn out to be a huge job :-).
Currently I've nearly got Cucumber-JS set up locally to run standalone in a browser and run my tests there, which I think is all that'll be needed on that side. Unfortunately this means my team will have to keep refreshing this page in the background to actually run their tests, and we can't run these in CI, both of which are quite annoying.
I think to fix all of this all I need to do is create a cucumberRunner.js in Chutzpah/JSRunners and then tie it in to the rest of Chutzpah somehow. Could you give me some kind of idea what else actually needs doing, and what cucumberRunner.js would need to do from Chutzpah's end? Any pointers would be great :D
Currently I've nearly got Cucumber-JS set up locally to run standalone in a browser and run my tests there, which I think is all that'll be needed on that side. Unfortunately this means my team will have to keep refreshing this page in the background to actually run their tests, and we can't run these in CI, both of which are quite annoying.
I think to fix all of this all I need to do is create a cucumberRunner.js in Chutzpah/JSRunners and then tie it in to the rest of Chutzpah somehow. Could you give me some kind of idea what else actually needs doing, and what cucumberRunner.js would need to do from Chutzpah's end? Any pointers would be great :D