-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refold from caseygoodhew/grunt-cucumber #104
Conversation
…t tasks from running
@@ -184,10 +184,8 @@ module.exports = function(grunt) { | |||
handler(grunt, options, commands, function handlerCallback(err) { | |||
if (err) { | |||
grunt.log.error('failed tests, please see the output'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invoking done(false) causes the grunt task to report a failure, which probably isn't the desired intention here - failed tests should not result in a failed grunt task.
The issue with this is that any subsequent grunt tasks do not run. In our case, our grunt command sequence looked like:
['mockserver_start', 'cucumber', 'mockserver_stop']
In this case, if a test case failed, mockserver_stop was never invoked.
The expected behavior is that the task should succeed and failures should be dealt with by inspecting the test results in a subsequent step / process.
Looks good. I apologise, I don't get notifications from this repo for whatever crazy reason. |
Thanks! |
-- Applied suggested fixes from ESLINT
-- Comment inline about potential breaking change in failed test handling