@@ -2005,7 +2005,7 @@ msgstr ""
20052005#: ../../library/unittest.rst:1521
20062006msgid ""
20072007"This method accepts a coroutine that can be used as a cleanup function."
2008- msgstr ""
2008+ msgstr "此方法接受一个可被用作清理函数的协程。 "
20092009
20102010#: ../../library/unittest.rst:1525
20112011msgid ""
@@ -2016,17 +2016,22 @@ msgid ""
20162016" :meth:`run`'s caller. At the end of the test all the tasks in the event "
20172017"loop are cancelled."
20182018msgstr ""
2019+ "设置一个新的事件循环来运行测试,将结果收集至作为 *result* 传入的 :class:`TestResult`。 如果 *result* 被省略或为"
2020+ " ``None``,则会创建一个临时的结果对象(通过调用 :meth:`defaultTestResult` 方法)并使用它。 结果对象会被返回给 "
2021+ ":meth:`run` 的调用方。 在测试结束时事件循环中的所有任务都将被取消。"
20192022
20202023#: ../../library/unittest.rst:1533
20212024msgid "An example illustrating the order::"
2022- msgstr ""
2025+ msgstr "一个显示先后顺序的例子:: "
20232026
20242027#: ../../library/unittest.rst:1569
20252028msgid ""
20262029"After running the test, ``events`` would contain ``[\" setUp\" , "
20272030"\" asyncSetUp\" , \" test_response\" , \" asyncTearDown\" , \" tearDown\" , "
20282031"\" cleanup\" ]``."
20292032msgstr ""
2033+ "在运行测试之后,``events`` 将会包含 ``[\" setUp\" , \" asyncSetUp\" , \" test_response\" , "
2034+ "\" asyncTearDown\" , \" tearDown\" , \" cleanup\" ]``。"
20302035
20312036#: ../../library/unittest.rst:1574
20322037msgid ""
@@ -2036,6 +2041,8 @@ msgid ""
20362041"test cases using legacy test code, allowing it to be integrated into a "
20372042":mod:`unittest`-based test framework."
20382043msgstr ""
2044+ "这个类实现了 :class:`TestCase` 的部分接口,允许测试运行方驱动测试,但不提供可被测试代码用来检查和报告错误的方法。 "
2045+ "这个类被用于创建使用传统测试代码的测试用例,允许它被集成到基于 :mod:`unittest` 的测试框架中。"
20392046
20402047#: ../../library/unittest.rst:1584
20412048msgid "Deprecated aliases"
0 commit comments