Skip to content
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.

jasmineNodeOpts #132

Open
scriby opened this issue Sep 10, 2015 · 5 comments
Open

jasmineNodeOpts #132

scriby opened this issue Sep 10, 2015 · 5 comments

Comments

@scriby
Copy link

scriby commented Sep 10, 2015

I see support for cucumberOpts and mochaOpts... but no jasmine options. Am I missing something or is that a miss?
@scriby scriby mentioned this issue Sep 17, 2015
Open
@sakshinagpal
Copy link

Any update on this issue ?

@F1LT3R
Copy link

F1LT3R commented Jan 15, 2016

The jasmineNodeOpts don't seem to be picked up when grunt is running for some reason here too. (And I think this is not limited to grunt-protractor-runner. Just doing a shell command to run protractor manually from grunt, also fails to pick up the opts. Odd.

@ghost
Copy link

ghost commented Jun 14, 2016

Same issue here

@mindywhitsitt
Copy link

+1

@sakshinagpal
Copy link

Try with the below tweak

Go to grunt-protractor-runner\tasks\protractor_runner.js
Add jasmineNodeOpts in objectArgs array

mindywhitsitt added a commit to mindywhitsitt/grunt-protractor-runner that referenced this issue Jun 16, 2017
@mindywhitsitt
pass jasmineNodeOpts; resolves teerapap#132 and teerapap#133
b5bac3b
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@scriby @F1LT3R @mindywhitsitt @sakshinagpal