feat: to rst:1342

Author: ken71301

library/unittest.mock-examples.po

@@ -8,7 +8,7 @@ msgstr ""
 "Project-Id-Version: Python 3.12\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-09-09 00:03+0000\n"
-"PO-Revision-Date: 2024-04-02 21:55+0800\n"
+"PO-Revision-Date: 2024-04-09 00:26+0800\n"
 "Last-Translator: Liang-Bo Wang <me@liang2.tw>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
 "tw)\n"
@@ -1191,25 +1191,27 @@ msgstr ""
 
 #: ../../library/unittest.mock-examples.rst:1154
 msgid "Here's an example that mocks out the 'fooble' module."
-msgstr ""
+msgstr "下面是一個 mock out 'fooble' 模組的例子。"
 
 #: ../../library/unittest.mock-examples.rst:1166
 msgid ""
 "As you can see the ``import fooble`` succeeds, but on exit there is no "
 "'fooble' left in :data:`sys.modules`."
 msgstr ""
+"如你所建，``import fooble`` 成功了，但在離開之後，:data:`sys.modules` 中就沒"
+"有 'fooble' 了。"
 
 #: ../../library/unittest.mock-examples.rst:1169
 msgid "This also works for the ``from module import name`` form:"
-msgstr ""
+msgstr "這也適用於 ``from module import name`` 形式："
 
 #: ../../library/unittest.mock-examples.rst:1179
 msgid "With slightly more work you can also mock package imports:"
-msgstr ""
+msgstr "透過稍微多一點的處理，你也可以 mock 套件的引入："
 
 #: ../../library/unittest.mock-examples.rst:1192
 msgid "Tracking order of calls and less verbose call assertions"
-msgstr ""
+msgstr "追蹤呼叫順序與更簡潔的呼叫斷言"
 
 #: ../../library/unittest.mock-examples.rst:1194
 msgid ""
@@ -1218,6 +1220,9 @@ msgid ""
 "doesn't allow you to track the order of calls between separate mock objects, "
 "however we can use :attr:`~Mock.mock_calls` to achieve the same effect."
 msgstr ""
+":class:`Mock` 類別可以讓你透過 :attr:`~Mock.method_calls` 屬性追蹤 mock 物件"
+"上方法呼叫的\\ *順序*。這不會讓你可以追蹤不同的 mock 物件之間的呼叫順序，然而"
+"我們可以使用 :attr:`~Mock.mock_calls` 來達到相同的效果。"
 
 #: ../../library/unittest.mock-examples.rst:1199
 msgid ""
@@ -1226,19 +1231,27 @@ msgid ""
 "separate mocks from a parent one. Calls to those child mock will then all be "
 "recorded, in order, in the ``mock_calls`` of the parent:"
 msgstr ""
+"因為 mock 會在 ``mock_calls`` 中追蹤對子 mock 的呼叫，且存取 mock 的任意屬性"
+"會建立一個子 mock，所以我們可以從父 mock 建立不同的 mock。之後對這些子 mock "
+"的呼叫將依序全部記錄在父 mock 的 ``mock_calls`` 中："
 
 #: ../../library/unittest.mock-examples.rst:1216
 msgid ""
 "We can then assert about the calls, including the order, by comparing with "
 "the ``mock_calls`` attribute on the manager mock:"
 msgstr ""
+"之後我們可以透過與管理器 (manager) mock 上的 ``mock_calls`` 屬性進行比較來斷"
+"言呼叫的順序："
 
 #: ../../library/unittest.mock-examples.rst:1223
 msgid ""
 "If ``patch`` is creating, and putting in place, your mocks then you can "
 "attach them to a manager mock using the :meth:`~Mock.attach_mock` method. "
 "After attaching calls will be recorded in ``mock_calls`` of the manager. ::"
 msgstr ""
+"如果 ``patch`` 正在被建立並放置為你的 mock，那麼你可以使用 :meth:`~Mock."
+"attach_mock` 方法將它們附加到管理器 mock。附加之後，呼叫將被記錄在管理器的 "
+"``mock_calls``中。： ::"
 
 #: ../../library/unittest.mock-examples.rst:1242
 msgid ""
@@ -1248,12 +1261,17 @@ msgid ""
 "data:`call` object). If that sequence of calls are in :attr:`~Mock."
 "mock_calls` then the assert succeeds."
 msgstr ""
+"如果進行了多次呼叫，但你只對其中特定呼叫的序列感興趣，則可以是使用 :meth:"
+"`~Mock.assert_has_calls` 方法。這需要一個呼叫串列（使用 :data:`call` 物件建"
+"構）。如果該呼叫序列位於 :attr:`~Mock.mock_calls` 中，則斷言成功。"
 
 #: ../../library/unittest.mock-examples.rst:1256
 msgid ""
 "Even though the chained call ``m.one().two().three()`` aren't the only calls "
 "that have been made to the mock, the assert still succeeds."
 msgstr ""
