appears to be using the QUnit stop and start methods in an obsolete way.
Specifically, the stop method is called with a very large number that appears to be a timeout value. The documentation on the QUnit site says:
The optional argument allows you to compress multiple stop() calls into one, e.g. stop(2) has the same effect as stop(); stop().
Note: This used to be the timeout argument, which was never recommended for use in non-debugging code. If you need a global timeout, set QUnit.config.testTimeout instead.
should be made in the setup procedures to indicate which version of the QUnit package should be used.