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

getting started #24

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

getting started #24

pjkix opened this issue Jan 3, 2014 · 11 comments

Comments

@pjkix
Copy link

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
Copy link

Same error on ubuntu

@benjaminach
Copy link

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

@mejarc
Copy link

mejarc commented Jan 12, 2014

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

@natchiketa
Copy link

Same issue as OP, but not when using PhantomJS:

1__bash

@doctyper
Copy link

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
Copy link

Same issue here, with firefox,phantomjs and chrome

@carwin
Copy link

carwin commented Nov 13, 2014

Also having this issue with Firefox.

@iamnewton
Copy link

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
Copy link

carwin commented Dec 18, 2014

At the moment only phantomjs is really working for me.

@laurentbristiel
Copy link

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

@indraneelr
Copy link

@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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants