I've used Selenium with Cucumber just enough to know that I want to
try it more. I've segregated my tests into non-javascript cucumber
features that run fast and javascript tests that run much slower. I
run the fast tests with autotest as I develop features. Everything
ought to degrade nicely, so I develop these features first. Then as
javascript or ajax features are added, I can manually run the
javascript cucumber features which need Selenium. Not everything needs
to be tested through selenium, so I do not worry so much about the
speed. I haven't used this setup much yet, but so far I like the

>From this page it looks like you do not need to run jruby to use
culerity. Celerity runs in JRuby, but your application doesn't need


On Tue, Jan 11, 2011 at 7:21 PM, Bess Sadler <bess.sad...@gmail.com> wrote:
> Can anyone recommend a javascript testing framework? At Stanford, we know we 
> need to test the js portions of our applications, but we haven't settled on a 
> tool for that yet. I've heard good things about celerity 
> (http://celerity.rubyforge.org/) but I believe it only works with jruby, 
> which has been a barrier to getting started with it so far. Anyone have other 
> tools to suggest? Is anyone doing javascript testing in a way they like? Feel 
> like sharing?
> Thanks!
> Bess

Reply via email to