You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</source>
122
-
<targetstate="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</target>
122
+
<targetstate="translated">`Assert.AreEqual` e `Assert.AreNotEqual` usano `EqualityComparer<T>.Default`. Per i tipi simili a una raccolta, si basa sulla semantica di uguaglianza del tipo invece di confrontare gli elementi di sequenza, quindi `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` o `Assert.AreEquivalent`/`Assert.AreNotEquivalent` sono in genere la soluzione migliore.</target>
<source>`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</source>
127
-
<targetstate="new">`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</target>
127
+
<targetstate="translated">`{0}` in {1} (che implementa IEnumerable<T>) non esegue un confronto tra sequenze elemento per elemento. Usare `Assert.AreSequenceEqual` per il confronto ordinato a livello di elemento, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` per un confronto non ordinato o `Assert.AreEquivalent` per un confronto strutturale approfondito.</target>
@@ -549,17 +549,17 @@ Anche il tipo che dichiara questi metodi deve rispettare le regole seguenti:
549
549
</trans-unit>
550
550
<trans-unitid="PreferAsyncAssertionDescription">
551
551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552
-
<targetstate="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552
+
<targetstate="translated">Quando si verificano le eccezioni dal codice asincrono, usare i metodi di asserzione asincrona invece di bloccare l'operazione asincrona con GetXhtmliter().GetResult().</target>
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</source>
122
-
<targetstate="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</target>
122
+
<targetstate="translated">Elementy `Assert.AreEqual` i `Assert.AreNotEqual` używają elementu `EqualityComparer<T>.Default`. W przypadku typów przypominających kolekcję jest to oparte na semantyce równości typu zamiast porównywania elementów sekwencji, więc lepszym rozwiązaniem jest `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` lub `Assert.AreEquivalent`/`Assert.AreNotEquivalent`.</target>
<source>`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</source>
127
-
<targetstate="new">`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</target>
127
+
<targetstate="translated">`{0}` na {1} (który implementuje IEnumerable<T>) nie wykonuje porównania sekwencji z elementami. Użyj opcji `Assert.AreSequenceEqual` dla uporządkowanego porównania z elementami, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` dla nieuporządkowanego lub `Assert.AreEquivalent`, aby uzyskać głębokie porównanie strukturalne.</target>
@@ -549,17 +549,17 @@ Typ deklarujący te metody powinien również przestrzegać następujących regu
549
549
</trans-unit>
550
550
<trans-unitid="PreferAsyncAssertionDescription">
551
551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552
-
<targetstate="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552
+
<targetstate="translated">Podczas weryfikowania wyjątków z kodu asynchronicznego użyj metod asercji asynchronicznej, zamiast blokować operację asynchroniczną za pomocą metody GetAwaiter().GetResult().</target>
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</source>
122
-
<targetstate="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer<T>.Default`. For collection-like types this relies on the type's own equality semantics instead of comparing sequence elements, so `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` or `Assert.AreEquivalent`/`Assert.AreNotEquivalent` are usually the better fit.</target>
122
+
<targetstate="translated">`Assert.AreEqual` ve `Assert.AreNotEqual`, `EqualityComparer<T>.Default` kullanır. Koleksiyon benzeri türlerde bu, dizi öğelerini karşılaştırmak yerine türün kendi eşitlik semantiğine dayanır. Bu nedenle genellikle `Assert.AreSequenceEqual`/`Assert.AreNotSequenceEqual` ya da `Assert.AreEquivalent`/`Assert.AreNotEquivalent` daha uygundur.</target>
<source>`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</source>
127
-
<targetstate="new">`{0}` on {1} (which implements IEnumerable<T>) does not perform element-wise sequence comparison. Use `Assert.AreSequenceEqual` for ordered element-wise comparison, `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` for unordered, or `Assert.AreEquivalent` for deep structural comparison.</target>
127
+
<targetstate="translated">`{0}` üzerinde {1} (IEnumerable<T> uygulayan) öğe bazında dizi karşılaştırması yapmaz. Sıralı öğe bazında karşılaştırma için `Assert.AreSequenceEqual`, sırasız karşılaştırma için `Assert.AreSequenceEqual(..., SequenceOrder.InAnyOrder)` ya da derin yapısal karşılaştırma için `Assert.AreEquivalent` kullanın.</target>
@@ -549,17 +549,17 @@ Bu metotları bildiren türün ayrıca aşağıdaki kurallara uyması gerekir:
549
549
</trans-unit>
550
550
<trans-unitid="PreferAsyncAssertionDescription">
551
551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552
-
<targetstate="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552
+
<targetstate="translated">Zaman uyumsuz koddan gelen özel durumları doğrularken GetAwaiter().GetResult() ile zaman uyumsuz işlemi engellemek yerine zaman uyumsuz onaylama yöntemlerini kullanın.</target>
0 commit comments