blocks|key|1691252|text|捕获从断言失败中生成的异常。在catch块中，您可以随心所欲地输出数据。然后，当您完成后，您可以重新抛出异常。测试跑步者可能不会知道其中的区别。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691253|免责声明:我还没有在Python的单元测试框架中尝试过，但我已经在其他单元测试框架中尝试过了。|1691254|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Catch the exception that gets generated from the assertion failure. In your catch block you could output the data however you wanted to wherever. Then when you were done you could rethrow the exception. The test runner probably wouldn't know the difference.
Disclaimer: I haven't tried this with Python's unit test framework, but I have with other unit test frameworks.

blocks|key|1476252|text|为此，我们使用日志记录模块。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476253|例如：|1476254|import+logging
class+SomeTest(+unittest.TestCase+):
++++def+testSomething(+self+):
++++++++log=+logging.getLogger(+"SomeTest.testSomething"+)
++++++++log.debug(+"this=+%25r",+self.this+)
++++++++log.debug(+"that=+%25r",+self.that+)
++++++++#+etc.
++++++++self.assertEquals(+3.14,+pi+)

if+__name__+==+"__main__":
++++logging.basicConfig(+stream=sys.stderr+)
++++logging.getLogger(+"SomeTest.testSomething"+).setLevel(+logging.DEBUG+)
++++unittest.main()|code-block|syntax|javascript|1476255|这允许我们为特定的测试打开调试，我们知道这些测试失败了，并且我们需要额外的调试信息。|1476256|然而，我更喜欢的方法不是花很多时间在调试上，而是花在编写更细粒度的测试来暴露问题上。|1476257|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

We use the logging module for this.

For example:

<pre><code>import logging
class SomeTest( unittest.TestCase ):
 def testSomething( self ):
 log= logging.getLogger( "SomeTest.testSomething" )
 log.debug( "this= %r", self.this )
 log.debug( "that= %r", self.that )
 # etc.
 self.assertEquals( 3.14, pi )

if __name__ == "__main__":
 logging.basicConfig( stream=sys.stderr )
 logging.getLogger( "SomeTest.testSomething" ).setLevel( logging.DEBUG )
 unittest.main()
</code></pre>

That allows us to turn on debugging for specific tests which we know are failing and for which we want additional debugging information.

My preferred method, however, isn't to spend a lot of time on debugging, but spend it writing more fine-grained tests to expose the problem.

blocks|key|1476319|text|我想我可能想得太多了。我想出的一种方法是，简单地使用一个全局变量来累积诊断数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476320|如下所示：|1476321|log1+=+dict()
class+TestBar(unittest.TestCase):
++++def+runTest(self):
++++++++for+t1,+t2+in+testdata:
++++++++++++f+=+Foo(t1)
++++++++++++if+f.bar(t2)+!=+2:
++++++++++++++++log1("TestBar.runTest")+=+(f,+t1,+t2)
++++++++++++++++self.fail("f.bar(t2)+!=+2")|code-block|syntax|javascript|1476322|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I think I might have been overthinking this. One way I've come up with that does the job, is simply to have a global variable that accumulates the diagnostic data.
Something like this:
<pre><code>log1 = dict()
class TestBar(unittest.TestCase):
 def runTest(self):
 for t1, t2 in testdata:
 f = Foo(t1)
 if f.bar(t2) != 2:
 log1(&quot;TestBar.runTest&quot;) = (f, t1, t2)
 self.fail(&quot;f.bar(t2) != 2&quot;)
</code></pre>

