[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.

     1

change_attribute_type('CWCache', 'timestamp', 'TZDatetime')

     2

change_attribute_type('CWUser', 'last_login_time', 'TZDatetime')

     3

change_attribute_type('CWSource', 'latest_retrieval', 'TZDatetime')

     4

drop_attribute('CWSource', 'synchronizing')

     5

add_attribute('CWSource', 'in_synchronization')