Comments on: Dead simple JavaScript Unit Testing in Rails

By: Testing the javascripts « The Stickies Project

Testing the javascripts « The Stickies Project — Thu, 31 Dec 2009 21:19:35 +0000

[...] and I have a lot of respect for their code. There are other blog posts (Jason Rudolph’s and Dr Nic’s) that outline the inner details and usage of Blue Ridge (it packages other tools, such as [...]

By: Ennuyer.net » Blog Archive » Rails Reading - December 16, 2009

Ennuyer.net » Blog Archive » Rails Reading - December 16, 2009 — Wed, 16 Dec 2009 13:10:35 +0000

[...] Dr Nic ’s Dead simple JavaScript Unit Testing in Rails [...]

By: Dr Nic

Dr Nic — Mon, 16 Nov 2009 01:26:04 +0000

@micah, the minimalistic option is to drop a note in the Issues tracker for the project on github with your gist etc. Hopefully someone else then decides they want to do all the work of writing unit tests etc.

Or, it’s a great opportunity to have a look in the blue-ridge project, figure out where you could write unit tests to test that “if I have a spec that is destructive to the DOM, the next spec still sees the original DOM” for example.

I think I did attempt to do this once, and couldn’t figure out how I hooked stuff into Screw.Unit. Yeah, it didn’t seem obvious at all. You might need to ask a screw.unit person for help.

Definitely a great patch though if you can wire it in!

By: Micah Geisel

Micah Geisel — Sun, 15 Nov 2009 23:08:29 +0000

it works! i had to wrap the html fixture in a div.fixture to avoid stomping on the test runner’s html, but this could be avoided by integrating these changes directly into blue ridge.

http://gist.github.com/235556

ive never really had anything worth contributing back until now, how best to proceed? open a dialog with relevance?

By: Dr Nic

Dr Nic — Sun, 15 Nov 2009 21:48:36 +0000

@micah, I think someone else mentioned the $.fn.clone method after the session. I completely forgot about it til now. It could be quickly tested in a before/after block pair before being imported into blueridge.

By: Micah Geisel

Micah Geisel — Sun, 15 Nov 2009 21:36:15 +0000

Regarding the problem concerning DOM transactions, perhaps we could set up the initial state (events and all) inside of an iframe. Then, before each test, we could use $.fn.clone(true) to copy this state (events and all) into the main html file.

What do you think?

By: InVisible Blog » links for 2009-11-13

InVisible Blog » links for 2009-11-13 — Fri, 13 Nov 2009 16:01:54 +0000

[...] 13th, 2009 Dr Nic ’s Dead simple JavaScript Unit Testing in Rails (tags: javascript testing rails tdd bdd video js) How To Start A Rails Edge App The Easy Way | [...]

By: Replica Christian Louboutin

Replica Christian Louboutin — Fri, 13 Nov 2009 12:11:58 +0000

Just get online today and you will see what is all about, they have the most beautiful stuff that you have ever seen, check it out, you won´t regret it.

By: Michael Krisher

Michael Krisher — Thu, 12 Nov 2009 15:41:46 +0000

For those wanting to just dip their toe in the JavaScript testing water, I wrote a Rails plugin that allows for easy setup and functional testing of JavaScript using QUnit from the jQuery folks. I tried to make it extremely easy to use thinking it was more for people new to JS testing:

http://github.com/mkrisher/qunit_for_rails

By: Nando Vieira

Nando Vieira — Thu, 12 Nov 2009 14:17:58 +0000

Have you considered JSpec (http://jspec.info)? From all the frameworks I have tested, JSpec was the best one… it has jQuery integration, a syntax similar to Ruby/RSpec and is being actively developed.

I’m using it in all my latest projects!