blocks|key|1691492|text|另一种选择--在测试失败的地方启动调试器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691493|尝试使用Testoob运行您的测试(它将运行您的单元测试套件而不做任何更改)，当测试失败时，您可以使用'--debug‘命令行开关打开调试器。|1691494|下面是Windows上的终端会话：|1691495|C:\work>+testoob+tests.py+--debug
F
Debugging+for+failure+in+test:+test_foo+(tests.MyTests.test_foo)
>+c:\python25\lib\unittest.py(334)failUnlessEqual()
->+(msg+or+'%25r+!=+%25r'+%25+(first,+second))
(Pdb)+up
>+c:\work\tests.py(6)test_foo()
->+self.assertEqual(x,+y)
(Pdb)+l
++1+++++from+unittest+import+TestCase
++2+++++class+MyTests(TestCase):
++3+++++++def+test_foo(self):
++4+++++++++x+=+1
++5+++++++++y+=+2
++6++->+++++self.assertEqual(x,+y)
[EOF]
(Pdb)|code-block|syntax|javascript|1691496|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Another option - start a debugger where the test fails.
Try running your tests with Testoob (it will run your unit test suite without changes), and you can use the '--debug' command line switch to open a debugger when a test fails.
Here's a terminal session on Windows:
<pre class="lang-none prettyprint-override"><code>C:\work&gt; testoob tests.py --debug
F
Debugging for failure in test: test_foo (tests.MyTests.test_foo)
&gt; c:\python25\lib\unittest.py(334)failUnlessEqual()
-&gt; (msg or '%r != %r' % (first, second))
(Pdb) up
&gt; c:\work\tests.py(6)test_foo()
-&gt; self.assertEqual(x, y)
(Pdb) l
 1 from unittest import TestCase
 2 class MyTests(TestCase):
 3 def test_foo(self):
 4 x = 1
 5 y = 2
 6 -&gt; self.assertEqual(x, y)
[EOF]
(Pdb)
</code></pre>

blocks|key|1476487|text|在Python2.7中，您可以使用额外的参数msg向错误消息中添加信息，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1476488|self.assertEqual(f.bar(t2),+2,+msg='{0},+{1}'.format(t1,+t2))|code-block|syntax|javascript|1476489|官方文档是here。|1476490|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.python.org/2/library/unittest.html#unittest.TestCase.assertEqual^0|M|3|0|0|5|4|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

In Python 2.7 you could use an additional parameter, <code>msg</code>, to add information to the error message like this:
<pre><code>self.assertEqual(f.bar(t2), 2, msg='{0}, {1}'.format(t1, t2))
</code></pre>
The official documentation is <a href="http://docs.python.org/2/library/unittest.html#unittest.TestCase.assertEqual" rel="nofollow noreferrer">here</a>.

blocks|key|1691654|text|inspect.trace将允许您在抛出异常后获取局部变量。然后，可以使用如下所示的装饰器包装单元测试，以保存这些局部变量，以便在事后检查时进行检查。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1691655|import+random
import+unittest
import+inspect


def+store_result(f):
++++"""
++++Store+the+results+of+a+test
++++On+success,+store+the+return+value.
++++On+failure,+store+the+local+variables+where+the+exception+was+thrown.
++++"""
++++def+wrapped(self):
++++++++if+'results'+not+in+self.__dict__:
++++++++++++self.results+=+{}
++++++++#+If+a+test+throws+an+exception,+store+local+variables+in+results:
++++++++try:
++++++++++++result+=+f(self)
++++++++except+Exception+as+e:
++++++++++++self.results[f.__name__]+=+{'success':False,+'locals':inspect.trace()[-1][0].f_locals}
++++++++++++raise+e
++++++++self.results[f.__name__]+=+{'success':True,+'result':result}
++++++++return+result
++++return+wrapped

def+suite_results(suite):
++++"""
++++Get+all+the+results+from+a+test+suite
++++"""
++++ans+=+{}
++++for+test+in+suite:
++++++++if+'results'+in+test.__dict__:
++++++++++++ans.update(test.results)
++++return+ans

#+Example:
class+TestSequenceFunctions(unittest.TestCase):

++++def+setUp(self):
++++++++self.seq+=+range(10)

++++@store_result
++++def+test_shuffle(self):
++++++++#+make+sure+the+shuffled+sequence+does+not+lose+any+elements
++++++++random.shuffle(self.seq)
++++++++self.seq.sort()
++++++++self.assertEqual(self.seq,+range(10))
++++++++#+should+raise+an+exception+for+an+immutable+sequence
++++++++self.assertRaises(TypeError,+random.shuffle,+(1,2,3))
++++++++return+{1:2}

++++@store_result
++++def+test_choice(self):
++++++++element+=+random.choice(self.seq)
++++++++self.assertTrue(element+in+self.seq)
++++++++return+{7:2}

++++@store_result
++++def+test_sample(self):
++++++++x+=+799
++++++++with+self.assertRaises(ValueError):
++++++++++++random.sample(self.seq,+20)
++++++++for+element+in+random.sample(self.seq,+5):
++++++++++++self.assertTrue(element+in+self.seq)
++++++++return+{1:99999}


