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

By: Interessante Links im Netz 12 | DaRaFF's Blog

Interessante Links im Netz 12 | DaRaFF's Blog — Tue, 20 Jul 2010 06:42:31 +0000

[...] http://www.onenaught.com/posts/85/turn-your-jquery-code-into-a-richer-unit-testable-plugin [...]

By: Derick Jones

Derick Jones — Fri, 07 May 2010 12:21:15 +0000

I was randomly just browsing sites having jQuery related posts and landed here. Glad that I did! I liked the way you have covered everything in detail, yet it is in an easy to understand manner. I don't know if this will interest you. There is a site called u-2-me. There is a whole community of knowledge providers and knowledge seekers. You can actually engage in online teaching about jQuery. You would be great. Just thought I would let you know.

By: andhapp

andhapp — Fri, 09 Apr 2010 06:57:37 +0000

I have not gone through the entire post but it is very comprehensive and touches everything one needs to know. Amazing work!

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…