QUnit: "polluted" config.fixture -> window.load versus domready

QUnit: "polluted" config.fixture -> window.load versus domready

Hi,

I'm testing several modules, wich need to use QUnit.reset. Some of the modules are modifying the DOM on domready. My Problem is, that the config.fixture is set on window.onload and therefore saves the wrong HTML-Structure. Currently, I'm delaying the tests DOM-Manipulation, if I detect a window.Qunit is there a better workaround/solution for this problem?

regards
alex





    • Topic Participants

    • info