suite+=+unittest.TestLoader().loadTestsFromTestCase(TestSequenceFunctions)
unittest.TextTestRunner(verbosity=2).run(suite)

from+pprint+import+pprint
pprint(suite_results(suite))|code-block|syntax|javascript|1691656|最后一行将打印测试成功的返回值和失败时的局部变量，在本例中为x：|1691657|{'test_choice':+{'result':+{7:+2},+'success':+True},
+'test_sample':+{'locals':+{'self':+<__main__.TestSequenceFunctions+testMethod=test_sample>,
++++++++++++++++++++++++++++'x':+799},
+++++++++++++++++'success':+False},
+'test_shuffle':+{'result':+{1:+2},+'success':+True}}|1691658|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

inspect.trace will let you get local variables after an exception has been thrown. You can then wrap the unit tests with a decorator like the following one to save off those local variables for examination during the post mortem.
<pre><code>import random
import unittest
import inspect


def store_result(f):
 &quot;&quot;&quot;
 Store the results of a test
 On success, store the return value.
 On failure, store the local variables where the exception was thrown.
 &quot;&quot;&quot;
 def wrapped(self):
 if 'results' not in self.__dict__:
 self.results = {}
 # If a test throws an exception, store local variables in results:
 try:
 result = f(self)
 except Exception as e:
 self.results[f.__name__] = {'success':False, 'locals':inspect.trace()[-1][0].f_locals}
 raise e
 self.results[f.__name__] = {'success':True, 'result':result}
 return result
 return wrapped

def suite_results(suite):
 &quot;&quot;&quot;
 Get all the results from a test suite
 &quot;&quot;&quot;
 ans = {}
 for test in suite:
 if 'results' in test.__dict__:
 ans.update(test.results)
 return ans

# Example:
class TestSequenceFunctions(unittest.TestCase):

 def setUp(self):
 self.seq = range(10)

 @store_result
 def test_shuffle(self):
 # make sure the shuffled sequence does not lose any elements
 random.shuffle(self.seq)
 self.seq.sort()
 self.assertEqual(self.seq, range(10))
 # should raise an exception for an immutable sequence
 self.assertRaises(TypeError, random.shuffle, (1,2,3))
 return {1:2}

 @store_result
 def test_choice(self):
 element = random.choice(self.seq)
 self.assertTrue(element in self.seq)
 return {7:2}

 @store_result
 def test_sample(self):
 x = 799
 with self.assertRaises(ValueError):
 random.sample(self.seq, 20)
 for element in random.sample(self.seq, 5):
 self.assertTrue(element in self.seq)
 return {1:99999}


suite = unittest.TestLoader().loadTestsFromTestCase(TestSequenceFunctions)
unittest.TextTestRunner(verbosity=2).run(suite)

from pprint import pprint
pprint(suite_results(suite))
</code></pre>
The last line will print the returned values where the test succeeded and the local variables, in this case x, when it fails:
<pre><code>{'test_choice': {'result': {7: 2}, 'success': True},
 'test_sample': {'locals': {'self': &lt;__main__.TestSequenceFunctions testMethod=test_sample&gt;,
 'x': 799},
 'success': False},
 'test_shuffle': {'result': {1: 2}, 'success': True}}
</code></pre>

blocks|key|1476595|text|在Facundo+Casco's+answer上扩展，这对我来说工作得很好：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1476596|class+MyTest(unittest.TestCase):
++++def+messenger(self,+message):
++++++++try:
++++++++++++self.assertEqual(1,+2,+msg=message)
++++++++except+AssertionError+as+e:++++++
++++++++++++print+"\nMESSENGER+OUTPUT:+%25s"+%25+str(e),|code-block|syntax|javascript|1476597|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/284043/outputting-data-from-unit-test-in-python/13688397#13688397^0|1|M|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Expanding on <a href="https://stackoverflow.com/questions/284043/outputting-data-from-unit-test-in-python/13688397#13688397">Facundo Casco's answer</a>, this works quite well for me:
<pre><code>class MyTest(unittest.TestCase):
 def messenger(self, message):
 try:
 self.assertEqual(1, 2, msg=message)
 except AssertionError as e: 
 print &quot;\nMESSENGER OUTPUT: %s&quot; % str(e),
</code></pre>

