On Nov 12, 7:18 am, "Edward K. Ream" <[email protected]> wrote:
> We are now "officially", that is, by my fiat, in a new testing regime. Rev 4783 completes the present round of html work by adding 3 new unit tests for badly-formed html. Earlier revs today add several important improvements for external unit testing. 1. Replaced g.es_exception with g.es_print_exception. Very important when running unit tests externally. 2. scannerUnitTest now prints all "failure" information as part of the failing assert that triggers the unit-test failure. This is a great new pattern: the failure information is now associated with the rest of the unit test information, and is much more clearly formatted than before. 3. As the result of Point 2, it became obvious why Python unit tests were failing externally: there was no @tabwidth in effect so (for reasons unclear, and not important) the test contained intermixed blanks and tabs. As a result, the test was failing before the "meat" was being run. The fix was simply to put @tabwidth -4 in all python- related import tests. All in all, a good day for unit tests, especially externally-run unit tests. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
