Closed GoogleCodeExporter closed 8 years ago
This is a problem with unittest itself and it's tricky to work around it in
Nose (although we are still considering it). In the meantime you can use this:
https://github.com/kumar303/disable-docstring
Original comment by kumar.mcmillan
on 31 Jul 2011 at 6:27
How can it be a problem with unittest? As far as I know, I'm not even using
it. Am I missing something?
Original comment by dave@boostpro.com
on 31 Jul 2011 at 7:12
Note also: I'm perfectly capable of leaving out the docstrings myself and using
Python comments instead... but I really like the descriptive output I get from
the docstrings. I was just hoping to get some help from Nose in generating
additional context for that output.
Original comment by dave@boostpro.com
on 31 Jul 2011 at 7:14
Nose is just an extension of unittest.
If you want to customize the output you can do so in a plugin by implementing
describeTest() as the plugin does that I linked to.
Original comment by kumar.mcmillan
on 1 Aug 2011 at 1:21
Original issue reported on code.google.com by
dave@boostpro.com
on 31 Jul 2011 at 1:30