Hi all,
Currently, if you define e.g. an autouse fixture function it is going to
be called _after_ the xUnit setup functions. This is especially
surprising when you do a session-scoped autouse fixture. I am wondering
if we could reverse the order, i.e. call fixture functions (including
On Sun, Dec 16, 2012 at 13:21 +0100, Ronny Pfannschmidt wrote:
sounds like the correct curse of action else legacy tests cant be
integrated with fixtures propperly
curse of action ... like that one :)
i wonder if we should go as far as allowing fixtures to be arguments
to pytest xunit test
I think it's best to think of the xunit-style setup and teardown as part of
the actual test - as in, if you're blindly translating this:
class SomethingTest(TestCase):
def setUp(self):
self.doop = 1
def tearDown(self):
del self.doop
def
On Sun, Dec 16, 2012 at 13:49 -0700, lahwran wrote:
I think it's best to think of the xunit-style setup and teardown as part of
the actual test - as in, if you're blindly translating this:
class SomethingTest(TestCase):
def setUp(self):
self.doop = 1
def
Hi, I've got a bit of a problem related to how pytest determines the fully
qualified name for a module. I have a django 1.3 layout project which has
an __init__.py at its root, due to oddities in how django functions. so I
have something like this layout:
~/project_venv/ # containing the
