[TIP] setUp and tearDown behavior
redforks at gmail.com
Mon Jan 18 19:29:51 PST 2010
On Tue, Jan 19, 2010 at 11:14 AM, Alfredo Deza <arufuredosan at gmail.com>wrote:
> Can you try an give me some examples? I think I am not following you
> On Mon, Jan 18, 2010 at 10:05 PM, Red Forks <redforks at gmail.com> wrote:
>> On Tue, Jan 19, 2010 at 10:37 AM, Alfredo Deza <arufuredosan at gmail.com>wrote:
>>> I am building some tests for a Python installer that copies some files
>>> and changes some permissions.
>>> Nothing weird there.
>>> However, in the test class I am starting with a setUp that basically
>>> calls the installer (so the tests can see if everything is where it should
>>> be), this is followed by a few assertions and finally a tearDown is called
>>> where everything gets uninstalled.
>>> When running the tests with nosetests, I see that setUp and tearDown are
>>> called for *every* method in my test class (e.g. installs => runs test
>>> method => uninstalls ....)
>>> Isn't setUp supposed to be run once at the beginning of the class? or is
>>> this expected?
>>> In case this is expected, is there a way to do it *just once *for all
>>> the methods?
>>> testing-in-python mailing list
>>> testing-in-python at lists.idyll.org
>> Maybe you need module level setup / teapDown func.
Method 1: using module level setup / teardown:
# setup codes here
# teardown codes here
Method 2: class level setup / teardown
# setup codes
# teardown codes
Note: All this is nosetest extension, i.e. can only run under nosetest.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python