feat: to rst:590

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-01-14 23:14+0800\n"
+"PO-Revision-Date: 2024-01-17 01:09+0800\n"
 "Last-Translator: Liang-Bo Wang <[email protected]>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
 "tw)\n"
@@ -467,10 +467,13 @@ msgid ""
 "argument (or :func:`patch.object` with two arguments). The mock will be "
 "created for you and passed into the test function / method:"
 msgstr ""
+"如果你想使用一個 mock 進行 patch，你可以使用僅帶有一個引數的 :func:`patch`/ "
+"（或帶有兩個引數的 :func:`patch.object`/ ）。Mock 將被建立並被傳遞到測試函"
+"式 / 方法中："
 
 #: ../../library/unittest.mock-examples.rst:471
 msgid "You can stack up multiple patch decorators using this pattern::"
-msgstr ""
+msgstr "你可以使用這個模式堆疊多個 patch 裝飾器： ::"
 
 #: ../../library/unittest.mock-examples.rst:482
 msgid ""
@@ -479,44 +482,54 @@ msgid ""
 "decorators are applied). This means from the bottom up, so in the example "
 "above the mock for ``test_module.ClassName2`` is passed in first."
 msgstr ""
+"當你嵌套 patch 裝飾器時，mock 會以被應用的順序傳遞到裝飾函數（裝飾器應用的正"
+"常 *Python* 順序）。這意味著由下而上，因此在上面的範例中，\\ ``module."
+"ClassName2`` 的 mock 會先被傳入。"
 
 #: ../../library/unittest.mock-examples.rst:487
 msgid ""
 "There is also :func:`patch.dict` for setting values in a dictionary just "
 "during a scope and restoring the dictionary to its original state when the "
 "test ends:"
 msgstr ""
+"也有 :func:`patch.dict`，用於在測試範圍中設定字典內的值，並在測試結束時將其恢"
+"復為原始狀態："
 
 #: ../../library/unittest.mock-examples.rst:498
 msgid ""
 "``patch``, ``patch.object`` and ``patch.dict`` can all be used as context "
 "managers."
 msgstr ""
+"``patch``、``patch.object`` 和 ``patch.dict`` 都可以用來作為情境管理器。"
 
 #: ../../library/unittest.mock-examples.rst:500
 msgid ""
 "Where you use :func:`patch` to create a mock for you, you can get a "
 "reference to the mock using the \"as\" form of the with statement:"
 msgstr ""
+"當你使用 :func:`patch` 為你建立一個 mock 時，你可以使用 with 陳述式的 \"as\" "
+"形式來取得 mock 的參照："
 
 #: ../../library/unittest.mock-examples.rst:515
 msgid ""
 "As an alternative ``patch``, ``patch.object`` and ``patch.dict`` can be used "
 "as class decorators. When used in this way it is the same as applying the "
 "decorator individually to every method whose name starts with \"test\"."
 msgstr ""
+"另外，“patch”、“patch.object” 和 “patch.dict” 也可以用來作為類別裝飾器。以這"
+"種方式使用時，與將裝飾器單獨應用於名稱以 “test” 開頭的每個方法相同。"
 
 #: ../../library/unittest.mock-examples.rst:523
 msgid "Further Examples"
-msgstr ""
+msgstr "更多例子"
 
 #: ../../library/unittest.mock-examples.rst:526
 msgid "Here are some more examples for some slightly more advanced scenarios."
-msgstr ""
+msgstr "以下是一些更進階一點的情境的範例。"
 
 #: ../../library/unittest.mock-examples.rst:530
 msgid "Mocking chained calls"
-msgstr ""
+msgstr "Mock 鍊接呼叫"
 
 #: ../../library/unittest.mock-examples.rst:532
 msgid ""
@@ -525,30 +538,40 @@ msgid ""
 "for the first time, or you fetch its ``return_value`` before it has been "
 "called, a new :class:`Mock` is created."
 msgstr ""
+"一旦你了解了 :attr:`~Mock.return_value` 屬性，mock 鏈接呼叫其實就很簡單了。當"
+"一個 mock 第一次被呼叫，或者你在它被呼叫之前取得其 ``return_value`` 時，一個"
+"新的 :class:`Mock` 就會被建立。"
 
 #: ../../library/unittest.mock-examples.rst:537
 msgid ""
 "This means that you can see how the object returned from a call to a mocked "
 "object has been used by interrogating the ``return_value`` mock:"
 msgstr ""
