[devtools] qunit: use new async testing APIs
http://qunitjs.com/cookbook/#asynchronous-callbacks
QUnit keeps track of all the assert.async() objects created inside the
test functions and expects all done() functions to be called. Failure to
do so will result in the test being failed.
Unlike .start and .stop which were internal APIs, assert.async() is
stricter and fails tests if assert methods are used *after* all done()
functions are called (see "test callback execution order").
Related to #5533333.
<html>
<head>
<!-- dependencies -->
<script type="text/javascript" src="utils.js"></script>
<script type="text/javascript" src="../../data/jquery.js"></script>
<script src="../../data/cubicweb.python.js" type="text/javascript"></script>
<script src="../../data/cubicweb.js" type="text/javascript"></script>
<script src="../../data/cubicweb.compat.js" type="text/javascript"></script>
<!-- qunit files -->
<script type="text/javascript" src="../../../devtools/data/qunit.js"></script>
<link rel="stylesheet" type="text/css" media="all" href="../../../devtools/data/qunit.css" />
<!-- test suite -->
<script src="cwmock.js" type="text/javascript"></script>
<script src="test_utils.js" type="text/javascript"></script>
</head>
<body>
<div id="main"> </div>
<h1 id="qunit-header">cw.utils functions tests</h1>
<h2 id="qunit-banner"></h2>
<ol id="qunit-tests">
</body>
</html>