Re: Test fixture concepts
Wichert Akkerman <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2011-4-20 21:59, Martijn Faassen wrote: > On 03/29/2011 02:43 PM, Wichert Akkerman wrote: >> On 3/29/11 14:40 , Stephan Richter wrote: >>> >>> Yeah, Marius led me recently to that path too. Write a narrative in text files >>> and use doc strings of functions to do edge cases (or when you don't have time >>> for the narrative). I am getting used to it. I still much prefer the sort of >>> output comparison that doctests/manuel gives me over the assertion language >>> that unittest.TestCase requires. >> >> FWIW unittest2 has much nicer output if you use the new assert methods. > > py.test has very nice output if you use the Python 'assert' statement. > There are no assert methods to remember. That sounds nice. I have used Catch (https://github.com/philsquared/catch) a lot for C++ testing recently which also uses a single assert statement instead of a miriad of assert* functions, and it has been a very pleasant experience. Wichert. -- Wichert Akkerman <[email protected]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )