When there is a parsing error we should exit with a non 0 exit code

midniteio / multi-cuke

Parallel cucumber-js testing via Node's child_process.spawn api

13 stars 4 forks source link

When there is a parsing error we should exit with a non 0 exit code #54

Closed vsiakka closed 8 years ago

vsiakka commented 8 years ago

Make sure multi-cuke raises a non 0 exit code when we can't parse the a feature
Make sure multi-cuke raises a non 0 exit code when the parser raises an exception
Make feature parsing errors more readable

This also addresses https://github.com/midniteio/multi-cuke/issues/24 @midniteio @efokschaner @guykisel

mention-bot commented 8 years ago

@vsiakka, thanks for your PR! By analyzing the annotation information on this pull request, we identified @midniteio and @guykisel to be potential reviewers

guykisel commented 8 years ago

:+1: