qunit/testrunner: Log relevant node in unfinished animations and reset
authorTimo Tijhof <krinklemail@gmail.com>
Thu, 20 Nov 2014 17:54:05 +0000 (17:54 +0000)
committerKrinkle <krinklemail@gmail.com>
Wed, 26 Nov 2014 06:27:11 +0000 (06:27 +0000)
commit0615b0f2b91c0985313023d6183b56a7317147df
tree53f2bb0b2ebfae70009616e848217461eb05c13b
parent8228859ad3dd864ddf7b3b1165c40221a37d305d
qunit/testrunner: Log relevant node in unfinished animations and reset

Having unfinished animations affect other test can be a problem,
but when it does happen, having just a number isn't helpful in
trying to pinpoint the cause.

Logging a description of the element should make this relatively
straight forward.

Also reset the animations after the test so that the next test has a
clean start (instead of the current situation where every subsequent
test, until the animation finishes, also reports it as a failure).

Example:

 Unfinished animation #0 in fx queue on <div class="mw-notification
  mw-notification-tag-legacy" style="opacity: 0; "/>

Change-Id: I41058c4cba3383e3ad1456990ccf8dae4ca64951
tests/qunit/data/testrunner.js