Re: [Pyunit-interest] comments on PyUnit

[Steve P. <ste...@ya...>]

Steve wrote:
> > I think this can be safely done in time for this week's 2.1 release
> > (though that's not *my* call to make).

Guido replied:
> The code freeze is planned to start Thursday (probably Thu afternoon),
> so you have approximately a day!


I have now checked the changes into both the Python and PyUnit CVS trees.

The complete set of fail*() methods, together with their 'assert*' synonyms,
is now:

   fail()
   failIf()
   failUnless()           --   assert_()
   failIfEqual()          --   assertNotEqual(), assertNotEquals()
   failUnlessEqual()      --   assertEqual(), assertEquals()

There is a new attribute 'failureException' in the TestCase class; this
attribute parameterises the exception that indicates test failures, and
is set to 'AssertionError' by default. Subclasses may override it if they
wish:

    class TestFailed(Exception): pass

    class StandardTestCase(unittest.TestCase):
       failureException = TestFailed

or even:

    class StandardTestCase(unittest.TestCase):
       class failureException(Exception): pass

I will make a new PyUnit release at the weekend that will correspond to the
'unittest.py' included in the Python 2.1 final release.

Best wishes,

-Steve

-- 
Steve Purcell, Pythangelist
Get testing at http://pyunit.sourceforge.net/
Any opinions expressed herein are my own and not necessarily those of Yahoo