From 56b87f0d49dbfae4b3b781957bcf3645455a530b Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Mon, 10 Nov 2025 20:35:45 -0800 Subject: [PATCH 1/3] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2835857 --- src/Analyzers/MSTest.Analyzers/xlf/Resources.cs.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.ko.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf | 6 +++--- src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf | 6 +++--- 8 files changed, 24 insertions(+), 24 deletions(-) diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.cs.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.cs.xlf index b7b156acca..a416844e86 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.cs.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.cs.xlf @@ -991,17 +991,17 @@ Typ deklarující tyto metody by měl také respektovat následující pravidla: Do not use asserts in catch blocks - Do not use asserts in catch blocks + Nepoužívat kontrolní výrazy v blocích catch Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + Nepoužívejte kontrolní výrazy v blocích catch, protože test nemusí selhat, pokud není vyvolána žádná výjimka. 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. - 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. + Používání kontrolních výrazů v blocích catch je problematické, protože test projde, i když se nevyvolá žádná výjimka a blok catch se nikdy nespustí. K ověření, že je vyvolána výjimka, použijte metody Assert.Throws, Assert.ThrowsExactly, Assert.ThrowsAsync nebo Assert.ThrowsExactlyAsync a poté proveďte další kontrolní výrazy nad zachycenou výjimkou bez použití bloku try-catch. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf index b5ad5d9582..34fe594c45 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.es.xlf @@ -991,17 +991,17 @@ El tipo que declara estos métodos también debe respetar las reglas siguientes: Do not use asserts in catch blocks - Do not use asserts in catch blocks + No use aserciones en bloques catch Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + No use aserciones en bloques catch porque es posible que no produzcan un error en la prueba si no se produce ninguna excepción 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. - 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. + 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 produzca una excepción y, a continuación, realice aserciones adicionales en la excepción detectada sin usar el bloque try-catch. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf index 143099764f..8e3595e788 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ja.xlf @@ -991,17 +991,17 @@ The type declaring these methods should also respect the following rules: Do not use asserts in catch blocks - Do not use asserts in catch blocks + catch ブロックでアサートを使用しないでください Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + 例外がスローされない場合、テストに失敗しない可能性があるため、catch ブロックでアサートを使用しないでください 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. - 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. + catch ブロックでアサートを使用すると、例外がスローされず、catch ブロックが実行されなくてもテストが成功するため、問題があります。'Assert.Throws'、'Assert.ThrowsExactly'、'Assert.ThrowsAsync'、または 'Assert.ThrowsExactlyAsync' を使用して例外がスローされたことを確認し、try-catch ブロックを使用せずにキャッチされた例外に対して追加のアサートを実行します。 diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ko.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ko.xlf index ba20940467..dfd7749d6f 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.ko.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.ko.xlf @@ -991,17 +991,17 @@ The type declaring these methods should also respect the following rules: Do not use asserts in catch blocks - Do not use asserts in catch blocks + catch 블록에서 어설션 사용 안 함 Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + 예외가 발생하지 않으면 테스트가 실패하지 않을 수 있으니 catch 블록에서 어설션을 사용하지 마세요. 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. - 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. + 예외가 발생하지 않고 catch 블록이 실행되지 않더라도 테스트가 통과하기 때문에 catch 블록에서 어설션을 사용하는 것은 문제가 됩니다. 'Assert.Throws', 'Assert.ThrowsExactly', 'Assert.ThrowsAsync' 또는 'Assert.ThrowsExactlyAsync'를 사용하여 예외가 발생했는지 확인한 다음 try-catch 블록을 사용하지 않고 catch된 예외에 대해 추가 어설션을 만듭니다. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf index 0cddbbe3a1..5351c55de2 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf @@ -991,17 +991,17 @@ Typ deklarujący te metody powinien również przestrzegać następujących regu Do not use asserts in catch blocks - Do not use asserts in catch blocks + Nie używaj asercji w blokach catch Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + Nie używaj asercji w blokach catch, ponieważ test może nie zakończyć się niepowodzeniem, jeśli nie zostanie zgłoszony żaden wyjątek 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. - 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. + Używanie asercji w blokach catch jest problematyczne, ponieważ test zakończy się powodzeniem, nawet jeśli nie zostanie zgłoszony żaden wyjątek i blok catch nigdy nie zostanie wykonany. Użyj instrukcji „Assert.Throws”, „Assert.ThrowsExactly”, „Assert.ThrowsAsync” lub „Assert.ThrowsExactlyAsync”, aby sprawdzić, czy zgłoszono wyjątek, a następnie wykonaj dodatkowe asercje dla przechwyconego wyjątku bez użycia bloku try-catch. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf index 455d4571c1..3836015abc 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.pt-BR.xlf @@ -991,17 +991,17 @@ O tipo que declara esses métodos também deve respeitar as seguintes regras: Do not use asserts in catch blocks - Do not use asserts in catch blocks + Não usar assertivas em blocos catch Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + Não use assertivas em blocos catch porque elas podem não falhar no teste se nenhuma exceção for lançada 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. - 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. + 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. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf index 8b5b8691a7..1042c81aea 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf @@ -993,17 +993,17 @@ Bu yöntemleri bildiren tipin ayrıca aşağıdaki kurallara uyması gerekir: Do not use asserts in catch blocks - Do not use asserts in catch blocks + Catch bloklarında assert kullanmayın Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + Catch bloklarında assert kullanmayın, çünkü özel durum atılmadığında test başarısız olmayabilir 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. - 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. + Catch bloklarında assert kullanmak sorunludur, çünkü özel durum atılmasa ve catch bloğu hiç çalıştırılmasa bile test geçecektir. Bir özel durumun atıldığını doğrulamak için ‘Assert.Throws’, ‘Assert.ThrowsExactly’, ‘Assert.ThrowsAsync’ veya ‘Assert.ThrowsExactlyAsync’ kullanın ve ardından try-catch bloğu kullanmadan yakalanan özel durum üzerinde ek doğrulamalar yapın. diff --git a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf index 2bea1eda8d..07a93414ca 100644 --- a/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf +++ b/src/Analyzers/MSTest.Analyzers/xlf/Resources.zh-Hans.xlf @@ -991,17 +991,17 @@ The type declaring these methods should also respect the following rules: Do not use asserts in catch blocks - Do not use asserts in catch blocks + 不要在 catch 块中使用断言 Do not use asserts in catch blocks because they may not fail the test if no exception is thrown - Do not use asserts in catch blocks because they may not fail the test if no exception is thrown + 不要在 catch 块中使用断言，因为如果没有引发异常，断言可能不会导致测试失败 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. - 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. + 在 catch 块中使用断言是有问题的，因为即使没有引发异常且 catch 块从未执行，测试也会通过。请使用 "Assert.Throws"、"Assert.ThrowsExactly"、"Assert.ThrowsAsync" 或 "Assert.ThrowsExactlyAsync" 来验证是否引发了异常，然后对捕获的异常进行额外断言，而无需使用 try-catch 块。 From 28eddbacf51931c5d85abb5919ffc92aa4d7461c Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Mon, 10 Nov 2025 20:40:11 -0800 Subject: [PATCH 2/3] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2835857 --- .../TestFramework/Resources/xlf/FrameworkMessages.es.xlf | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf index 9a8979cae4..125e04007a 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.es.xlf @@ -254,12 +254,12 @@ Real: {2} Value '{0}' is not within the expected range [{1}..{2}]. {3} - Value '{0}' is not within the expected range [{1}..{2}]. {3} + El valor "{0}" no está dentro del rango esperado [{1}..{2}]. {3} The maximum value must be greater than the minimum value. - The maximum value must be greater than the minimum value. + El valor máximo debe ser mayor que el valor mínimo. From be6780c451b4cb1d72f97f5baf00b44ec2dfa32a Mon Sep 17 00:00:00 2001 From: dotnet bot Date: Mon, 10 Nov 2025 20:40:51 -0800 Subject: [PATCH 3/3] Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2835857 --- .../TestFramework/Resources/xlf/FrameworkMessages.ko.xlf | 4 ++-- .../TestFramework/Resources/xlf/FrameworkMessages.pl.xlf | 4 ++-- .../TestFramework/Resources/xlf/FrameworkMessages.tr.xlf | 4 ++-- .../TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ko.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ko.xlf index 1a2547fd48..ae66824880 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ko.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.ko.xlf @@ -254,12 +254,12 @@ Actual: {2} Value '{0}' is not within the expected range [{1}..{2}]. {3} - Value '{0}' is not within the expected range [{1}..{2}]. {3} + '{0}' 값이 예상 범위 [{1}..{2}] 내에 있지 않습니다. {3} The maximum value must be greater than the minimum value. - The maximum value must be greater than the minimum value. + 최댓값은 최솟값보다 커야 합니다. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pl.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pl.xlf index 7bec7e8034..eda93267c7 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pl.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.pl.xlf @@ -254,12 +254,12 @@ Rzeczywiste: {2} Value '{0}' is not within the expected range [{1}..{2}]. {3} - Value '{0}' is not within the expected range [{1}..{2}]. {3} + Wartość „{0}” nie mieści się w oczekiwanym zakresie [{1}..{2}]. {3} The maximum value must be greater than the minimum value. - The maximum value must be greater than the minimum value. + Wartość maksymalna musi być większa niż wartość minimalna. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.tr.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.tr.xlf index 2aeaeb6d11..f225e01eb7 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.tr.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.tr.xlf @@ -254,12 +254,12 @@ Gerçekte olan: {2} Value '{0}' is not within the expected range [{1}..{2}]. {3} - Value '{0}' is not within the expected range [{1}..{2}]. {3} + Değer '{0}' beklenen aralık [{1}..{2}] içinde değil. {3} The maximum value must be greater than the minimum value. - The maximum value must be greater than the minimum value. + En yüksek değer, en düşük değerden büyük olmalıdır. diff --git a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf index 0e3a939d7d..b9e8438e79 100644 --- a/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf +++ b/src/TestFramework/TestFramework/Resources/xlf/FrameworkMessages.zh-Hans.xlf @@ -254,12 +254,12 @@ Actual: {2} Value '{0}' is not within the expected range [{1}..{2}]. {3} - Value '{0}' is not within the expected range [{1}..{2}]. {3} + 值 "{0}" 不在预期范围 [{1}..{2}] 内。{3} The maximum value must be greater than the minimum value. - The maximum value must be greater than the minimum value. + 最大值必须大于最小值。