nose's .setUp() and .tearDown() are not supported #377
Labels
type: bug
problem that needs to be addressed
Comments
|
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42): What backward compat issues do you see? If someone defines a setUp/tearDown in a non-unittest-deriving test class i guess she would expect them to run. That being said, i slightly dislike "polluting" the non-unittest test class with redundant setup/teardown methods. It probably would also affect setUpClass, right? however, i consider providing nose compatibility out of the box a possibly trumping goal. What do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported by: Floris Bruynooghe (BitBucket: flub, GitHub: flub)
py.test claims to support nose's class level setup and teardown. However nose will execute the
.setUp()and.tearDown()methods of a class for each test function even when the class is not aunitest.TestCasesubclass. py.test OTOH does not seem to do this.It's probably not so hard to do this but before diving into it I was wondering if this even is something py.test wants to support as it can have backwards incompatibility issues. So maybe the right answer is to simply document the limitation/incompatibility?
The text was updated successfully, but these errors were encountered: