Closed bkardell closed 11 years ago
For some reason it would appear that using the grunt copy of qunit is causing problems, using the CDN version, however and setting the basepath appears to resolve issues.
Note however that this yields a fail in node of our 4/142 tests now:
WebIDL Byte - [Clamp] choosing +0 rather than −0. Message: -0.5 rounds to +0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Byte-tests.js:87 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383 WebIDL Byte - If x is NaN, +0, −0, +∞, or −∞, then return the IDL byte value that represents 0. Message: -0, so 0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Byte-tests.js:93 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383 WebIDL Octet - [Clamp] choosing +0 rather than −0. Message: -0.5 rounds to +0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Octet-tests.js:87 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383 WebIDL Octet - If x is NaN, +0, −0, +∞, or −∞, then return the IDL octet value that represents 0. Message: -0, so 0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Octet-tests.js:93 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383
WebIDL Byte - [Clamp] choosing +0 rather than −0. Message: -0.5 rounds to +0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Byte-tests.js:87 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383
WebIDL Byte - If x is NaN, +0, −0, +∞, or −∞, then return the IDL byte value that represents 0. Message: -0, so 0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Byte-tests.js:93 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383
WebIDL Octet - [Clamp] choosing +0 rather than −0. Message: -0.5 rounds to +0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Octet-tests.js:87 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383
WebIDL Octet - If x is NaN, +0, −0, +∞, or −∞, then return the IDL octet value that represents 0. Message: -0, so 0 Actual: true Expected: false at http://code.jquery.com/qunit/qunit-1.10.0.js:488 at http://localhost:8000/test/WebIDL.Octet-tests.js:93 at http://code.jquery.com/qunit/qunit-1.10.0.js:136 at http://code.jquery.com/qunit/qunit-1.10.0.js:279 at process (http://code.jquery.com/qunit/qunit-1.10.0.js:1277) at http://code.jquery.com/qunit/qunit-1.10.0.js:383
Warning: 4/142 assertions failed (213ms) Use --force to continue.
For some reason it would appear that using the grunt copy of qunit is causing problems, using the CDN version, however and setting the basepath appears to resolve issues.
Note however that this yields a fail in node of our 4/142 tests now:
Warning: 4/142 assertions failed (213ms) Use --force to continue.