Hmm. The test would fail on Mac OS X or Linux because the separatorChar there is '/' and it wouldn't split correctly on '\'.

My point is, the larger the test coverage is on all platforms, the less likely we are to see a regression in any particular platform specific section. For that matter, the less platform specific sections of code we have, the better.

I would prefer being able to also run this test on Mac OS X or Linux and have it correctly test the \ splitting behavior. That means moving the selection of File.separatorChar inside getHumanishName() over to our SystemReader class, and using the MockSystemReader to set it to '\' specifically in this test function. That is perhaps too ugly for something this simple.