Merging test scripts and output demo

Chad Dombrova chadrik at gmail.com
Fri Jun 11 18:51:17 CDT 2010


having used greg's testing suite on my own additions to bfiles, i can vouch
that it was vast improvement over the standard test suite.  to reiterate a
few points:
1) it's quite simple because it is actually compatible with run-tests.
2) the base Tester class provides a base library of helper methods for doing
common testing operations.  this alone is a big time saver and will continue
to improve over time.
3) if you need something more specific you can create a Tester subclass
where you put all of your own helper methods.
4) i don't have you tell you how much more convenient it is to write these
assertions in pure python, without needing to dump each of them into a
separate python executable
5) the ability to assert stdout and stderr results within the test code is
also a huge usability win, and so far i don't believe any of the other
suggested test suites distinguish between these when checking output.
6) lastly, i think that greg has done a good job of keeping the tests fairly
shell-like by avoiding a design like the unittest framework.

-chad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100611/0301cf62/attachment.htm>


More information about the Mercurial-devel mailing list