Comments on: One-stop JavaScript Unit Testing for Rails 2.0

By: uberVU - social comments

uberVU - social comments — Sat, 31 Oct 2009 17:00:37 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by bjhess: What’s everyone doing for JS Unit testing? Thought javascript_test plugin, then saw this: http://bit.ly/1HiIXg. Not sure where to go……

By: One-stop JavaScript Unit Testing for Rails 2.0 « A little story

One-stop JavaScript Unit Testing for Rails 2.0 « A little story — Fri, 03 Apr 2009 13:45:15 +0000

[...] April 3, 2009 Source: http://drnicwilliams.com/2008/02/19/one-stop-javascript-unit-testing-for-rails2/ [...]

By: Multiple versions of ruby with stow | MJWall.com

Multiple versions of ruby with stow | MJWall.com — Sat, 16 Aug 2008 22:48:25 +0000

[...] Multiruby looks like it may do what I want. I already have it installed, because I am autotest-addicted (first coined by Dr Nic. [...]

By: James Seigel

James Seigel — Mon, 30 Jun 2008 14:50:49 +0000

Just wondering if you’ve managed to integrate this into something like cruisecontrol.rb in a way that would close the browsers after?

Cheers
James.

By: Dr Nic

Dr Nic — Fri, 30 May 2008 21:21:50 +0000

You can have 2xRunners. There should be an inline comment decribing what to do.

By: Miho

Miho — Fri, 30 May 2008 17:52:29 +0000

Hi Dr Nic, thank you for your reply.
Turned out if you have more than 1 Test.Unit.Runner within 1 xxx_test.html file, you will not get the results (number of failures and errors) back to the terminal. Now we have separated all the Test.Unit.Runner to each xxx_test.html file, it’s all good. We should have done this way from the beginning anyways!

By: Dr Nic

Dr Nic — Thu, 29 May 2008 01:24:06 +0000

Hmm, it should display errors back in the terminal – that’s kind of its purpose. I don’t use it much so I haven’t noticed it behaving badly. The code comes from the prototypejs project – so they might have some more recent commits to fix any issues etc, and these fixes can be ported back across.

By: Miho

Miho — Thu, 29 May 2008 00:56:57 +0000

Hi Dr Nic,

Thank you very much for your javascript_unittest plugin. We are enjoying it very much:)

One question though. Seems like when we run tests from rake command, we don’t get the feedback of failures and errors. Here is the output from rake command.

$ rake test:javascripts

Started tests in Firefox
..
Finished in 1 seconds.
0 tests, 104 assertions, 0 failures, 0 errors

We have failures and errors and see them red on the browser. I’m wondering if there is a way for us to see that in the terminal rather than checking the browser every time. And if there is a way, it will help us to make it automated test!

By: Dr Nic

Dr Nic — Wed, 02 Apr 2008 07:21:42 +0000

@will bailey [via] – the mechanism that makes the generator available to rails is new to rails 2.0 – it can find generators within gems (within /rails_generator folders).

What you can do is create a ~/.rails/generators folder, and copy the entire generator folder from within the gem into it. Then all your rails applications will have access to the generator. Make sense?

By: will bailey

will bailey — Tue, 01 Apr 2008 18:26:54 +0000

Hey Dr Nic,

Can this gem be used in a rails 1.2.6 project? We’ve not yet upgraded to Rails 2, but I’d like to take advantage of this cool gem you’ve developed.

Thanks!