[Chandler-dev] Unit and Functional Tests updated to handle Unicode character display

[Philippe Bossut]

Heikki Toivonen wrote:
> That sucks for a developer. Instead of running the test once, you need
> to run it n number of times to get y percentage confidence that your
> code is working. You check in, and you might get a failure immediately,
> an hour later, or a day later or, ...
>   
Agree 100%. Also remember that we ping the devs who committed code 
between a green build and a failure. If we start having random failures, 
people will start to be complacent again and failures won't be fixed in 
a timely fashion.
> The problem with TestCrypto was not determinism, the problem was that it
> used only one code point with value that fit into "extended ASCII".
>
> My suggestion is to select two (or if that is too few, a couple more)
> representative code points and put them always in the string. So
> something like:
>
> u = u"%s%s%s"% (u'\u00C5', defaultText, u'\u8ad6')
>   
+1

- Philippe