-
Notifications
You must be signed in to change notification settings - Fork 123
can't run #1
Comments
Please tell me your node, Gruntjs and protractor version. Which OS did you run on? |
Hi, 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. |
Failed without an error before. These changes fix it, taken from: teerapap#1 Awaiting response from the developer, and / or a proper fix.
Having the same issue. The fix by @julrich seems to fix the problem. |
@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.
|
… data.configFile reference from tasks/protractor_runner.js to fix a problem with the protractor task not being registered correctly with Grunt, see issue teerapap#1
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.
The text was updated successfully, but these errors were encountered: