Hardy icon indicating copy to clipboard operation
Hardy copied to clipboard

getting started

Open pjkix opened this issue 10 years ago • 11 comments

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?

pjkix avatar Jan 03 '14 01:01 pjkix

Same error on ubuntu

benjaminach avatar Jan 03 '14 14:01 benjaminach

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

benjaminach avatar Jan 03 '14 14:01 benjaminach

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

mejarc avatar Jan 12 '14 23:01 mejarc

Same issue as OP, but not when using PhantomJS:

1__bash

natchiketa avatar Jan 24 '14 15:01 natchiketa

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.

doctyper avatar Jan 28 '14 19:01 doctyper

Same issue here, with firefox,phantomjs and chrome

jheimbach avatar May 15 '14 22:05 jheimbach

Also having this issue with Firefox.

carwin avatar Nov 13 '14 09:11 carwin

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.

iamnewton avatar Dec 09 '14 18:12 iamnewton

At the moment only phantomjs is really working for me.

carwin avatar Dec 18 '14 16:12 carwin

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

laurentbristiel avatar Dec 19 '14 11:12 laurentbristiel

@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

indraneelr avatar May 17 '15 17:05 indraneelr