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

getting started #24

Open
pjkix opened this Issue Jan 3, 2014 · 11 comments

Comments

Projects
None yet
10 participants
@pjkix

pjkix commented Jan 3, 2014

I'm having trouble getting started with hardy. I followed all the steps here http://hardy.io/getting-started.html
but when i try and run the example test i just see a blank firefox window and this output in the console.

$ hardy . 
Hardy v1.1.0

INFO Loading browser firefox
.F
INFO Shutting down browser
firefox success

am i missing something?

@benjaminach

This comment has been minimized.

Show comment
Hide comment
@benjaminach

benjaminach Jan 3, 2014

Same error on ubuntu

Same error on ubuntu

@benjaminach

This comment has been minimized.

Show comment
Hide comment
@benjaminach

benjaminach Jan 3, 2014

Test with phantomjs "hardy --browser=phantomjs ."

Test with phantomjs "hardy --browser=phantomjs ."

@mejarc

This comment has been minimized.

Show comment
Hide comment
@mejarc

mejarc Jan 12, 2014

I'm getting that result with hardy --browser=phantomjs . as well.

mejarc commented Jan 12, 2014

I'm getting that result with hardy --browser=phantomjs . as well.

@natchiketa

This comment has been minimized.

Show comment
Hide comment
@natchiketa

natchiketa Jan 24, 2014

Same issue as OP, but not when using PhantomJS:

1__bash

Same issue as OP, but not when using PhantomJS:

1__bash

@doctyper

This comment has been minimized.

Show comment
Hide comment
@doctyper

doctyper Jan 28, 2014

I'm also seeing the same issue. Running OS X Mavericks, node 0.10.24. Rolling back to hardy 1.0.1 did not make a difference, the error persists.

I'm also seeing the same issue. Running OS X Mavericks, node 0.10.24. Rolling back to hardy 1.0.1 did not make a difference, the error persists.

@JHeimbach

This comment has been minimized.

Show comment
Hide comment
@JHeimbach

JHeimbach May 15, 2014

Same issue here, with firefox,phantomjs and chrome

Same issue here, with firefox,phantomjs and chrome

@carwin

This comment has been minimized.

Show comment
Hide comment
@carwin

carwin Nov 13, 2014

Also having this issue with Firefox.

carwin commented Nov 13, 2014

Also having this issue with Firefox.

@chrisopedia

This comment has been minimized.

Show comment
Hide comment
@chrisopedia

chrisopedia Dec 9, 2014

Is everyone still having this issue? I just set up via the Getting Started, and I'm getting the same thing. I'm pretty sure this has something to do with the Firefox drivers, because when I run hardy --browser=phantomjs,chrome . I get results from the tests.

Is everyone still having this issue? I just set up via the Getting Started, and I'm getting the same thing. I'm pretty sure this has something to do with the Firefox drivers, because when I run hardy --browser=phantomjs,chrome . I get results from the tests.

@carwin

This comment has been minimized.

Show comment
Hide comment
@carwin

carwin Dec 18, 2014

At the moment only phantomjs is really working for me.

carwin commented Dec 18, 2014

At the moment only phantomjs is really working for me.

@laurentbristiel

This comment has been minimized.

Show comment
Hide comment
@laurentbristiel

laurentbristiel Dec 19, 2014

same here. Works with phantomJS and Chrome (+chromedriver) but fails with Firefox (version 31)

same here. Works with phantomJS and Chrome (+chromedriver) but fails with Firefox (version 31)

@indraneelr

This comment has been minimized.

Show comment
Hide comment
@indraneelr

indraneelr May 17, 2015

@pjkix Turns out that in any browser other than firefox, this happens if there is any error in your .feature file. For example, if you mentioned a wrong css property. In my case I was measuring "font-color" instead of "color".
Seems like it eats up the error returned by cucumber.js and returns a success message.
Running cucumber manually helped finding out the error:

cucumber.js -f pretty -r selectors.js -r /path/to/localnpminstall/node_modules/hardy/features/step_definitions --browser=phantomjs test.feature

@pjkix Turns out that in any browser other than firefox, this happens if there is any error in your .feature file. For example, if you mentioned a wrong css property. In my case I was measuring "font-color" instead of "color".
Seems like it eats up the error returned by cucumber.js and returns a success message.
Running cucumber manually helped finding out the error:

cucumber.js -f pretty -r selectors.js -r /path/to/localnpminstall/node_modules/hardy/features/step_definitions --browser=phantomjs test.feature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment