Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Here is my Gruntfile.js:
When I run "grunt protractor", I get this output and nothing else:
I tried adding a console.log call inside the task definition and that is not output.
I was having this issue too.
I'm running Linux Mint.
Running "grunt protractor" would give me a "Done, without errors." message without actually running protractor.
"grunt protractor --verbose" gave interesting results:
It looks like the protractor task isn't being registered? In protractor_runner.js I switch the register signature from registerMultiTask to registerTask and dropped the special configFile block (configFile is pulled in by this.options()).
This fixed the problem for me.
Running "grunt protractor" ran protractor correctly with my specified config file.
I'm not sure if switching from a multi-task to a plain registerTask is the way to go, so I'm not submitting a pull request.
I ran into this same issue and @pcorey's solution above got it up and running for me.
I'm in the same boat on this, however, so I'd be interested to see a preferred resolution or alternative in place.
@pcorey Thanks! I cannot reproduce this issue so I cannot debug it. I think I have to keep registering the task with registerMultiTask because someone may be using the task with multi configuration. However, thank you very much for this clue.
and the block below is for backward compatibility with my mistake in the early version.