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

Aborts when setting engine to 'slimerjs' #55

Closed
brandondurham opened this issue Sep 3, 2014 · 3 comments
Closed

Aborts when setting engine to 'slimerjs' #55

brandondurham opened this issue Sep 3, 2014 · 3 comments

Comments

@brandondurham
Copy link

As far as I can tell SlimerJS is installed and working properly. However, when I change the engine option in grunt-casper to slimerjs I get an "Aborted due to warnings." message in the console with no error details. Here is What I'm seeing in the console:

Running "casper:functional" (casper) task
>>
Casper Task 'casper:functional' took ~1393ms to run
Warning: Task "casper:functional" failed. Use --force to continue.

Aborted due to warnings.

And here is what I have in my Gruntfile.js:

casper: {
    options: {
        test: true,
        includes: './bower_components/jquery/dist/jquery.min.js',
        engine: 'slimerjs'
    },
    functional: {
        options: {
            args: ['--rooturl=http://<%= connect.options.hostname %>:<%= connect.options.port %>/']
        },
        files: {
            'test/results/functional-results.xml': [
                'test/spec/**/*.js'
            ]
        }
    }
},

Any idea what might be happening?

@iamchrismiller
Copy link
Owner

Thank you.. Looks like the environment export for the binary location wasn't set. I also added slimerjs to package.json. install latest version and let me know if you run into any other issues.

@brandondurham
Copy link
Author

Worked, Chris. Thanks!

@icd2k3
Copy link

icd2k3 commented Feb 6, 2015

I'm still having this issue with 0.4.1 - when I run my tests with the "phantomjs" engine they work fine...

but when using "slimerjs":
Aborted due to warnings. with no details

Any ideas?

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

3 participants