+"儘管鍊接呼叫 ``m.one().two().three()`` 並不是對 mock 進行的唯一呼叫，斷言仍會"
+"成功。"
 
 #: ../../library/unittest.mock-examples.rst:1259
 msgid ""
@@ -1262,16 +1280,21 @@ msgid ""
 "about the order. In this case you can pass ``any_order=True`` to "
 "``assert_has_calls``:"
 msgstr ""
+"有時，可能會對一個 mock 進行多次呼叫，而你只對斷言其中\\ *某些*\\ 感興趣。你"
+"甚至可能不關心順序。在這種情況下，你可以將 ``any_order=True`` 傳遞給 "
+"``assert_has_calls``："
 
 #: ../../library/unittest.mock-examples.rst:1271
 msgid "More complex argument matching"
-msgstr ""
+msgstr "更複雜的引數匹配"
 
 #: ../../library/unittest.mock-examples.rst:1273
 msgid ""
 "Using the same basic concept as :data:`ANY` we can implement matchers to do "
 "more complex assertions on objects used as arguments to mocks."
 msgstr ""
+"使用與 :data:`ANY` 相同的基本概念，我們可以實作匹配器 (matcher)，對用作對 "
+"mock 的引數的物件進行更複雜的斷言。"
 
 #: ../../library/unittest.mock-examples.rst:1276
 msgid ""
@@ -1282,27 +1305,32 @@ msgid ""
 "attributes of this object then we can create a matcher that will check these "
 "attributes for us."
 msgstr ""
+"假設我們希望將某些物件傳遞給一個 mock，預設情況下，該 mock 會根據物件識別性"
+"（使用者定義類別的 Python 預設值）進行相等比較。要使用 :meth:`~Mock."
+"assert_called_with`，我們需要傳入完全相同的物件。如果我們只對該物件的某些屬性"
+"感興趣，那麼我們可以建立一個匹配器來為我們檢查這些屬性。"
 
 #: ../../library/unittest.mock-examples.rst:1283
 msgid ""
 "You can see in this example how a 'standard' call to ``assert_called_with`` "
 "isn't sufficient:"
 msgstr ""
+"你可以在這個範例中看到對 ``assert_called_with`` 的一個「標準」呼叫是不夠的："
 
 #: ../../library/unittest.mock-examples.rst:1298
 msgid ""
 "A comparison function for our ``Foo`` class might look something like this:"
-msgstr ""
+msgstr "對我們的 ``Foo`` 類別的比較函式看起來可能會像這樣："
 
 #: ../../library/unittest.mock-examples.rst:1310
 msgid ""
 "And a matcher object that can use comparison functions like this for its "
 "equality operation would look something like this:"
-msgstr ""
+msgstr "可以使用這樣的比較函式進行自身相等性運算的匹配器物件會長得像這樣："
 
 #: ../../library/unittest.mock-examples.rst:1321
 msgid "Putting all this together:"
-msgstr ""
+msgstr "把這些都放在一起："
 
 #: ../../library/unittest.mock-examples.rst:1326
 msgid ""
@@ -1313,12 +1341,18 @@ msgid ""
 "``assert_called_with`` passes, and if they don't an :exc:`AssertionError` is "
 "raised:"
 msgstr ""
+"``Matcher`` 是用我們想要比較的 ``Foo`` 物件和比較函式實例化的。在 "
+"``assert_called_with`` 中，``Matcher`` 相等方法將被呼叫，它將呼叫 mock 的物件"
+"與我們建立匹配器的物件進行比較。如果它們匹配，則 ``assert_called_with`` 會通"
+"過，如果它們不匹配，則會引發 :exc:`AssertionError`："
 
 #: ../../library/unittest.mock-examples.rst:1339
 msgid ""
 "With a bit of tweaking you could have the comparison function raise the :exc:"
 "`AssertionError` directly and provide a more useful failure message."
 msgstr ""
+"透過一些調整，你可以讓比較函式直接引發 :exc:`AssertionError` 並提供更有用的失"
+"敗訊息。"
 
 #: ../../library/unittest.mock-examples.rst:1342
 msgid ""
@@ -1328,3 +1362,8 @@ msgid ""
 "integration.match_equality <https://pyhamcrest.readthedocs.io/en/release-1.8/"
 "integration/#module-hamcrest.library.integration.match_equality>`_)."
 msgstr ""
+"從版本 1.5 開始，Python 測試函式庫 `PyHamcrest <https://pyhamcrest."
+"readthedocs.io/>`_ 提供了類似的功能，在這裡可能有用，以其相等匹配器的形式 "
+"(\\ `hamcrest.library.integration.match_equality <https://pyhamcrest."
+"readthedocs.io/en/release-1.8/integration/#module-hamcrest.library."
+"integration.match_equality>`_\\ )。"