From bc8b4625a7a6646fbf3cd7cda312c156282a93c3 Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Fri, 22 May 2026 02:17:25 -0700 Subject: [PATCH 1/4] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2981612 --- .../MSTest.Analyzers/xlf/Resources.de.xlf | 2 +- .../MSTest.Analyzers/xlf/Resources.es.xlf | 2 +- .../MSTest.Analyzers/xlf/Resources.it.xlf | 2 +- .../MSTest.Analyzers/xlf/Resources.ja.xlf | 2 +- .../MSTest.Analyzers/xlf/Resources.pt-BR.xlf | 2 +- .../MSTest.Analyzers/xlf/Resources.ru.xlf | 2 +- .../xlf/Resources.zh-Hans.xlf | 2 +- .../xlf/Resources.zh-Hant.xlf | 2 +- .../Resources/xlf/AzureDevOpsResources.de.xlf | 32 +++++++++---------- .../Resources/xlf/AzureDevOpsResources.es.xlf | 32 +++++++++---------- .../Resources/xlf/AzureDevOpsResources.it.xlf | 32 +++++++++---------- .../xlf/AzureDevOpsResources.pt-BR.xlf | 32 +++++++++---------- 12 files changed, 72 insertions(+), 72 deletions(-) diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.de.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.de.xlf index 0f6b990ca1..303c4c40da 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.de.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.de.xlf @@ -1042,7 +1042,7 @@ Der Typ, der diese Methoden deklariert, sollte auch die folgenden Regeln beachte Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + Die Verwendung von Asserts in Catch-Blöcken ist problematisch, da der Test auch dann erfolgreich ist, wenn keine Ausnahme ausgelöst wird und der Catch-Block nie ausgeführt wird. Verwenden Sie „Assert.Throws“, „Assert.ThrowsExactly“, „Assert.ThrowsAsync“ oder „Assert.ThrowsExactlyAsync“, um zu überprüfen, ob eine Ausnahme ausgelöst wird, und erstellen Sie dann zusätzliche Assertionen für die abgefangene Ausnahme, ohne den „try-catch“-Block zu verwenden. Die Regel kennzeichnet auch „throw new AssertFailedException(...)“ und „throw new AssertInconclusiveException(...)“ (die ausgeschriebenen Formen von „Assert.Fail“ und „Assert.Inconclusive“). „Assert.Inconclusive“ und „throw new AssertInconclusiveException(...)“ sind ausgenommen, wenn sie in einem gefilterten Catch („catch (...) when (...)“) verwendet werden, da das Herabstufen eines abgefangenen Fehlers zu einem Inconclusive-Ergebnis der einzige Anwendungsfall ist, der sich nicht ohne Catch-Block ausdrücken lässt. Bei anderen absichtlichen Umgehungen, zum Beispiel wenn eine zur Laufzeit erstellte Meldung an den Fehler angehängt wird, unterdrücken Sie die Diagnose mit „#pragma warning disable MSTEST0058“. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf index a9dbf38175..3e2d9f972b 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf @@ -1041,7 +1041,7 @@ El tipo que declara estos métodos también debe respetar las reglas siguientes: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + El uso de aserciones en bloques catch es problemático porque la prueba se superará incluso aunque no se produzca ninguna excepción y el bloque catch nunca se ejecuta. Use "Assert.Throws", "Assert.ThrowsExactly", "Assert.ThrowsAsync" o "Assert.ThrowsExactlyAsync" para comprobar que se produce una excepción y, a continuación, realice aserciones adicionales en la excepción detectada sin usar el bloque try-catch. La regla también marca "throw new AssertFailedException(...)" y "throw new AssertInconclusiveException(...)". (las formas desenredadas de "Assert.Fail" y "Assert.Inconclusive"). 'Assert.Inconclusive' (y 'throw new AssertInconclusiveException(...)') está exento cuando se usa dentro de un catch filtrado ('catch (...) when (...)'), porque degradar un error detectado a un resultado no concluyente es el único caso de uso que no se puede expresar sin un bloque catch. Para otras omisiones intencionadas (por ejemplo, adjuntar a un mensaje generado en tiempo de ejecución al error), suprime el diagnóstico con "#pragma warning disable MSTEST0058". diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.it.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.it.xlf index 1d9e07d651..b63f33d308 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.it.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.it.xlf @@ -1041,7 +1041,7 @@ Anche il tipo che dichiara questi metodi deve rispettare le regole seguenti: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + L'uso di asserzioni nei blocchi catch è problematico perché il test risulta superato anche se non viene generata alcuna eccezione e il blocco catch non viene mai eseguito. Utilizzare "Assert.Throws", "Assert.ThrowsExactly", "Assert.ThrowsAsync" o "Assert.ThrowsExactlyAsync" per verificare che venga generata un'eccezione, quindi effettuare ulteriori asserzioni sull'eccezione rilevata senza usare il blocco try-catch. La regola segnala anche "throw new AssertFailedException(...)" e "throw new AssertInconclusiveException(...)" (le forme semplificate di "Assert.Fail" e "Assert.Inconclusive"). "Assert.Inconclusive" (e "throw new AssertInconclusiveException(...)") è escluso quando viene usato all'interno di un catch filtrato ("catch (...) when (...)"), perché declassare un errore intercettato a un esito Inconclusive è l'unico caso d'uso che non può essere espresso senza un blocco catch. Per altri bypass intenzionali (ad esempio, allegare al fallimento un messaggio generato in fase di esecuzione), disabilita la diagnostica con "#pragma warning disable MSTEST0058". diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf index 04d6192f15..b06f9fdd68 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf @@ -1041,7 +1041,7 @@ The type declaring these methods should also respect the following rules: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + catch ブロックでアサートを使用すると、例外がスローされず、catch ブロックが実行されなくてもテストが成功するため、問題があります。'Assert.Throws'、'Assert.ThrowsExactly'、'Assert.ThrowsAsync'、または 'Assert.ThrowsExactlyAsync' を使用して例外がスローされたことを確認し、try-catch ブロックを使用せずにキャッチされた例外に対して追加のアサートを実行します。ルールでは、'throw new AssertFailedException(...)' と 'throw new AssertInconclusiveException(...)' にもフラグが設定されます('Assert.Fail' および 'Assert.Inconclusive' の下書き形式)。'Assert.Inconclusive' (および 'throw new AssertInconclusiveException(...)') は、フィルター処理された catch ('catch (...) when (...)') 内で使用すると除外されます。キャッチされた失敗を不確定な結果に降格することは、catch ブロックなしで表現できない唯一のユース ケースであるためです。その他の意図的なバイパス (たとえば、ランタイム ビルドのメッセージをエラーにアタッチする) の場合は、"#pragma 警告の無効化MSTEST0058' を使用して診断を抑制します。 diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf index 79853df796..5cb977417b 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf @@ -1041,7 +1041,7 @@ O tipo que declara esses métodos também deve respeitar as seguintes regras: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + Usar assertivas em blocos catch é problemático porque o teste será aprovado mesmo que nenhuma exceção seja lançada e o bloco catch nunca seja executado. Use "Assert.Throws", "Assert.ThrowsExactly", "Assert.ThrowsAsync" ou "Assert.ThrowsExactlyAsync" para verificar se uma exceção foi lançada e, em seguida, faça asserções adicionais sobre a exceção capturada sem usar o bloco try-catch. A regra também sinaliza "throw new AssertFailedException(...)" e "throw new AssertInconclusiveException(...)" (as formas expandidas de "Assert.Fail" e "Assert.Inconclusive"). "Assert.Inconclusive" (e "throw new AssertInconclusiveException(...)") é isento quando usado dentro de um catch filtrado ("catch (...) when (...)"), porque rebaixar uma falha detectada para um resultado inconclusivo é o único caso de uso que não pode ser expresso sem um bloco catch. Para outros bypasses intencionais (por exemplo, anexar uma mensagem criada em runtime à falha), suprime o diagnóstico com "pragma warning disable MSTEST0058". diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ru.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ru.xlf index a277ef3392..569d19c064 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ru.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ru.xlf @@ -1053,7 +1053,7 @@ The type declaring these methods should also respect the following rules: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + Использование утверждений в блоках catch является проблематичным, так как тест будет пройден, даже если не возникает исключение, а блок catch не выполняется. Используйте "Assert.Throws", "Assert.ThrowsExactly", "Assert.ThrowsAsync" или "Assert.ThrowsExactlyAsync" для проверки возникновения исключения, а затем выполните дополнительные утверждения перехваченного исключения без применения блока try-catch. Это правило также помечает конструкции "throw new AssertFailedException(...)" и "throw new AssertInconclusiveException(...)" (десахаризованные формы "Assert.Fail" и "Assert.Inconclusive"). Вызов "Assert.Inconclusive" (а также "throw new AssertInconclusiveException(...)") является исключением при использовании внутри фильтрующего блока "catch" ("catch (...) when (...)"), поскольку понижение статуса перехваченного сбоя до результата "Inconclusive" — это единственный сценарий использования, который невозможно реализовать без применения блока "catch". Для других намеренных обходов (например, прикрепления сообщения, сформированного во время выполнения) подавите диагностику с помощью "#pragma warning disable MSTEST0058". diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf index ad3e665feb..78f3cc5634 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf @@ -1041,7 +1041,7 @@ The type declaring these methods should also respect the following rules: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + 在 catch 块中使用断言是有问题的，因为即使没有引发异常且 catch 块从未执行，测试也会通过。请使用 "Assert.Throws"、"Assert.ThrowsExactly"、"Assert.ThrowsAsync" 或 "Assert.ThrowsExactlyAsync" 来验证是否引发了异常，然后对捕获的异常进行额外断言，而无需使用 try-catch 块。此规则还会标记 "throw new AssertFailedException(...)" 和 "throw new AssertInconclusiveException(...)" (即 "Assert.Fail" 和 "Assert.Inconclusive" 的简化形式)。"Assert.Inconclusive"(以及 "throw new AssertInconclusiveException(...)")在筛选后的 catch("catch(...) when(...)")中使用时可豁免，因为将捕获的失败降级为非确定性结果是唯一无法在没有 catch 块的情况下表达的场景。对于其他有意绕过的情况(例如，将运行时生成的消息附加到失败信息)，请使用 "#pragma warning disable MSTEST0058" 禁止显示此诊断信息。 diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hant.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hant.xlf index 4e4e85c0f7..b93f4e842c 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hant.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hant.xlf @@ -1041,7 +1041,7 @@ The type declaring these methods should also respect the following rules: Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. - Using asserts in catch blocks is problematic because the test will pass even if no exception is thrown and the catch block is never executed. Use 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' or 'Assert.ThrowsExactlyAsync' to verify that an exception is thrown, and then make additional assertions on the caught exception without using the try-catch block. The rule also flags 'throw new AssertFailedException(...)' and 'throw new AssertInconclusiveException(...)' (the desugared forms of 'Assert.Fail' and 'Assert.Inconclusive'). 'Assert.Inconclusive' (and 'throw new AssertInconclusiveException(...)') is exempt when used inside a filtered catch ('catch (...) when (...)'), because demoting a caught failure to an Inconclusive outcome is the only use case that cannot be expressed without a catch block. For other intentional bypasses (for example, attaching a runtime-built message to the failure), suppress the diagnostic with '#pragma warning disable MSTEST0058'. + 在 Catch 區塊中使用斷言會有問題，因為即使沒有拋出例外且 Catch 區塊從未執行，測試仍會通過。請使用 'Assert.Throws'、'Assert.ThrowsExactly'、'Assert.ThrowsAsync' 或 'Assert.ThrowsExactlyAsync' 來驗證是否有拋出例外，然後在不使用 try-catch 區塊的情況下，對捕捉到的例外進行進一步判斷提示。此規則也會標記 'throw new AssertFailedException(...)' 和 'throw new AssertInconclusiveException(...)' ('Assert.Fail' 和 'Assert.Inconclusive' 的去糖化形式)。'Assert.Inconclusive' (和 'throw new AssertInconclusiveException(...)') 在篩選的 catch ('catch (...) when (...)') 內使用時豁免，因為將攔截失敗降級為不明結果是唯一使用 catch 區塊才能表達的使用案例。對於其他刻意的旁路 (例如，將執行階段內建訊息連結至失敗)，請隱藏具有 '#pragma warning disable MSTEST0058' 的診斷。 diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.de.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.de.xlf index 28e255840e..c28331fd0d 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.de.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.de.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + Die Azure DevOps Liveveröffentlichung konnte den Testlauf nicht abschließen. Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + Die Azure DevOps Liveveröffentlichung konnte den Testlauf nicht erstellen. Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + Die Azure DevOps Liveveröffentlichung konnte die Koordinierungsdatei nicht löschen. Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + Die Azure DevOps Liveveröffentlichung hat nach {0} beim Warten auf {1} Teilnehmerdatei(en) eine Zeitüberschreitung erreicht; der Lauf wird trotzdem abgeschlossen. Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + Die Azure DevOps REST API-Anforderung mit Statuscode „{0}“ ist fehlgeschlagen. Antwort: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + Die Azure DevOps REST API hat eine unerwartete Antwortnutzlast zurückgegeben. '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + „--publish-azdo-test-results“ wurde festgelegt, aber die Azure DevOps Liveveröffentlichung ist deaktiviert, weil die folgenden Umgebungsvariablen fehlen oder ungültig sind: {0}. {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + Die Azure DevOps Liveveröffentlichung konnte azdo-runid.<buildId>.json für den gemeinsam genutzten Lauf nicht finden. {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + Die Azure DevOps Liveveröffentlichung konnte die Testergebnisse nicht veröffentlichen. Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + Die Azure DevOps REST API-Anforderung ist nach allen Wiederholungen fehlgeschlagen. Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + Die Azure DevOps Liveveröffentlichung hat eine azdo-runid.<buildId>.json-Datei für ein anderes Azure DevOps-Projekt gefunden. {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + Zeitüberschreitung Timeout: {0} - Timeout: {0} + Zeitüberschreitung: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + Benutzerdefinierter Azure DevOps Testlaufname für die Liveveröffentlichung von Testergebnissen. '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + „--publish-azdo-run-name“ erfordert, dass „--publish-azdo-test-results“ aktiviert ist. {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + Testergebnisse live auf der Azure DevOps Registerkarte „Tests“ veröffentlichen. diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.es.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.es.xlf index 8dff36bd25..1521999be2 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.es.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.es.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + La publicación en directo de Azure DevOps no pudo completar la ejecución de pruebas. Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + La publicación en directo de Azure DevOps no pudo crear la ejecución de pruebas. Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + La publicación en directo de Azure DevOps no pudo eliminar el archivo de coordinación Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + La publicación en directo de Azure DevOps agotó el tiempo de espera después de {0} esperar {1} archivo(s) de participante; finalizando la ejecución de todos modos. Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + La solicitud a la API de REST de Azure DevOps falló con el código de estado {0}. Respuesta: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + La API de REST de Azure DevOps devolvió una carga útil de respuesta inesperada. '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + Se estableció '--publish-azdo-test-results', pero la publicación en directo de Azure DevOps está deshabilitada porque faltan las siguientes variables de entorno o no son válidas: {0}. {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + La publicación en directo de Azure DevOps no pudo localizar azdo-runid.<buildId>.json para la ejecución compartida. {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + La publicación en directo de Azure DevOps no pudo publicar los resultados de las pruebas. Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + La solicitud a la API de REST de Azure DevOps falló después de todos los reintentos. Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + La publicación en directo de Azure DevOps encontró un archivo azdo-runid.<buildId>.json para otro proyecto de Azure DevOps. {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + Tiempo de expiración Timeout: {0} - Timeout: {0} + Tiempo de espera: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + Nombre personalizado de la ejecución de pruebas de Azure DevOps para la publicación en directo de resultados de pruebas. '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + '--publish-azdo-run-name' requiere que '--publish-azdo-test-results' esté habilitado {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + Publique los resultados de las pruebas en directo en la pestaña pruebas de Azure DevOps. diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.it.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.it.xlf index 2229587458..4959502a5f 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.it.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.it.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + La pubblicazione live di Azure DevOps non è riuscita a completare l'esecuzione dei test. Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + La pubblicazione live di Azure DevOps non è riuscita a creare l'esecuzione dei test. Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + La pubblicazione live di Azure DevOps non è riuscita a eliminare il file di coordinamento Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + La pubblicazione live di Azure DevOps è andata in timeout dopo {0} di attesa di {1} file partecipanti; l'esecuzione verrà comunque finalizzata. Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + La richiesta dell'API REST di Azure DevOps non è riuscita con codice di stato {0}. Risposta: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + L'API REST di Azure DevOps ha restituito un payload di risposta imprevisto. '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + "--publish-azdo-test-results" è stato impostato, ma la pubblicazione live di Azure DevOps è disabilitata perché le seguenti variabili di ambiente sono mancanti o non valide: {0}. {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + La pubblicazione live di Azure DevOps non è riuscita a individuare azdo-runid.<buildId>.json per l'esecuzione condivisa. {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + La pubblicazione live di Azure DevOps non è riuscita a pubblicare i risultati dei test. Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + La richiesta dell'API REST di Azure DevOps non è riuscita dopo tutti i tentativi. Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + La pubblicazione live di Azure DevOps ha trovato un file azdo-runid.<buildId>.json per un progetto Azure DevOps diverso. {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + Timeout Timeout: {0} - Timeout: {0} + Timeout: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + Nome personalizzato dell'esecuzione dei test di Azure DevOps per la pubblicazione live dei risultati dei test. '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + "--publish-azdo-run-name" richiede che "--publish-azdo-test-results" sia abilitato {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + Pubblica i risultati dei test in tempo reale nella scheda Test di Azure DevOps. diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.pt-BR.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.pt-BR.xlf index 475044b0f1..e3ba398d79 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.pt-BR.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.pt-BR.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + A publicação ao vivo do Azure DevOps falhou ao concluir a execução de teste. Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + A publicação ao vivo do Azure DevOps falhou ao criar a execução de teste. Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + A publicação ao vivo do Azure DevOps falhou ao excluir o arquivo de coordenação Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + A publicação ao vivo do Azure DevOps atingiu o tempo limite depois de {0} aguardar {1} arquivo(s) dos participantes, finalizando a execução mesmo assim. Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + A solicitação da API REST do Azure DevOps falhou com o código de status {0}. Resposta: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + A API REST do Azure DevOps retornou uma carga de resposta inesperada. '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + "--publish-azdo-test-results" foi definido, mas a publicação ao vivo do Azure DevOps está desabilitada porque as seguintes variáveis de ambiente estão ausentes ou são inválidas: {0}. {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + A publicação ao vivo do Azure DevOps não pôde localizar azdo-runid.<buildId>.json para a execução compartilhada. {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + A publicação ao vivo do Azure DevOps falhou ao publicar os resultados do teste. Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + A solicitação da API REST do Azure DevOps falhou após todas as tentativas. Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + A publicação ao vivo do Azure DevOps encontrou um arquivo azdo-runid.<buildId>.json para um projeto do Azure DevOps diferente. {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + Tempo limite Timeout: {0} - Timeout: {0} + Tempo limite: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + Nome de execução de teste do Azure DevOps personalizado para publicação de resultado de teste ao vivo. '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + "--publish-azdo-run-name" requer que "--publish-azdo-test-results" esteja habilitado {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + Publique os resultados do teste ao vivo na guia Testes do Azure DevOps. From 8a88146e6b398abb707a007335dfbb82e4ea2f32 Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Fri, 22 May 2026 02:18:56 -0700 Subject: [PATCH 2/4] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2981612 --- .../xlf/AzureDevOpsResources.zh-Hans.xlf | 32 +++++++++---------- .../xlf/AzureDevOpsResources.zh-Hant.xlf | 32 +++++++++---------- .../Resources/xlf/CrashDumpResources.cs.xlf | 5 --- .../Resources/xlf/CrashDumpResources.de.xlf | 5 --- .../Resources/xlf/CrashDumpResources.es.xlf | 5 --- .../Resources/xlf/CrashDumpResources.fr.xlf | 5 --- .../Resources/xlf/CrashDumpResources.it.xlf | 5 --- .../Resources/xlf/CrashDumpResources.ja.xlf | 5 --- .../Resources/xlf/CrashDumpResources.ko.xlf | 5 --- .../Resources/xlf/CrashDumpResources.pl.xlf | 5 --- .../xlf/CrashDumpResources.pt-BR.xlf | 5 --- .../Resources/xlf/CrashDumpResources.ru.xlf | 5 --- .../Resources/xlf/CrashDumpResources.tr.xlf | 5 --- .../xlf/CrashDumpResources.zh-Hans.xlf | 5 --- .../xlf/CrashDumpResources.zh-Hant.xlf | 5 --- 15 files changed, 32 insertions(+), 97 deletions(-) diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hans.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hans.xlf index cb3ddaf267..51cfba657d 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hans.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hans.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + Azure DevOps 实时发布未能完成测试运行。 Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + Azure DevOps 实时发布未能创建测试运行。 Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + Azure DevOps 实时发布未能删除协调文件 Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + Azure DevOps 实时发布在等待 {1} 个参与者文件 {0} 后超时；仍将完成运行。 Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + Azure DevOps REST API 请求失败，状态代码为 {0}。响应: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + Azure DevOps REST API 返回了意外的响应有效负载。 '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + 已设置 "--publish-azdo-test-results"，但由于以下环境变量缺失或无效，Azure DevOps 实时发布已禁用: {0}。 {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + Azure DevOps 实时发布无法找到共享运行对应的 azdo-runid.<buildId>.json 文件。 {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + Azure DevOps 实时发布未能发布测试结果。 Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + Azure DevOps REST API 请求在所有重试后均失败。 Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + Azure DevOps 实时发布发现了属于其他 Azure DevOps 项目的 azdo-runid.<buildId>.json 文件。 {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + 超时 Timeout: {0} - Timeout: {0} + 超时: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + 用于实时测试结果发布的自定义 Azure DevOps 测试运行名称。 '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + "--publish-azdo-run-name" 需要启用 "--publish-azdo-test-results" {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + 将测试结果实时发布到 Azure DevOps 测试选项卡。 diff --git a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hant.xlf b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hant.xlf index dd1b932355..588909daa8 100644 --- a/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hant.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.zh-Hant.xlf @@ -29,67 +29,67 @@ Azure DevOps live publishing failed to complete the test run. - Azure DevOps live publishing failed to complete the test run. + Azure DevOps 即時發佈無法完成測試執行。 Azure DevOps live publishing failed to create the test run. - Azure DevOps live publishing failed to create the test run. + Azure DevOps 即時發佈無法建立測試執行。 Azure DevOps live publishing failed to delete coordination file - Azure DevOps live publishing failed to delete coordination file + Azure DevOps 即時發佈無法刪除協調檔案 Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. - Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway. + Azure DevOps 即時發佈在 {0} 等待 {1} 個參與者檔案後逾時; 無論如何都要完成執行。 Azure DevOps REST API request failed with status code {0}. Response: {1} - Azure DevOps REST API request failed with status code {0}. Response: {1} + Azure DevOps REST API 要求失敗，狀態碼為 {0}。回應: {1} Azure DevOps REST API returned an unexpected response payload. - Azure DevOps REST API returned an unexpected response payload. + Azure DevOps REST API 傳回了未預期的回應承載。 '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. - '--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}. + '--publish-azdo-test-results' 已設定，但 Azure DevOps 即時發佈已停用，因為下列環境變數遺失或無效: {0}。 {Locked='--publish-azdo-test-results'} Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. - Azure DevOps live publishing could not locate azdo-runid.<buildId>.json for the shared run. + Azure DevOps 即時發佈找不到共用執行的 azdo-runid.<buildId>.json。 {Locked="azdo-runid.<buildId>.json"} Azure DevOps live publishing failed to publish test results. - Azure DevOps live publishing failed to publish test results. + Azure DevOps 即時發佈無法發佈測試結果。 Azure DevOps REST API request failed after all retries. - Azure DevOps REST API request failed after all retries. + 在所有重試後，Azure DevOps REST API 要求失敗。 Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. - Azure DevOps live publishing found an azdo-runid.<buildId>.json file for a different Azure DevOps project. + Azure DevOps 即時發佈找到不同 Azure DevOps 專案的 azdo-runid.<buildId>.json 檔案。 {Locked="azdo-runid.<buildId>.json"} Timeout - Timeout + 逾時 Timeout: {0} - Timeout: {0} + 逾時: {0} @@ -184,17 +184,17 @@ Custom Azure DevOps test run name for live test-result publishing. - Custom Azure DevOps test run name for live test-result publishing. + 即時測試結果發佈的自訂 Azure DevOps 測試執行名稱。 '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled - '--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled + '--publish-azdo-run-name' 需要啟用 '--publish-azdo-test-results' {Locked='--publish-azdo-run-name'}{Locked='--publish-azdo-test-results'} Publish test results live to the Azure DevOps Tests tab. - Publish test results live to the Azure DevOps Tests tab. + 將測試結果即時發佈至 Azure DevOps 測試索引標籤。 diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.cs.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.cs.xlf index 84b182a7bb..ae1ff793fd 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.cs.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.cs.xlf @@ -111,11 +111,6 @@ Další informace najdete na https://learn.microsoft.com/dotnet/core/diagnostics [Pouze Linux/macOS] Při chybovém ukončení testovacího procesu vygeneruje zprávu o chybovém ukončení ve formátu JSON. Pokud chcete vygenerovat také soubor výpisu paměti, zkombinujte s parametrem --crashdump. Pokud se používá samostatně, vyžaduje .NET 7+; při kombinaci s parametrem --crashdump vyžaduje .NET 6+. Tento požadavek na modul runtime není nástrojem vynucován: v případě nepodporovaných modulů runtime nebude vygenerována žádná zpráva o chybovém ukončení. Nepodporuje se ve Windows kvůli omezení modulu runtime .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Žádosti typu {0} nejsou podporovány. diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.de.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.de.xlf index c9052305cf..34fff8634d 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.de.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.de.xlf @@ -111,11 +111,6 @@ Weitere Informationen finden Sie unter https://learn.microsoft.com/dotnet/core/d [Nur Linux/macOS] Generieren Sie einen JSON-Absturzbericht, wenn der Testprozess abstürzt. Kombinieren Sie dies mit „--crashdump“, um auch eine Absturzabbilddatei zu generieren. Erfordert .NET 7 und höher, wenn es allein verwendet wird; .NET 6+ in Kombination mit „--crashdump“. Diese Runtimeanforderung wird vom Tool nicht erzwungen: Bei nicht unterstützten Runtimes wird kein Absturzbericht ausgegeben. Wird unter Windows aufgrund einer .NET-Runtimeeinschränkung nicht unterstützt (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Anforderungen vom Typ "{0}" werden nicht unterstützt diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.es.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.es.xlf index 9bb1cce73d..6604e88901 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.es.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.es.xlf @@ -111,11 +111,6 @@ Para obtener más información, visite https://learn.microsoft.com/dotnet/core/d [Solo Linux/macOS] Genere un informe de bloqueo JSON cuando el proceso de prueba se bloquee. Combine con "--crashdump" para generar también un archivo de volcado. Requiere .NET 7+ cuando se usa solo; .NET 6+ cuando se combina con "--crashdump". La herramienta no aplica este requisito de tiempo de ejecución: en los entornos de ejecución no admitidos, no se emitirá ningún informe de bloqueo. No se admite en Windows debido a una limitación del entorno de ejecución de .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported No se admiten solicitudes de tipo '{0}' diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.fr.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.fr.xlf index 4162947c65..f819ecd771 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.fr.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.fr.xlf @@ -111,11 +111,6 @@ Pour plus d’informations, visitez https://learn.microsoft.com/dotnet/core/diag [Linux/macOS uniquement] Générez un rapport d’incident JSON lorsque le processus de test se bloque. Combinez-le avec « --crashdump » pour générer également un fichier de vidage. Nécessite .NET 7+ lorsqu’il est utilisé seul ; .NET 6+ lorsqu’il est combiné avec « --crashdump ». L’outil n’applique pas cette exigence de runtime : aucun rapport d’incident ne sera généré sur les runtimes non pris en charge. Non pris en charge sur Windows en raison d’une limitation du runtime .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Les demandes de type «{0}» ne sont pas prises en charge diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.it.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.it.xlf index dbab5ad895..c32f8beb77 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.it.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.it.xlf @@ -111,11 +111,6 @@ Per altre informazioni, visitare https://learn.microsoft.com/dotnet/core/diagnos [Solo Linux/macOS] Generare un report di arresto anomalo JSON quando il processo di test si arresta in modo anomalo. Combinare con ''--crashdump'' per generare anche un file di dump. Richiede .NET 7+ se usato da solo; .NET 6+ in combinazione con ''--crashdump''. Questo requisito di runtime non viene applicato dallo strumento: nei runtime non supportati non verrà generato alcun rapporto di arresto anomalo. Non supportato in Windows a causa di una limitazione del runtime .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Le richieste di tipo '{0}' non sono supportate diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ja.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ja.xlf index 34ad568361..27af36a8af 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ja.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ja.xlf @@ -111,11 +111,6 @@ For more information visit https://learn.microsoft.com/dotnet/core/diagnostics/c [Linux/macOS のみ] テスト プロセスがクラッシュしたときに JSON クラッシュ レポートを生成します。'--crashdump' と組み合わせて、ダンプ ファイルも生成できます。単独で使用する場合は .NET 7 以降、'--crashdump' と組み合わせる場合は .NET 6 以降が必要です。このランタイム要件はツールでは強制されません。サポートされていないランタイムではクラッシュ レポートは出力されません。.NET ランタイムの制限により、Windows ではサポートされません (dotnet/runtime#80191)。 - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported 型 '{0}' の要求はサポートされていません diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ko.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ko.xlf index 0afd48b958..6b0883fcf6 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ko.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ko.xlf @@ -111,11 +111,6 @@ For more information visit https://learn.microsoft.com/dotnet/core/diagnostics/c [Linux/macOS만 해당] 테스트 프로세스가 충돌할 때 JSON 크래시 보고서를 생성합니다. '--crashdump'와 함께 사용하면 덤프 파일도 생성합니다. 단독으로 사용할 때는 .NET 7+가 필요합니다. '--crashdump'와 함께 사용할 때는 .NET 6+가 필요합니다. 이 런타임 요구 사항은 도구에서 강제하지 않습니다. 지원되지 않는 런타임에서는 크래시 보고서가 생성되지 않습니다. .NET 런타임 제한(dotnet/runtime#80191)으로 인해 Windows에서는 지원되지 않습니다. - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported '{0}' 유형의 요청은 지원되지 않습니다. diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pl.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pl.xlf index b9a1eee4e4..dbe2f6f28f 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pl.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pl.xlf @@ -111,11 +111,6 @@ Aby uzyskać więcej informacji, odwiedź stronę https://learn.microsoft.com/do [Tylko Linux/macOS] Generuj raport JSON o awarii, gdy proces testowy ulegnie awarii. Połącz to z elementem „--crashdump”, aby też wygenerować plik zrzutu. Gdy używasz tego samodzielnie, wymaga to platformy .NET 7+; gdy używasz razem z elementem „--crashdump” — platformy .NET 6+. To wymaganie dotyczące środowiska uruchomieniowego nie jest wymuszane przez narzędzie: w nieobsługiwanych środowiskach uruchomieniowych nie będzie emitowany żaden raport o awarii. Nieobsługiwane w systemie Windows z powodu ograniczenia środowiska uruchomieniowego platformy .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Żądania typu „{0}” nie są obsługiwane diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pt-BR.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pt-BR.xlf index 346eb56b6a..8ee7367d93 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pt-BR.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.pt-BR.xlf @@ -111,11 +111,6 @@ Para obter mais informações, visite https://learn.microsoft.com/dotnet/core/di [Somente Linux/macOS] Gere um relatório de falha em JSON quando o processo de teste travar. Combine com '--crashdump' para também gerar um arquivo de despejo. Requer o .NET 7+ quando usado sozinho; .NET 6+ quando combinado com '--crashdump'. Esse requisito de runtime não é imposto pela ferramenta: em runtimes sem suporte. Nenhum relatório de falha será emitido. Sem suporte no Windows devido a uma limitação de runtime do .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Não há suporte para solicitações de tipo ''{0}'' diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ru.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ru.xlf index a6587dd1c1..05e8acb8a4 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ru.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.ru.xlf @@ -111,11 +111,6 @@ For more information visit https://learn.microsoft.com/dotnet/core/diagnostics/c [Только для Linux/macOS] Создать JSON-отчет об аварийном завершении, если процесс тестирования завершается аварийно. Чтобы также создать файл дампа, используйте вместе с --crashdump. При отдельном использовании требуется .NET 7+; в сочетании с --crashdump — .NET 6+. Это требование среды выполнения не применяется принудительно средством: в неподдерживаемых средах выполнения отчет об аварийном завершении не создается. Не поддерживается в Windows из-за ограничения среды выполнения .NET (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported Запросы типа "{0}" не поддерживаются diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.tr.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.tr.xlf index 381bd4d84e..ca02aa1fe2 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.tr.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.tr.xlf @@ -111,11 +111,6 @@ Daha fazla bilgi için https://learn.microsoft.com/dotnet/core/diagnostics/colle `[Yalnızca Linux/macOS] Test işlemi kilitlendiğinde bir JSON kilitlenme raporu oluşturun. Ayrıca bir döküm dosyası oluşturmak için '--crashdump' ile birlikte kullanın. Tek başına kullanıldığında .NET 7+ gerektirir. '--crashdump' ile birlikte kullanıldığında .NET 6+ gerektirir. Bu çalışma zamanı gereksinimi araç tarafından zorunlu kılınmaz. Desteklenmeyen çalışma zamanlarında kilitlenme raporu oluşturulmaz. .NET çalışma zamanı sınırlaması nedeniyle Windows'ta desteklenmez (dotnet/runtime#80191). - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported '{0}' türündeki istek desteklenmiyor diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hans.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hans.xlf index 12208794a2..beedd42ac9 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hans.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hans.xlf @@ -111,11 +111,6 @@ For more information visit https://learn.microsoft.com/dotnet/core/diagnostics/c [仅 Linux/macOS] 测试进程故障时生成 JSON 故障报表。与 "--crashdump" 结合使用时，还会生成转储文件。单独使用时需要 .NET 7+；与 "--crashdump" 结合使用时需要 .NET 6+。此工具不强制执行此运行时要求: 在不受支持的运行时上，不会生成故障报表。由于 .NET 运行时限制(dotnet/runtime#80191)，在 Windows 上不受支持。 - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported 不支持类型为“{0}”的请求 diff --git a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hant.xlf b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hant.xlf index 428ad4e4fc..8ce98477ed 100644 --- a/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hant.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.CrashDump/Resources/xlf/CrashDumpResources.zh-Hant.xlf @@ -111,11 +111,6 @@ For more information visit https://learn.microsoft.com/dotnet/core/diagnostics/c [僅限 Linux/macOS] 當測試處理序損毀時，產生 JSON 損毀報告。將此選項與 '--crashdump' 一起使用，也可產生傾印檔案。單獨使用時需要 .NET 7 以上版本；與 '--crashdump' 搭配使用時需要 .NET 6 以上版本。工具不會強制檢查此執行階段需求: 在不支援的執行階段上，不會輸出損毀報告。由於 .NET 執行階段的限制 (dotnet/runtime#80191)，Windows 不支援此功能。 - - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - You specified one or more crash dump parameters but did not enable crash dumps. Add --crashdump or --crash-report to the command line. - - Requests of type '{0}' is not supported 不支援類型 '{0}' 的要求 From 3c7ed5d6409c28749b740db8445a5b6eafab1036 Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Fri, 22 May 2026 02:20:25 -0700 Subject: [PATCH 3/4] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2981612 --- .../Resources/xlf/ExtensionResources.de.xlf | 24 +++++++++---------- .../Resources/xlf/ExtensionResources.es.xlf | 24 +++++++++---------- .../Resources/xlf/ExtensionResources.it.xlf | 24 +++++++++---------- .../xlf/ExtensionResources.pt-BR.xlf | 24 +++++++++---------- .../Resources/xlf/ExtensionResources.ru.xlf | 24 +++++++++---------- .../xlf/ExtensionResources.zh-Hans.xlf | 24 +++++++++---------- .../xlf/ExtensionResources.zh-Hant.xlf | 24 +++++++++---------- 7 files changed, 84 insertions(+), 84 deletions(-) diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.de.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.de.xlf index 51820ee0fa..fe2c7404f8 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.de.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.de.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + Eigenständiger HTML-Testbericht HTML Report - HTML Report + HTML-Bericht Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + Warnung: Die HTML-Berichtsdatei „{0}“ ist bereits vorhanden und wird überschrieben. '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + Das Dateinamenargument „--report-html-filename“ muss mit „.html“ enden (z. B. --report-html-filename myreport.html). The name of the generated HTML report - The name of the generated HTML report + Der Name des generierten HTML-Berichts. '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + „--report-html-filename“ erfordert, dass „--report-html“ aktiviert ist. file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + Das Dateinamenargument darf keinen Pfad und keine ungültigen Zeichen enthalten (z. B. --report-html-filename myreport.html). Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + Erstellt einen eigenständigen HTML-Bericht für die aktuelle Testsitzung HTML report generator - HTML report generator + HTML-Bericht-Generator '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + „--report-html“ kann bei Verwendung von „--list-tests“ nicht aktiviert werden Enable generating an HTML report - Enable generating an HTML report + Das Erstellen eines HTML-Berichts aktivieren HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + Der HTML-Bericht-Generator funktioniert nur mit Generatoren vom Typ "Microsoft.Testing.Platform.Builder.TestApplicationBuilder" diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.es.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.es.xlf index af01ade735..75b6592d33 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.es.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.es.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + Informe de prueba HTML independiente HTML Report - HTML Report + Informe HTML Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + Advertencia: el archivo de informe HTML "{0}" ya existe y se sobrescribirá. '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + El argumento del nombre de archivo '--report-html-filename' debe terminar en '.html' (por ejemplo, --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + Nombre del informe HTML generado '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + '--report-html-filename' requiere que '--report-html' esté habilitado file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + el argumento de nombre de archivo no debe contener una ruta de acceso ni caracteres no válidos (por ejemplo, --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + Generar un informe HTML independiente para la sesión de prueba actual HTML report generator - HTML report generator + Generador de informes HTML '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + '--report-html' no se puede habilitar cuando se usa '--list-tests' Enable generating an HTML report - Enable generating an HTML report + Habilitar la generación de un informe HTML HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + El generador de informes HTML solo funciona con generadores de tipo "Microsoft.Testing.Platform.Builder.TestApplicationBuilder" diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.it.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.it.xlf index b2fb74ae3a..8d2ec09e31 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.it.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.it.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + Report di test HTML autonomo HTML Report - HTML Report + Report HTML Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + Avviso: il file di report HTML "{0}" esiste già e verrà sovrascritto. '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + L'argomento del nome file "--report-html-filename" deve terminare con ".html" (ad esempio --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + Nome del report HTML generato '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + "--report-html-filename" richiede che "--report-html" sia abilitato file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + l'argomento del nome file non deve contenere un percorso o caratteri non validi (ad esempio --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + Generare un report HTML autonomo per la sessione di test corrente HTML report generator - HTML report generator + Generatore di report HTML '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + Non è possibile abilitare "--report-html" quando si usa "--list-tests" Enable generating an HTML report - Enable generating an HTML report + Abilita la generazione di un report HTML HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + Il generatore di report HTML funziona solo con i generatori di tipo "Microsoft.Testing.Platform.Builder.TestApplicationBuilder" diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.pt-BR.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.pt-BR.xlf index f132a40a28..4f8d2b4c8f 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.pt-BR.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.pt-BR.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + Relatório de teste html autossuficiente HTML Report - HTML Report + Relatório HTML Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + Aviso: o arquivo de relatório HTML "{0}" já existe e será substituído. '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + O argumento de nome de arquivo "--report-html-filename" deve terminar com ".html" (por exemplo, --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + O nome do relatório HTML gerado '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + "--report-html-filename" requer que "--report-html" esteja habilitado file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + o argumento de nome de arquivo não deve conter um caminho ou caracteres inválidos (por exemplo, --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + Produzir um relatório HTML autossuficiente para a sessão de teste atual HTML report generator - HTML report generator + Gerador de relatório HTML '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + Não é possível habilitar "--report-html" ao usar "--list-tests" Enable generating an HTML report - Enable generating an HTML report + Habilitar a geração de um relatório HTML HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + O gerador de relatório HTML só funciona com construtores do tipo "Microsoft.Testing.Platform.Builder.TestApplicationBuildert" diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.ru.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.ru.xlf index c535bab949..42a1d588ed 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.ru.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.ru.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + Автономный тестовый отчет в формате HTML HTML Report - HTML Report + Отчет в формате HTML Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + Предупреждение: HTML-файл отчета "{0}" уже существует и будет перезаписан. '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + Аргумент имени файла "--report-html-filename" должен оканчиваться на ".html" (например: --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + Имя сгенерированного отчета в формате HTML '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + Для "--report-html-filename" требуется включить "--report-html" file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + аргумент с именем файла не должен содержать путь или недопустимые символы (например: --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + Создать автономный отчет в формате HTML для текущего тестового сеанса HTML report generator - HTML report generator + Генератор отчетов в формате HTML '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + Параметр "--report-html" нельзя включить при использовании "--list-tests" Enable generating an HTML report - Enable generating an HTML report + Включить создание отчета в формате HTML HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + Генератор отчетов в формате HTML работает только со сборщиками типа "Microsoft.Testing.Platform.Builder.TestApplicationBuilder" diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hans.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hans.xlf index ac7f70bd02..1d7e4bbf9f 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hans.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hans.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + 独立 HTML 测试报告 HTML Report - HTML Report + HTML 报表 Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + 警告: HTML 报表文件“{0}”已存在，将被覆盖。 '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + "--report-html-filename" 文件名参数必须以 ".html" 结尾(例如 --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + 生成的 HTML 报表的名称 '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + "--report-html-filename" 需要启用 "--report-html" file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + 文件名参数不得包含路径或无效字符(例如 --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + 为当前测试会话生成独立的 HTML 报表 HTML report generator - HTML report generator + HTML 报表生成器 '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + 使用 "--list-tests" 时无法启用 "--report-html" Enable generating an HTML report - Enable generating an HTML report + 启用生成 HTML 报表 HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + HTML 报表生成器仅适用于 "Microsoft.Testing.Platform.Builder.TestApplicationBuilder" 类型的生成器 diff --git a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hant.xlf b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hant.xlf index 193fe97cbc..1401b444dc 100644 --- a/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hant.xlf +++ b/src/Platform/Microsoft.Testing.Extensions.HtmlReport/Resources/xlf/ExtensionResources.zh-Hant.xlf @@ -4,62 +4,62 @@ Self-contained HTML test report - Self-contained HTML test report + 獨立式 HTML 測試報告 HTML Report - HTML Report + HTML 報告 Warning: HTML report file '{0}' already exists and will be overwritten. - Warning: HTML report file '{0}' already exists and will be overwritten. + 警告: HTML 報告檔案 '{0}' 已經存在，將會被覆寫。 '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) - '--report-html-filename' file name argument must end with '.html' (e.g. --report-html-filename myreport.html) + '--report-html-filename' 檔名引數的結尾必須是 '.html' (例如 --report-html-filename myreport.html) The name of the generated HTML report - The name of the generated HTML report + 產生的 TRX 報告名稱 '--report-html-filename' requires '--report-html' to be enabled - '--report-html-filename' requires '--report-html' to be enabled + '--report-html-filename' 需要啟用 '--report-html' file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) - file name argument must not contain a path or invalid characters (e.g. --report-html-filename myreport.html) + 檔案名稱引數不能包含路徑或無效字元 (例如 --report-html-filename myreport.html) Produce a self-contained HTML report for the current test session - Produce a self-contained HTML report for the current test session + 為目前的測試工作階段產生獨立式 HTML 報告 HTML report generator - HTML report generator + TRX 報告產生器 '--report-html' cannot be enabled when using '--list-tests' - '--report-html' cannot be enabled when using '--list-tests' + 使用 '--list-tests' 時，無法啟用 '--report-html' Enable generating an HTML report - Enable generating an HTML report + 啟用產生 HTML 報告 HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' - HTML report generator only works with builders of type 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' + HTML 報表產生器只能與類型為 'Microsoft.Testing.Platform.Builder.TestApplicationBuilder' 的建立器一起運作 From 8977ab52d1d2bcf154cb0594dee422f508b1741a Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Fri, 22 May 2026 02:23:23 -0700 Subject: [PATCH 4/4] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2981612 --- .../TestFramework/Resources/xlf/FrameworkMessages.cs.xlf | 6 +++--- .../TestFramework/Resources/xlf/FrameworkMessages.de.xlf | 6 +++--- .../TestFramework/Resources/xlf/FrameworkMessages.es.xlf | 6 +++--- .../TestFramework/Resources/xlf/FrameworkMessages.pt-BR.xlf | 6 +++--- .../TestFramework/Resources/xlf/FrameworkMessages.ru.xlf | 6 +++--- .../Resources/xlf/FrameworkMessages.zh-Hans.xlf | 6 +++--- .../Resources/xlf/FrameworkMessages.zh-Hant.xlf | 6 +++--- 7 files changed, 21 insertions(+), 21 deletions(-) diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.cs.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.cs.xlf index 128c18e3c8..1336e27162 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.cs.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.cs.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + Očekával se řetězec, který neodpovídá zadanému vzoru. @@ -634,7 +634,7 @@ Skutečnost: {2} Expected values to differ. - Expected values to differ. + Očekávaly se lišící se hodnoty. @@ -669,7 +669,7 @@ Skutečnost: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + Očekával se řetězec odpovídající zadanému vzoru. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.de.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.de.xlf index 907d49d6b9..80bc751444 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.de.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.de.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + Es wurde erwartet, dass die Zeichenfolge nicht mit dem angegebenen Muster übereinstimmt. @@ -634,7 +634,7 @@ Tatsächlich: {2} Expected values to differ. - Expected values to differ. + Es wurde erwartet, dass sich die Werte unterscheiden. @@ -669,7 +669,7 @@ Tatsächlich: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + Es wurde erwartet, dass die Zeichenfolge mit dem angegebenen Muster übereinstimmt. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf index b9a70f1687..691f17512f 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + Se esperaba que la cadena no coincidía con el patrón especificado. @@ -634,7 +634,7 @@ Real: {2} Expected values to differ. - Expected values to differ. + Se esperaba que los valores variaran. @@ -669,7 +669,7 @@ Real: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + Se esperaba que la cadena coincidía con el patrón especificado. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pt-BR.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pt-BR.xlf index 366d515cba..2589996298 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pt-BR.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pt-BR.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + Esperava-se que a cadeia de caracteres não correspondesse ao padrão especificado. @@ -634,7 +634,7 @@ Real: {2} Expected values to differ. - Expected values to differ. + Esperava-se que os valores fossem diferentes. @@ -669,7 +669,7 @@ Real: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + Esperava-se que a cadeia de caracteres correspondesse ao padrão especificado. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ru.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ru.xlf index 2579cdf66d..8033d4d3da 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ru.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ru.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + Ожидалось, что строка не будет соответствовать указанному шаблону. @@ -634,7 +634,7 @@ Actual: {2} Expected values to differ. - Expected values to differ. + Ожидалось, что значения будут различаться. @@ -669,7 +669,7 @@ Actual: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + Ожидалось, что строка будет соответствовать указанному шаблону. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf index 2ab13c9b1c..a8351c4fa9 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + 应为不匹配指定模式的字符串。 @@ -634,7 +634,7 @@ Actual: {2} Expected values to differ. - Expected values to differ. + 预期值应不同。 @@ -669,7 +669,7 @@ Actual: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + 应为匹配指定模式的字符串。 diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hant.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hant.xlf index 5e7f620b07..b0237d196c 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hant.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hant.xlf @@ -455,7 +455,7 @@ Expected string to not match the specified pattern. - Expected string to not match the specified pattern. + 預期字串與指定的模式不符。 @@ -634,7 +634,7 @@ Actual: {2} Expected values to differ. - Expected values to differ. + 預期值會有所不同。 @@ -669,7 +669,7 @@ Actual: {2} Expected string to match the specified pattern. - Expected string to match the specified pattern. + 預期字串與指定的模式相符。