Skip to content
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

Config file is never read #18

Open
simbas opened this issue Oct 24, 2012 · 0 comments
Open

Config file is never read #18

simbas opened this issue Oct 24, 2012 · 0 comments

Comments

@simbas
Copy link

simbas commented Oct 24, 2012

the config file tasks/jasmine/phantom-config.json is never read.

Use this configuration:

{
  "webSecurityEnabled" : false
}

and log the phantom.defaultPageSettings.webSecurityEnabled property.

quick fix: change the arguments in the call of phantomjs helper from:

args : [
  // The main script file.
  grunt.task.getFile( 'jasmine/phantom-jasmine-runner.js' ),
  // The temporary file used for communications.
  tempfile.path,
  // The Jasmine helper file to be injected.
  grunt.task.getFile( 'jasmine/jasmine-helper.js' ),
  // URL to the Jasmine .html test file to run.
  url,
  timeout,
  // PhantomJS options.
  '--config=' + grunt.task.getFile( 'jasmine/phantom-config.json' )
]

to:

args : [
  // PhantomJS options.
  '--config=' + grunt.task.getFile( 'jasmine/phantom-config.json' ),
  // The main script file.
  grunt.task.getFile( 'jasmine/phantom-jasmine-runner.js' ),
  // The temporary file used for communications.
  tempfile.path,
  // The Jasmine helper file to be injected.
  grunt.task.getFile( 'jasmine/jasmine-helper.js' ),
  // URL to the Jasmine .html test file to run.
  url,
  timeout
]

Moreover, it could be great to have the ability to set a config file path from the gruntfile.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant