Comments on: Autotesting Javascript in Rails

By: Ed Spencer

Ed Spencer — Fri, 18 Apr 2008 19:39:56 +0000

Thanks for this, I’ve got a Windows solution for you.

I had to take the contents of js_autotest and chuck it in with the javascript_test_autotest_tasks.rake, as well as change rake to rake.bat - like this:

# javascript_test_autotest_tasks.rake
namespace :test do
namespace :recent do
#untouched
end

task :javascript_autotest do
system(’ruby script/rstakeout “rake.bat test:recent:javascript” test/javascript/*_test.html test/javascript/samples/*/* public/javascripts/*.js’)
end
end

Then obviously rake test:javascript_autotest from windows command line and everything seems to work pretty well. I’ve only tested it with a few trivial examples but it detects the right changes and runs the right tests so it looks promising.

It’s pretty trivial but I’ll submit a patch after I get back from the pub.

By: Automating Javascript Unit Tests / Specs - Part 1 — blog.mattwynne.net

Automating Javascript Unit Tests / Specs - Part 1 — blog.mattwynne.net — Sun, 06 Apr 2008 02:43:08 +0000

[...] think my next step is to take another look at what Thomas Fuchs has been up to, and also this rails-based effort from Dr Nic. We’re using the prototype.js framework anyway, so this seem like it would be a [...]

By: massimiliano

massimiliano — Sat, 26 Jan 2008 13:35:05 +0000

Great work!!!

On Mac OS X Leopard I had to change the first line of file script/rstakeout to

#!/usr/bin/ruby -w

By: Recompilação dos últimos links interessantes

Recompilação dos últimos links interessantes — Sat, 19 Jan 2008 14:24:29 +0000

[...] tutoriais e artigos técnicos interessantes que chamaram nossa atenção foram aqueles chamados Autotestando JavaScript em Rails, de Dr. Nic, que explica como testar nossos scripts em JavaScript desde um script em Rails, [...]

By: Mark

Mark — Fri, 11 Jan 2008 19:01:06 +0000

Windows Users have symbolic links! It’s just not well publicized:
http://shell-shocked.org/article.php?id=284
I use this program to easily create them:
http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html

Looking forward to the upcoming peepcode episode!

By: Dr Nic

Dr Nic — Fri, 11 Jan 2008 10:14:30 +0000

@Scott Becker [via] - sorry Scott The patches have all been applied now so future readers can live in a happy place that you were denied

By: Ruby, Rails, JavaScript « exceptionz

Ruby, Rails, JavaScript « exceptionz — Tue, 08 Jan 2008 10:30:42 +0000

[...] Autotesting JavaScript in Rails - Dr. Nic show us how to use the javascript_test plugin together with the ZenTest autotest script. [...]

By: maruis

maruis — Tue, 08 Jan 2008 09:39:28 +0000

Great intro into tdd’ing js. I am looking forward to the peepcode screen cast. I would definably be interested when it’s released.

Good news to hear Jeffrey is going to be a dad. He will enjoy the baby a lot…

Cheers…

By: napyfab:blog» Blog Archive » links for 2008-01-07

napyfab:blog» Blog Archive » links for 2008-01-07 — Mon, 07 Jan 2008 23:30:43 +0000

[...] Dr Nic » Autotesting Javascript in Rails (tags: javascript testing rails rubyonrails tdd ruby ajax howto framework development ror) [...]

By: Dr Nic

Dr Nic — Mon, 07 Jan 2008 21:56:12 +0000

@Martin Ström [via] - I under the desire to ensure the view being tested is the same, and the desire to be DRY about it.

My solution is to generate sample HTML, built from views, into my test/javascript/samples folder, and then load them into the html unittest page via synch GET request (synch Ajax request). I create the samples manually or via a rake task. Its very tricky convincing an ActionView::Base to render a template without a full request stack in place, but I’ve got a little helper method that tricks out a pretend request+controller.

I’ll post about it later when its all cleaned up, and the loadSample() JS helper patch is accepted into unittest.js.

But, with generated sample HTML for tests, I think that gives me enough DRYness.