blocks|key|1476614|text|我使用的方法非常简单。我只是把它记录下来作为警告，这样它就会真正显示出来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476615|import+logging

class+TestBar(unittest.TestCase):
++++def+runTest(self):

+++++++#this+line+is+important
+++++++logging.basicConfig()
+++++++log+=+logging.getLogger("LOG")

+++++++for+t1,+t2+in+testdata:
+++++++++f+=+Foo(t1)
+++++++++self.assertEqual(f.bar(t2),+2)
+++++++++log.warning(t1)|code-block|syntax|javascript|1476616|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The method I use is really simple. I just log it as a warning so it will actually show up.


<pre><code>import logging

class TestBar(unittest.TestCase):
 def runTest(self):

 #this line is important
 logging.basicConfig()
 log = logging.getLogger("LOG")

 for t1, t2 in testdata:
 f = Foo(t1)
 self.assertEqual(f.bar(t2), 2)
 log.warning(t1)
</code></pre>

blocks|key|1476695|text|使用日志记录：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1476696|import+unittest
import+logging
import+inspect
import+os

logging_level+=+logging.INFO

try:
++++log_file+=+os.environ["LOG_FILE"]
except+KeyError:
++++log_file+=+None

def+logger(stack=None):
++++if+not+hasattr(logger,+"initialized"):
++++++++logging.basicConfig(filename=log_file,+level=logging_level)
++++++++logger.initialized+=+True
++++if+not+stack:
++++++++stack+=+inspect.stack()
++++name+=+stack[1][3]
++++try:
++++++++name+=+stack[1][0].f_locals["self"].__class__.__name__+%2B+"."+%2B+name
++++except+KeyError:
++++++++pass
++++return+logging.getLogger(name)

def+todo(msg):
++++logger(inspect.stack()).warning("TODO:+{}".format(msg))

def+get_pi():
++++logger().info("sorry,+I+know+only+three+digits")
++++return+3.14

class+Test(unittest.TestCase):

++++def+testName(self):
++++++++todo("use+a+better+get_pi")
++++++++pi+=+get_pi()
++++++++logger().info("pi+=+{}".format(pi))
++++++++todo("check+more+digits+in+pi")
++++++++self.assertAlmostEqual(pi,+3.14)
++++++++logger().debug("end+of+this+test")
++++++++pass|code-block|syntax|javascript|1476697|用法：|1476698|#+LOG_FILE=/tmp/log+python3+-m+unittest+LoggerDemo
.
----------------------------------------------------------------------
Ran+1+test+in+0.047s

OK
#+cat+/tmp/log
WARNING:Test.testName:TODO:+use+a+better+get_pi
INFO:get_pi:sorry,+I+know+only+three+digits
INFO:Test.testName:pi+=+3.14
WARNING:Test.testName:TODO:+check+more+digits+in+pi|1476699|如果不设置LOG_FILE，日志将转到stderr。|offset|length|style|CODE|1476700|entityMap^0|0|0|0|0|5|8|J|6|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]|$M|Z|N|10|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Use logging:

<pre><code>import unittest
import logging
import inspect
import os

logging_level = logging.INFO

try:
 log_file = os.environ["LOG_FILE"]
except KeyError:
 log_file = None

def logger(stack=None):
 if not hasattr(logger, "initialized"):
 logging.basicConfig(filename=log_file, level=logging_level)
 logger.initialized = True
 if not stack:
 stack = inspect.stack()
 name = stack[1][3]
 try:
 name = stack[1][0].f_locals["self"].__class__.__name__ + "." + name
 except KeyError:
 pass
 return logging.getLogger(name)

def todo(msg):
 logger(inspect.stack()).warning("TODO: {}".format(msg))

def get_pi():
 logger().info("sorry, I know only three digits")
 return 3.14

class Test(unittest.TestCase):

 def testName(self):
 todo("use a better get_pi")
 pi = get_pi()
 logger().info("pi = {}".format(pi))
 todo("check more digits in pi")
 self.assertAlmostEqual(pi, 3.14)
 logger().debug("end of this test")
 pass
</code></pre>

Usage:

<pre><code># LOG_FILE=/tmp/log python3 -m unittest LoggerDemo
.
----------------------------------------------------------------------
Ran 1 test in 0.047s

