[TIP] pytest fixture autouse question

[Pella,Chris]

> -----Original Message-----
> From: holger krekel [mailto:holger at merlinux.eu]
> Sent: January-10-13 6:12 AM
> To: Pella,Chris
> Cc: holger krekel; testing-in-python at lists.idyll.org
> Subject: Re: [TIP] pytest fixture autouse question
> 
> On Wed, Jan 09, 2013 at 17:29 -0500, Pella,Chris wrote:
> > > -----Original Message-----
> > > From: holger krekel [mailto:holger at merlinux.eu]
> > > Sent: January-04-13 4:57 AM
> > > To: Pella,Chris
> > > Cc: testing-in-python at lists.idyll.org
> > > Subject: Re: [TIP] pytest fixture autouse question
> > >
> > > Hey Chris,
> > >
> > > On Thu, Jan 03, 2013 at 14:20 -0500, Pella,Chris wrote:
> > > > I may have a misunderstanding of when session-level autouse
> > > > fixtures are
> > > called. I am trying to create a session level fixture that runs
> > > before once per test session before any class setup is called.
> > >
> > > It's a known issue of mixing xUnit and pytest style fixtures. See
> > > here for a discussion and the planned resolution:
> > >
> > >
> > > http://mail.python.org/pipermail/pytest-dev/2012-
> December/002172.htm
> > > l
> > >
> > > For now, you can work around the issue like this::
> > >
> > >     class TestX:
> > >         @pytest.fixture(scope="class", autouse=True)
> > >         def setup_on_class(self):
> > >             ...
> > >
> > I now see a problem with this workaround ... e.g. If I run the following code
> it will throw an exception because cls.skip_me is no longer accessible.
> >
> > class TestThis():
> >     @pytest.fixture(scope="class", autouse=True)
> >     def setup_class(cls):
> >         #cls.skip_me = True
> >         cls.skip_me = False
> >
> >     def test_one(cls):
> >         if cls.skip_me == True:
> >             pytest.skip("can't test this")
> >         assert 1
> >
> >     def test_two(cls):
> >         if cls.skip_me == True:
> >             pytest.skip("can't test this")
> >         assert 1
> >
> >     def teardown_class(cls):
> >         pass
> 
> sorry, my bad.  I forgot to write down @classmethod:
> 
>      @classmethod
>      @pytest.fixture(scope="class", autouse=True)
>      def setup_class(cls):
>          #cls.skip_me = True
>          ...
> 
> This will make the above example work.  note though, that the test methods
> should better "self", not "cls".  All class attributes (including
> "TestThis.skip_me") will be visible on the "self" instance seen by the test
> methods.
> 
> best,
> holger
> 
> 
I noticed one thing with this.  Some of our tests have the teardown_class method right after the setup_class method in the test file. Using the two decorators with the teardown_class  changes the order that the teardown method is called. Normally teardown is executed last, but as soon as you add the fixture decorator it executes in file order.  Not sure if that is intentional or not.

       @classmethod
       @pytest.fixture(scope="class", autouse=True)
       def  teardown_class(self):
          #cls.skip_me = True
 
> you need to use
> >
> > > This will execute after th "session" scoped installer that you describe
> below.
> > >
> > > cheers,
> > > holger
> > >
> > > > I have conftest.py file in the directory where the tests reside
> > > > and in there I
> > > have some code that installs some client software on the test node.
> > > We only want to install the client once per session for all the test
> > > classes that get executed.
> > > >
> > > > @pytest.fixture(scope="session",autouse=True)
> > > > def installer_fixture(request):
> > > >     """
> > > >     Installs client at the session level
> > > >     """
> > > >     print "installing"
> > > >     client = InstallClient()
> > > >     client.install()
> > > >     time.sleep(60)
> > > >
> > > >     def uninstall():
> > > >         """
> > > >         Uninstall client
> > > >         """
> > > >         client.uninstall()
> > > >
> > > >     request.addfinalizer(uninstall)
> > > >
> > > >
> > > > I assumed that this would execute prior to any test setup for a
> > > > particular
> > > test class since it is a session level fixture, but I find that
> > > setup_class() executes before the clients get installed.
> > > >
> > > > e.g. with some toy test code I find  that the class setup gets
> > > > executed
> > > before the fixture.  This is not the behaviour I wanted or expected.
> > > >
> > > > import pytest
> > > >
> > > >
> > > > class TestMe:
> > > >
> > > >     def setup_class(cls):
> > > >         pytest.set_trace()
> > > >         print "setup"
> > > >
> > > >     def test_one(cls):
> > > >         print "test one"
> > > >
> > > >     def teardown_class(cls):
> > > >         print "teardown"
> > > >
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > chris
> > > >
> > > > The information contained in this electronic mail transmission may
> > > > be privileged and confidential, and therefore, protected from
> disclosure.
> > > > If you have received this communication in error, please notify us
> > > > immediately by replying to this message and deleting it from your
> > > > computer without copying or disclosing it.
> > > >
> > > >
> > > > _______________________________________________
> > > > testing-in-python mailing list
> > > > testing-in-python at lists.idyll.org
> > > > http://lists.idyll.org/listinfo/testing-in-python
> >
> > The information contained in this electronic mail transmission may be
> > privileged and confidential, and therefore, protected from disclosure.
> > If you have received this communication in error, please notify us
> > immediately by replying to this message and deleting it from your
> > computer without copying or disclosing it.
> >
> >
> >
The information contained in this electronic mail transmission 
may be privileged and confidential, and therefore, protected 
from disclosure. If you have received this communication in 
error, please notify us immediately by replying to this 
message and deleting it from your computer without copying 
or disclosing it.