I see that setuptools has an interface for launching the tests via 'setup.py
test': http://peak.telecommunity.com/DevCenter/setuptools#test-loader
I see that the tests work with nose and unittest. Does py.test provide the
necessary interfaces to launch py.test via setuptools?
I've confirmed my
I was espousing the joys of py.test at a recent #DCPython meetup. I found,
however, that I'm not the only person frustrated by the lack of
documentation on the basic process py.test uses to discover, setup, and
conduct tests.
There's mention here and there of setup/teardown methods, and their
:29
To: Jason R. Coombs
Cc: py-dev@codespeak.net
Subject: Re: [py-dev] feedback on py.test discovery/setup/process
documentation
Hi Jason,
thanks for the feedback, i appreciate it. I am aware that documentation
needs some love - i actually plan to port it to sphinx (which has builtin
--- you can reply above this line ---
New issue 178: stdout and stderr double-encoded in junitxml
https://bitbucket.org/hpk42/pytest/issue/178/stdout-and-stderr-double-encoded-in
Jason R. Coombs:
I'm finding that the junit XML generated by pytest 2.2.4 gets double-encoded
output. For example
--- you can reply above this line ---
New issue 197: Failing to parameterize leaves metafunc unparameterized,
resulting in error
https://bitbucket.org/hpk42/pytest/issue/197/failing-to-parameterize-leaves-metafunc
Jason R. Coombs:
We have a test where we often want to run it against a varying
--- you can reply above this line ---
New issue 198: localized conftest not run
https://bitbucket.org/hpk42/pytest/issue/198/localized-conftest-not-run
Jason R. Coombs:
In the [[https://bitbucket.org/yougov/pmxbot|pmxbot project]], there is a
pytest test suite, and within that test suite
