jsTestDriver does not handle certain unicode characters in tests

[thecapdan]

Trying to test a string that contains Japanese characters. (in most cases, we would use the i18n fixture to test translation tokens, but there may be some valid use cases where we need to test strings that contain these characters)

To reproduce, run the following UT

(function(){
'use strict';
var testCase = {
    setUp : function() {    },
    tearDown : function() { },
    "test JSTs ability to handle unicode" : function()
    { assertEquals('\u30ab', 'カ') }
    ,
    };
TestCase('UnicodeTest', testCase);
}());

Result:

UnicodeTest.test JSTs ability to handle unicode failed (3.00 ms): AssertError: expected "?" but was "?"
      AssertError: expected "?" but was "?"

See discussion at http://code.google.com/p/js-test-driver/issues/detail?id=85 and patch at https://code.google.com/p/js-test-driver/source/detail?r=170a4754abc99c3217d349d55592b86a89000efd

@andyberry88 if you are short of QAs(!) give me a shout and I can add a failing test

[andy-berry-dev]

@andyberry88 if you are short of QAs(!) give me a shout and I can add a failing test

That would be lovely 😄

[andy-berry-dev]

I've added some tests in 3fa7f14 to verify this isn't also an issue in our bundle file creator (which it isn't) so the fix for this is just going to require adding the patch that @thecapdan has linked to above.

[andy-berry-dev]

The plan is to move away from JsTestDriver and support pluggable test runners (#8). Given this is a bug with JsTestDriver I don' think this is something we should look at fixing so I'd suggest we close it. // @dchambers @ioanalianabalas

[ioanalianabalas]

Given that support pluggable test runners are scheduled for the next release after 1.0, I also agree that we can close this.

[dchambers]

I think NPM support will make the likelihood of us ever supporting other test frameworks increasingly less likely. And, in any case, even if we did support another test framework, it seems unreasonable that the test framework that the majority of our tests are currently written in isn't Unicode compatible. Finally, given that this there is a patch for fixing this, unless that patch doesn't work for the version of JsTestDriver we use then I'd like us to re-open this issue and instead fix by applying the patch.