Test suit

[Samuel Ytterbrink]

Hi all...

While Christian have bean working on the compiler and  i don't want to collide with his work, to much. I have decided to 'fix' the test suit to meat the unittest standard. This have bean hard cause the documentation on the unittest framework is big but not as well written as it's code.

I how ever are closing up on an end to my export and need some feedback on what is important in the old system and what can be left behind.

So far i have two factory functions for test classes, one for the normal and one for the ones expected to fail. Theses are outo discoverd with the frameworks own functions. This actually found tests which wasn't 'turned on' in the old suit. The output in text format is identical( except that the -a flag is always on).

What is missing:

  colors, they have never worked on my system.

  dots, the dots now comes all at once. 4 for a full test.

pros:

  by using the unittest framework we split the testcode and the output( result code). This makes the suit easyer to use with other programs that needs another result format. Also i think this have potential to be faster for speedy testing( when you just want to know that you didden't break anything), it can handel diferent verbosity levels.

the code is at: https://github.com/Neppord/py2js/blob/tester/test.py
--
//Samuel Ytterbrink