Drogomir's blog - Cucumber and Celerity - testing unobtrusive javascript Comments

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by dolphin

2010-03-04T11:01:58Z

actually run my javascript. It’s awesome because it’s headless, and far more reliable then Selenium (you can read more about it in Our Testing Stack ). But, I ran into an issue the other day, 70-450 dumps exposing an interesting facet of ruby that others might find it useful to know.

We run Celerity in a separate process from the one that is actually running our tests (in Cucumber).

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by mkuklis

2009-10-18T05:25:46Z

cool article! thanks for sharing!

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by jp

2009-08-05T10:05:23Z

Oops, sorry about that. Guess it’s #exit in Culerity and #close in Celerity.

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by Piotr Sarnacki

2009-07-11T20:42:11Z

@Andy, Matt

Sorry for that, I didn’t check it and blindly took jb at his word and changed it from exit to close. I’ve reverted that commit.

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by Andy Watts

2009-07-11T17:16:19Z

Thanks for posting this. Saved me a bunch of time.

I also had to change $browser.close with $browser.exit.

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by Matt

2009-07-06T08:47:16Z

I couldn’t work out why after all my tests were passing the browser process was hanging until I replaced $browser.close with $browser.exit, which worked for me. Also, from a quick look at the source code, this seems to be correct. Thanks for the great article.

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by Piotr Sarnacki

2009-06-17T09:12:31Z

jb: thanks for pointing it out, corrected.

Comment on 'Cucumber and Celerity - testing unobtrusive javascript' by jb

2009-06-16T22:37:08Z

There’s a typo in the at_exit hook – should $browser.close instead of $browser.exit