Consider some code that you call before or after a test, and you have
to duplicate that in more than one test, maybe dozens. Instead of
extracting a function a calling that each time, just specify setup or
teardown once for the module.

Jörn

On Sun, Sep 21, 2008 at 7:59 PM, Ariel Flesler <[EMAIL PROTECTED]> wrote:
>
> Good news. I don't quite understand what are they for (setup &
> teardown).
> What's a real world application ? the demos on the docs are not too
> realistic.
>
> --
> Ariel Flesler
> http://flesler.blogspot.com/
>
> On Sep 21, 1:56 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>> I've landed a few updates to QUnit: To start with, there is now a
>> testsuite to test QUnit:http://dev.jquery.com/view/trunk/qunit-test
>> (requires a checkout, due to svn:externals)
>>
>> Tests so far cover only the newly module-based setup/teardown
>> callbacks. These allow you to define code that runs before and after
>> each test in a module. More:http://docs.jquery.com/QUnit/module
>>
>> Other changes affect the global variables exposed by QUnit: Instead of
>> making everything global, only the public API is exposed, everything
>> else is private. That public API still includes names like q() and
>> t(), but that is another story.
>>
>> I've tested against jQuery core and the validation plugin, both run
>> fine, and jQuery UI all, which had 69 failing tests already, while not
>> being affected by the changes, as far as I can tell.
>>
>> I'm planning to clean up some of the legacy stuf, like the mentioned
>> q() and t() functions, and once that is done, to start versioning
>> QUnit, including a latest tag.
>>
>> Jörn
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jQuery Development" 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/jquery-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to