StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20319787
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-02T02:10:33.037
FavoriteCount
0
LastActivityDate
2013-12-21T18:23:11.163
LastEditDate
2013-12-21T18:23:11.163
LastEditorUserId
1771
OwnerUserId
1771
ParentId
14244463
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You just need to use TextTestRunner buffer option: <pre><code>import unittest2 class DemoTest(unittest2.TestCase): def test_one(self): print "'grimelsome' attribute of 'smoxy' was set to 'blimpy'" self.assertTrue(True) def test_two(self): print "'smithereen' attribute of 'brouhaha' was set to 'False'" self.assertTrue(False) if __name__ == '__main__': suite = unittest2.TestLoader().loadTestsFromTestCase(DemoTest) result = unittest2.TextTestRunner(verbosity=2, buffer=True).run(suite) </code></pre> Before each test, <code>TextTestResult</code>, used by the runner, will replace <code>sys.stderr</code> and <code>sys.stdout</code> with its own streams and only send the content to the original streams if the test fails or discards it otherwise. Note that because the fake <code>sys.std*</code> streams changes after each test, if you wanted to to do the same thing with logging output, you would have to add the logging handler after the sys.sdt* stream have been replaced, before each test or implement your own handler. Here's an example subclassing <code>logging.StreamHandler</code>: <pre><code>import logging import sys import unittest2 class DemoTest(unittest2.TestCase): logger = logging.getLogger('DemoTest') def setUp(self): self.logger.debug("setting up stuff and logging it...") def teardown(self): self.logger.debug("You won't see me") print "me neither" def test_one(self): self.logger.debug("'grimelsome' attribute of 'smoxy' was set to 'blimpy'") self.assertTrue(True) def test_two(self): self.logger.debug("'smithereen' attribute of 'brouhaha' was set to 'False'") self.assertTrue(False) class TestHandler(logging.StreamHandler): def __init__(self): logging.Handler.__init__(self) @property def stream(self): """Use which ever stream sys.stderr is referencing.""" return sys.stderr if __name__ == '__main__': formatter = logging.Formatter('%(name)s - %(levelname)s - %(message)s') logger_handler = TestHandler() logger_handler.setFormatter(formatter) logger = logging.getLogger() logger.setLevel(logging.DEBUG) logger.addHandler(logger_handler) suite = unittest2.TestLoader().loadTestsFromTestCase(DemoTest) result = unittest2.TextTestRunner( verbosity=2, buffer=True, resultclass=TestResult ).run(suite) </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPython unittest - how can I add debugging information to a TestResult object?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDinoboff
UserOwnerUserId
1. USDinoboff
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.