[pytest-dev] Introspecting fixtures from within a test

Hi there, I have a small question about fixtures. Basically inside a test function I would like to know which fixtures are active/avaialable and I want to be able to reference them and get their return values. @pytest.fixture def inner(): return 1 @pytest.fixture def foo(inner):

Re: [pytest-dev] Introspecting fixtures from within a test

Hi Christoph, you can retrieve the used fixtures from the test node and use named function right after. See https://gist.github.com/hackebrot/848ab671583540fe18d1 Hope this helps! Raphael > On 16 Jan 2016, at 13:43, Christoph Buelter w

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

The crucial part that is missing wrt to devpi/tox/pytest is the ability to automatically schedule tests to hosts. Rackspace provides us some funding for open source which we can use to have a Windows and a Linux host for running tests. A Windows machine already exists, 4 cores, 8 gigs ram. We

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

Hi Holger, On Sat, Jan 16, 2016 at 6:01 PM Holger Krekel wrote: > The crucial part that is missing wrt to devpi/tox/pytest is the ability to > automatically schedule tests to hosts. Rackspace provides us some funding > for open source which we can use to have a Windows and a Linux host for > run

Re: [pytest-dev] Testing pytest releases using devpi and CI servers

Haven't played yet with your integration code. So I can't contrast it. It was indeed a more general comment regarding what I perceive as the missing piece in open source testing infrastructure. It's true that I kind of am uncomfortable with using commercial hosting services like appveyor an