Some tests may become successful when you set
Thread.CurrentThread.CurrentCulture to en-US. Some won't, unless
you set current langauge and/or region (you should not do that
programmatically even if possible, anyways).
Anyways it may solve only one aspect of the problems I stated earlier.
Atsushi
Atsushi Eno wrote:
> Hey guys,
>
> I have seen a lot of bad NUnit tests that unnecessarily compare
> exception messages. They are wrong not only because they fail
> in non-English Windows environment but also because those tests
> will fail when Microsoft improves the messages. Furthermore, it
> b
Hey guys,
I have seen a lot of bad NUnit tests that unnecessarily compare
exception messages. They are wrong not only because they fail
in non-English Windows environment but also because those tests
will fail when Microsoft improves the messages. Furthermore, it
blocks possible message translatio
