Comments on: Getting Started With jQuery QUnit for Client-Side Javascript Testing

By: Deborah Smith

Deborah Smith — Wed, 07 Sep 2011 07:56:00 +0000

I recently came across your blog and have been reading and watching videos along.I thought I would leave my first comment.I do not know what to say except that I enjoyed reading what you have to say. find a job

By: Craig Buchek

Craig Buchek — Wed, 01 Oct 2008 02:00:26 +0000

It appears that your SetUp and TearDown features are already included in QUnit, as optional arguments to module(). Admittedly, it’s a bit odd place to put them, especially since the options are collectively called “lifecycle”.

By: ph

ph — Wed, 10 Sep 2008 07:35:33 +0000

When I copied the first program the outcome is only
“My Foo test” and nothing… Something wrong?

By: Ken Ko

Ken Ko — Sun, 07 Sep 2008 14:46:16 +0000

Hi, I’ve written a mock framework for jquery’s jqUnit framework, but haven’t been able to get the word out. Have a look if you are interested!

http://code.google.com/p/jqmock/

By: james

james — Fri, 05 Sep 2008 20:17:05 +0000

i need this to listen to music

By: Mika Tuupola

Mika Tuupola — Wed, 03 Sep 2008 10:56:09 +0000

Good timing on article. I just wrote my first unit tests two days ago using QUnit.

http://www.appelsiini.net/projects/jeditable/tests/

By: Peter Eysermans

Peter Eysermans — Wed, 03 Sep 2008 08:33:21 +0000

Nice introduction of QUnit, I’ve been using it in some of my projects.

I’m really looking forward to the article(s) about mocking with JavaScript, especially mocking QUnit resultsets (like $(‘div.my-class’). I’m currently struggling with that one and it’s been holding me back when trying to test client side code.

By: nap

nap — Mon, 01 Sep 2008 02:21:00 +0000

Great writeup chad, many thanks!

By: Chad Myers

Chad Myers — Sun, 31 Aug 2008 18:27:38 +0000

@Joe:

Right now all it tells us is whether all the tests passed or not, which is good enough for basic CI integration. At some point, in our copious amounts of free time, I’d like to be able to have all the tests matched somehow in C# so that a.) they add to our total test count b.) we can get better visibility when something goes wrong and c.) we can get (maybe) some test timings out of TeamCity.

Oh yeah, the whole TESTRESULTS thing is a customization we made for QUnit’s testrunner.js. I believe this change was accepted into the JQuery trunk, so it should be there. if not, it should be trivial to add yourself.

I’ve been thinking about forking the QUnit trunk to make it more xUnit-style (it isn’t right now, and the jQuery folks don’t seem to be too interested in making it so). Plus, I was thinking some basic expectation-based mocking might be useful, too. Right now we’re doing test double-style mocking which gets annoying after just a few of them.

By: Joe Ocampo

Joe Ocampo — Sun, 31 Aug 2008 17:16:58 +0000

@Josh

nice!