In a quick glance, all of the whitespace test file are invalid tests that don't prove anything

There is a major problem with the whitespace test files (all of them).  The
problem is that you can't tell from the results (or even the original data)
what the inputs were and what the outputs should be.  For all whitespace
testing, we should be using the &###; format instead of trying to insert a
space, tab or whatever.  Plus, the line right below it, should indicate with
a color block what the width of the final whitespace is supposed to be.

If I have a test that says :
X     X

"The results are two Xs", how is an end tester going to see the difference
between:

X    X

And 

X X

Plus, how do I know if the character there is a single white space, a double
white space, a zero white space, or a control character?

Melissa Newman

Received on Tuesday, 2 March 2010 13:39:23 UTC