Comments on: Turn your jQuery code into a richer, unit testable, plugin

By: Josh Ribakoff

Josh Ribakoff — Fri, 29 Jan 2010 04:31:53 +0000

Hey, I don’t think we’re talking about the same thing. I took a look at JSunit and it has that feature. I just wrote an article and pinged back, it shows exactly what I meant and shows the “test page runner” i wrote for qunit. It execute your pages and aggregates their results in one place, although it doesn’t have the fancy progress bar that jsunit has.

By: Javascript Unit Testing, Test Pages (test classes). « Web Application Development, E-commerce, Sales & Marketing

Fri, 29 Jan 2010 04:25:26 +0000

[...] is another topic. I’ll have to give a ping back to Anup Shah for teaching me that art. Comments [...]

By: Anup Shah

Anup Shah — Tue, 26 Jan 2010 12:15:34 +0000

@Josh: If you see the unit tests I used in the full example, I tried to break each test down to a reasonable test case/scenario. I dunno if that helps answer the question you had in that forum post?

By: R.L.

R.L. — Fri, 22 Jan 2010 18:11:24 +0000

Just getting started with QUnit. Thanks for the very helpful information!

By: Josh Ribakoff

Josh Ribakoff — Fri, 22 Jan 2010 15:16:33 +0000

Also I should add that qunit’s start() and stop() methods are the key to implementing his asynchronous example.

By: Josh Ribakoff

Josh Ribakoff — Fri, 22 Jan 2010 15:15:28 +0000

Good example, yeah! For any thing that is business logic, you definitely do want to test first. UI stuff generally test last (but take it in the same isolated chunks as you would in a test first approach).

Which is exactly the road block I have run into with qunit

See my post here.. http://forums.devnetwork.net/viewtopic.php?f=13&t=111849

What is your answer to this?

By: Anup Shah

Anup Shah — Fri, 22 Jan 2010 15:11:22 +0000

@Josh: thanks for the comment. Interesting point abotu TDD as a last methodology — yeah, often wouldn’t recommend it, but I read somewhere, and found sometimes myself, that for certain kind of UI things, it sometimes is useful to do a bit later

e.g. if generating a ton of HTML and exploring as you go and then tweaking (usually thanks to IE!) then it may be saner to create the unit tests for that kind of stuff nearer to the end…

By: Josh Ribakoff

Josh Ribakoff — Wed, 20 Jan 2010 17:31:50 +0000

Interesting article, you definitely helped me out. You do a good job articulating why longer lines of code is sometimes desired. I get that a lot when I try to help people decompose their designs. People will say “oh you just made it longer and more complex”.

I have also found that after doing true TDD for a while (like a year), you can almost adopt a test last methodology (although I wouldn’t recommend it).. You just get better at working in small increments after doing true TDD.

By: Anup Shah

Anup Shah — Tue, 03 Nov 2009 18:07:58 +0000

@Paul: the links to the full examples actually work. I looked at the examples in the post again.

I should have clarified that the test() methods that make use of the testUtil object are in the same anonymous function, so it is accessible (if you see the link to the full tests, that is how it is done). I will update the post shortly. Thanks for spotting that.

By: Paul Irish

Paul Irish — Mon, 02 Nov 2009 16:49:28 +0000

From what I’m seeing the plugin code you wrote won’t work with these unit tests.
The unit tests depend on testUtils being globally accessible, but the testUtils object is defined within the plugin function.
You could probably rejigger things a bit to make that work though.