OK
# cat /tmp/log
WARNING:Test.testName:TODO: use a better get_pi
INFO:get_pi:sorry, I know only three digits
INFO:Test.testName:pi = 3.14
WARNING:Test.testName:TODO: check more digits in pi
</code></pre>

If you do not set <code>LOG_FILE</code>, logging will got to <code>stderr</code>.

blocks|key|1476768|text|为此，您可以使用logging模块。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1476769|因此，在单元测试代码中，使用：|1476770|import+logging+as+log

def+test_foo(self):
++++log.debug("Some+debug+message.")
++++log.info("Some+info+message.")
++++log.warning("Some+warning+message.")
++++log.error("Some+error+message.")|code-block|syntax|javascript|1476771|默认情况下，警告和错误输出到/dev/stderr，因此它们应该在控制台上可见。|1476772|要自定义日志(如格式化)，请尝试以下示例：|1476773|#+Set-up+logger
if+args.verbose+or+args.debug:
++++logging.basicConfig(+stream=sys.stdout+)
++++root+=+logging.getLogger()
++++root.setLevel(logging.INFO+if+args.verbose+else+logging.DEBUG)
++++ch+=+logging.StreamHandler(sys.stdout)
++++ch.setLevel(logging.INFO+if+args.verbose+else+logging.DEBUG)
++++ch.setFormatter(logging.Formatter('%25(asctime)s+%25(levelname)s:+%25(name)s:+%25(message)s'))
++++root.addHandler(ch)
else:
++++logging.basicConfig(stream=sys.stderr)|1476774|entityMap^0|8|7|0|0|0|E|B|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|S|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|T|$]]

You can use <code>logging</code> module for that.

So in the unit test code, use:

<pre><code>import logging as log

def test_foo(self):
 log.debug("Some debug message.")
 log.info("Some info message.")
 log.warning("Some warning message.")
 log.error("Some error message.")
</code></pre>

By default warnings and errors are outputted to <code>/dev/stderr</code>, so they should be visible on the console.

To customize logs (such as formatting), try the following sample:

<pre><code># Set-up logger
if args.verbose or args.debug:
 logging.basicConfig( stream=sys.stdout )
 root = logging.getLogger()
 root.setLevel(logging.INFO if args.verbose else logging.DEBUG)
 ch = logging.StreamHandler(sys.stdout)
 ch.setLevel(logging.INFO if args.verbose else logging.DEBUG)
 ch.setFormatter(logging.Formatter('%(asctime)s %(levelname)s: %(name)s: %(message)s'))
 root.addHandler(ch)
else:
 logging.basicConfig(stream=sys.stderr)
</code></pre>

blocks|key|1476836|text|您还可以使用--locals选项：python3+-m+unittest+--locals。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1476837|来自python3+-m+unittest+-h：--locals++++Show+local+variables+in+tracebacks|1476838|entityMap^0|6|8|H|S|0|2|M|P|1A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

You can also use the <code>--locals</code> option: <code>python3 -m unittest --locals</code>.
From <code>python3 -m unittest -h</code>: <code>--locals Show local variables in tracebacks</code>

If I'm writing unit tests in Python (using the unittest module), is it possible to output data from a failed test, so I can examine it to help deduce what caused the error?
I am aware of the ability to create a customized message, which can carry some information, but sometimes you might deal with more complex data, that can't easily be represented as a string.
For example, suppose you had a class Foo, and were testing a method bar, using data from a list called testdata:
<pre><code>class TestBar(unittest.TestCase):
 def runTest(self):
 for t1, t2 in testdata:
 f = Foo(t1)
 self.assertEqual(f.bar(t2), 2)
</code></pre>
If the test failed, I might want to output t1, t2 and/or f, to see why this particular data resulted in a failure. By output, I mean that the variables can be accessed like any other variables, after the test has been run.

Outputting data from unit test in Python

单元测试

调试器

Windows

Python

如果我用Python编写单元测试(使用unittest模块)，是否可以从失败的测试中输出数据，这样我就可以检查它以帮助推断导致错误的原因？我知道创建自定义消息的能力，它可以携带一些信息，但有时您可能会处理更复杂的数据，这些数据不容易表示为字符串。例如，假设您有一个类Foo，并且正在使用一个名为testdata的列表中的...

问在Python中输出单元测试中的数据
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Python中输出单元测试中的数据EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Python中输出单元测试中的数据
EN