ant test runs the tests.
CustomScriptTest fails.
Eyeballing the test output (courtesy of some added debugging statements) shows the output is about 650 characters as opposed to the expected 700ish. Eyeballing it looks the same so my guess is the equals failure is due to character sets and/or line endings.
I'm on Windows and I know when I was debugging the TCRS file fetch, sometimes I got byte equivalence but other times I had to ignore white space to get equivalence. I got the feeling that part of the difference was due to the OS of the machine that the data file was on when it was checked in.
In any event, if it works for someone on a non-Windows box then the test (as implemented) is OS specific. I'm not sure this is worth fixing but figured I'd note it.
CustomScriptTest fails.
Eyeballing the test output (courtesy of some added debugging statements) shows the output is about 650 characters as opposed to the expected 700ish. Eyeballing it looks the same so my guess is the equals failure is due to character sets and/or line endings.
I'm on Windows and I know when I was debugging the TCRS file fetch, sometimes I got byte equivalence but other times I had to ignore white space to get equivalence. I got the feeling that part of the difference was due to the OS of the machine that the data file was on when it was checked in.
In any event, if it works for someone on a non-Windows box then the test (as implemented) is OS specific. I'm not sure this is worth fixing but figured I'd note it.