I discovered that one mistake I had made was I assumed that I could always retrieve the characters of a 'Dao.Token.Token' using 'Dao.Token.asUStr'. I had completely forgotten that you cannot do this for keyword an operator tokens because they do not store the parsed characters with the token in order to save memory. I have written proper comments on the 'Dao.Token.asUStr' family of function to remind everyone of this.
Fixed a few more bugs over lunch break. The new testing program is working very well.
Fixed a bug in the display function, and added a 'Dao.Test.showTestMode' function which can be triggered with the command line argument "-t". I also had to add the callback function 'Dao.Test.showTest' to the 'Dao.Test.UnitTester' data type. 'Dao.Test.showTestMode' will take parameters from the command line, or read line-by-line standard input if the command line parameter is "-", and generate a random test using the integer value of that command line or input line parameter. The test is not evaluated, it is only generated and printed to the STDOUT stream. You can then pass some random numbers on the command line or on the STDIN stream to check the quality of the random tests generated.
Fixed a whole bunch of bugs that were exposed (or caused by) the unit tester. Right now I am able to run the tests up to the point where a stack overflow occurs somewhere around the 883250th test case.  I noticed that the quality of the random tests may perhaps not be that great. I may need to make the random test case generator more random by relying more heavily on the pseudo-random number generator.