Features I miss from py.test

[Leah Klearman]

Jason asked a while back what features I like in py.test that nose doesn't have. 

Right now I'm being driven nuts by the fact that when you cancel a test run, it doesn't output any of the data from the tests that have run so far. It happens quite frequently that I change something that breaks all of my tests, and I can determine that something like this went wrong when I see 3 errors in a row, but I need the stack trace to debug it, and I don't want to wait for the whole suite to finish running in order to get that info.

I also miss layered conftest.py files provided along with the test code (each test directory could specify how it used the test runner differently). It might be possible to do it using the instructions at https://nose.readthedocs.org/en/latest/plugins/writing.html#registering-a-plugin-without-setuptools, but that requires a custom runner as well. 

Thanks,

-Leah