On 5 Mar 2009, at 09:15, Saq Imtiaz wrote:
>
> Do we have a testing framework in place for the jQuery enabled
> release?
> I'd like to suggest that all refactoring be accompanied with unit
> tests for the corresponding code. This will help catch possible bugs
> and lead to better code coverage which will be helpful in the long
> run, and I don't think the cost in terms of time or effort will be
> very high. The key is just getting a recipe/vertical in order for such
> unit testing, unless we already have one?
Agreed: using tests is essential for lots of reasons, not least to
define expected functionality, as well as helping with cross-browser
issues.
AIUI Phil, Martin have all been using qunit to various degrees, which
supports async calls:
http://docs.jquery.com/QUnit
There's code in the Branch jcore directory which probably needs work
to put into the Trunk:
http://svn.tiddlywiki.org/Branches/jcore/qunit/
I've been experimenting and plan to switch to qunit for my plugin
development, though much of my recent work has been, um, quick and
visual, and not ideal candidates for TDD.
Paul (psd)
--
http://blog.whatfettle.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
