Hello

When a test starts a timeout with setTimeout but this isn't execute before the test is finished this

timeout can affect the next test. Such problems are hard to debug.

Does QUnit supports in some finding such problems?

I implemented an ad-hoc solution but IMHO this should be part of the QUnit framework the same

way as checking for namespace pollution is.

    Raimar