Antoine Pitrou <[EMAIL PROTECTED]> writes:
> For what it's worth, I've been using nose for quite a long time and
> the first reason I did so is, like you, because I wanted to write
> tests in a light way (without having to declare classes).
>
> Then after writing some dozens of tests I switched b
Antoine Pitrou wrote:
(especially when you come to have setup/teardown functions shared by several
tests).
These days, I tend to just write a context manager for common
setup/teardown code rather than using the setUp/tearDown hooks (at least
for Python's own test suite, where I have the luxur
Steven D'Aprano pearwood.info> writes:
>
> I am interested in this suggestion. I didn't know about py.test.
>
> I admit to dissatisfaction with unittest (too Java-ish and heavyweight
> for my tastes). I would love a test suite midway in weight between
> doctests and unittest, so I will check i
