[TIP] Make py.test output more like nose?
randy at thesyrings.us
Tue Jul 22 12:33:26 PDT 2014
I have some problems running nose on Windows. I've filed a bug report,
but it's been a long time and no movement. I don't have time to
troubleshoot why it's not working, so py.test seems like another option.
Some projects are specific to one test runner or another due to custom
setup/hooks/plugins needed. I figured it would be good to learn both of
Also, I did figure it out eventually. --tb=native is what I want. I
then set that in a configuration file in my home directory:
Husband | Father | Redeemed Sinner
/"For what does it profit a man to gain the whole world
and forfeit his soul?" (Mark 8:36 ESV)/
On 07/22/2014 01:42 PM, Marcin Tustin wrote:
> This isn’t meant to be snide: if you want nose-style output, why not
> use nose? What’s the draw of py.test?
> *From:*testing-in-python-bounces at lists.idyll.org
> [mailto:testing-in-python-bounces at lists.idyll.org] *On Behalf Of
> *Randy Syring
> *Sent:* Tuesday, July 22, 2014 1:31 PM
> *To:* testing-in-python at lists.idyll.org
> *Subject:* [TIP] Make py.test output more like nose?
> I've been trying various combinations of command line settings for
> py.test to get the output to be more like nose when exceptions are
> encountered. Currently, py.test is showing me several frames of
> information and the source code related to the traceback. But all I
> want is what nose gives me 1) a dot for pass and 2) a normal python
> traceback for failure.
> *Randy Syring*
> Husband | Father | Redeemed Sinner
> /"For what does it profit a man to gain the whole world
> and forfeit his soul?" (Mark 8:36 ESV)/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python