+"這代表你可以透過訊問 (interrogate) / ``return_value`` mock 來了解一個對被 "
+"mock 的物件的呼叫回傳的物件是如何被使用的："
 
 #: ../../library/unittest.mock-examples.rst:545
 msgid ""
 "From here it is a simple step to configure and then make assertions about "
 "chained calls. Of course another alternative is writing your code in a more "
 "testable way in the first place..."
 msgstr ""
+"從這裡開始，只需一個簡單的步驟即可進行配置並對鍊接呼叫進行斷言。 當然，另一種"
+"選擇是先以更容易被測試的方式撰寫程式碼..."
 
 #: ../../library/unittest.mock-examples.rst:549
 msgid "So, suppose we have some code that looks a little bit like this:"
-msgstr ""
+msgstr "所以，假設我們有一些程式碼，看起來大概像這樣："
 
 #: ../../library/unittest.mock-examples.rst:558
 msgid ""
 "Assuming that ``BackendProvider`` is already well tested, how do we test "
 "``method()``? Specifically, we want to test that the code section ``# more "
 "code`` uses the response object in the correct way."
 msgstr ""
+"假設 ``BackendProvider`` 已經經過充分測試，那麼我們該如何測試 ``method()``？ "
+"具體來說，我們要測試程式碼部分 ``# more code`` 是否以正確的方式使用 "
+"``response`` 物件。"
 
 #: ../../library/unittest.mock-examples.rst:562
 msgid ""
@@ -559,25 +582,37 @@ msgid ""
 "assume the object it returns is 'file-like', so we'll ensure that our "
 "response object uses the builtin :func:`open` as its ``spec``."
 msgstr ""
+"由於此呼叫鍊是從實例屬性進行的，因此我們可以在 ``Something`` 實例上 monkey "
+"patch ``backend`` 屬性。在這種特定的情況下，我們只對最終呼叫 ``start_call`` "
+"的回傳值感興趣，因此我們不需要做太多配置。我們假設它傳回的物件是類檔案物件 "
+"(file-like)，因此我們會確保我們的 response 物件使用內建的 :func:`open` 作為"
+"其 ``spec``。"
 
 #: ../../library/unittest.mock-examples.rst:569
 msgid ""
 "To do this we create a mock instance as our mock backend and create a mock "
 "response object for it. To set the response as the return value for that "
 "final ``start_call`` we could do this::"
 msgstr ""
+"為此，我們建立一個 mock 實例作為我們的 mock backend，並為其建立一個 mock "
+"response 物件。要將 response 設定為最後的 ``start_call`` 的回傳值，我們可以這"
+"樣做： ::"
 
 #: ../../library/unittest.mock-examples.rst:575
 msgid ""
 "We can do that in a slightly nicer way using the :meth:`~Mock."
 "configure_mock` method to directly set the return value for us::"
 msgstr ""
+"我們可以使用 :meth:`~Mock.configure_mock` 方法來以稍為友善一點的方式為我們直"
+"接設定回傳值： ::"
 
 #: ../../library/unittest.mock-examples.rst:584
 msgid ""
 "With these we monkey patch the \"mock backend\" in place and can make the "
 "real call::"
 msgstr ""
+"有了這些，我們就可以將 \"mock backend\" monkey patch 到位，並且可以進行真正的"
+"呼叫： ::"
 
 #: ../../library/unittest.mock-examples.rst:590
 msgid ""
@@ -586,6 +621,9 @@ msgid ""
 "be several entries in ``mock_calls``. We can use :meth:`call.call_list` to "
 "create this list of calls for us::"
 msgstr ""
+"藉由使用 :attr:`~Mock.mock_calls`，我們可以使用一個斷言來檢查鍊接呼叫。一個鍊"
+"接呼叫是一行程式碼中的多個呼叫，因此 ``mock_calls`` 中會有多個條目。我們可以"
+"使用 :meth:`call.call_list` 來為我們建立這個呼叫串列： ::"
 
 #: ../../library/unittest.mock-examples.rst:601
 msgid "Partial mocking"