JP
JP
I tried it today but the problem is still there and was not fixed by Issue 399. As far as I understand it after trying a few things each test...
Ok, I see now why you need to add things in the multiprocess plugin, I thought the multiprocessing module worked differently. Google Code Info: Author: [email protected] Created On: 2011-11-22T14:40:12.000Z
https://github.com/nose-devs/nose/commit/ec9eb1d2ffb2ea897fac5b80c9d941b3845cc6a0#diff-3 appears to be the revision that introduced this change.
Sounds good to me. Though as someone who has been burned by many a bad migration, I have to suggest running them with your tests, at least in continuous integration....
Similar to the feature in nose or in sphinx's doctest support -- actually now that I think of it we should try to be fully compatible with sphinx so that...
Not as sure about this after working on mp. Putting on hold.
This is a good idea, and would help with implementing the `--failed` switch.
The --failed switch is one thing the testids plugin supports in nose but not nose2 -- a mode to rerun just the tests that failed in the last test run...
Good idea. Labels applied.
I'm not sure what you tried here -- using a TestCase subclass as a layer? That won't work, by design -- layers aren't test cases, they are just a way...