Replacing strictEqual-assertion with a more useful QUnit.push that includes the expec...
authorKrinkle <krinkle@users.mediawiki.org>
Mon, 13 Jun 2011 00:47:15 +0000 (00:47 +0000)
committerKrinkle <krinkle@users.mediawiki.org>
Mon, 13 Jun 2011 00:47:15 +0000 (00:47 +0000)
commit73231301ae3192c6a32ee927e242b0be9b3d5fae
tree9debf1564cad44c21828bd2fc0ad41588288cf01
parentfc91fde5f19bd3bdf5becfe529829ff073559ccf
Replacing strictEqual-assertion with a more useful QUnit.push that includes the expected and actual values in the html output. This way debugging problems from the TestSwarm will be easier.

This way we end up with:
"Expected: > 100, Result: 99"
instead of:
"Expected: true, Result: false"
which could virtually mean anything (even null, undefined, string, array, you name it)

* Also fixed issue in jquery.colorUtil.js
tests/qunit/suites/resources/jquery/jquery.autoEllipsis.js
tests/qunit/suites/resources/jquery/jquery.colorUtil.js
tests/qunit/suites/resources/mediawiki/mediawiki.js