module parameter for QUnit.reset() usage

[bennom]

With these changes it's possible to define a (boolean) parameter for module() - resetFixture:

If set to true: QUnit.reset() will be skipped for the module.
If not set / set to false: QUnit.reset() will be performed as usual.

[jzaefferer]

What issue are you addressing here? In what case wouldn't you want to address the fixture?

[bennom]

One of the main principles of unit testing is "keep the tests atomic". With this in mind, I'm trying to test my jQuery plugin. 1st test: initialization (with html replacements), 2nd test: some user interactions based on the elements inserted by test #1 (new DOM elements will appear again) and so on. But between each test the DOM elements inserted by the plugin will be reset (but I need them to apply more tests). So I think sometimes it's necessary to keep the content within the fixture :-)

[jzaefferer]

"keep tests atomic", right, that's exactly why this is really wrong. You should put shared init code into module-setup, not sure fixture. Otherwise your second test breaks when you run it standalone, e.g. using the Rerun link.