Skip to content

Commit 07df337

Browse files
authored
Localized file check-in by OneLocBuild Task: Build definition ID 1218: Build ID 2980844 (#8463)
1 parent 90e525f commit 07df337

14 files changed

Lines changed: 319 additions & 319 deletions

File tree

src/Analyzers/MSTest.Analyzers.CodeFixes/xlf/CodeFixResources.it.xlf

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,17 +24,17 @@
2424
</trans-unit>
2525
<trans-unit id="AvoidAssertAreEqualOnCollectionsEquivalentFix">
2626
<source>Replace with `Assert.{0}`</source>
27-
<target state="new">Replace with `Assert.{0}`</target>
27+
<target state="translated">Sostituire con `Assert.{0}`</target>
2828
<note />
2929
</trans-unit>
3030
<trans-unit id="AvoidAssertAreEqualOnCollectionsInAnyOrderFix">
3131
<source>Replace with `Assert.{0}(..., SequenceOrder.InAnyOrder)`</source>
32-
<target state="new">Replace with `Assert.{0}(..., SequenceOrder.InAnyOrder)`</target>
32+
<target state="translated">Sostituire con `Assert.{0}(..., SequenceOrder.InAnyOrder)`</target>
3333
<note />
3434
</trans-unit>
3535
<trans-unit id="AvoidAssertAreEqualOnCollectionsOrderedFix">
3636
<source>Replace with `Assert.{0}` (ordered)</source>
37-
<target state="new">Replace with `Assert.{0}` (ordered)</target>
37+
<target state="translated">Sostituire con `Assert.{0}` (ordinato)</target>
3838
<note />
3939
</trans-unit>
4040
<trans-unit id="AvoidAssertAreSameWithValueTypesFix">
@@ -54,7 +54,7 @@
5454
</trans-unit>
5555
<trans-unit id="AvoidUsingAssertsInAsyncVoidContextFix">
5656
<source>Change return type to 'Task'</source>
57-
<target state="new">Change return type to 'Task'</target>
57+
<target state="translated">Cambia tipo restituito in ''Task''</target>
5858
<note />
5959
</trans-unit>
6060
<trans-unit id="ChangeMethodAccessibilityToPrivateFix">
@@ -159,7 +159,7 @@
159159
</trans-unit>
160160
<trans-unit id="UseAsyncAssertionFix">
161161
<source>Use async assertion</source>
162-
<target state="new">Use async assertion</target>
162+
<target state="translated">Usare un'asserzione asincrona</target>
163163
<note />
164164
</trans-unit>
165165
<trans-unit id="UseAttributeOnTestMethodFix">

src/Analyzers/MSTest.Analyzers/xlf/Resources.it.xlf

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,17 +119,17 @@ Anche il tipo che dichiara questi metodi deve rispettare le regole seguenti:
119119
</trans-unit>
120120
<trans-unit id="AvoidAssertAreEqualOnCollectionsDescription">
121121
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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-
<target state="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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+
<target state="translated">`Assert.AreEqual` e `Assert.AreNotEqual` usano `EqualityComparer&lt;T&gt;.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>
123123
<note />
124124
</trans-unit>
125125
<trans-unit id="AvoidAssertAreEqualOnCollectionsMessageFormat">
126126
<source>`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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-
<target state="new">`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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+
<target state="translated">`{0}` in {1} (che implementa IEnumerable&lt;T&gt;) 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>
128128
<note />
129129
</trans-unit>
130130
<trans-unit id="AvoidAssertAreEqualOnCollectionsTitle">
131131
<source>Avoid Assert.AreEqual on collection types</source>
132-
<target state="new">Avoid Assert.AreEqual on collection types</target>
132+
<target state="translated">Evitare Assert.AreEqual sui tipi di raccolta</target>
133133
<note />
134134
</trans-unit>
135135
<trans-unit id="AvoidAssertAreSameWithValueTypesDescription">
@@ -549,17 +549,17 @@ Anche il tipo che dichiara questi metodi deve rispettare le regole seguenti:
549549
</trans-unit>
550550
<trans-unit id="PreferAsyncAssertionDescription">
551551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552-
<target state="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552+
<target state="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>
553553
<note />
554554
</trans-unit>
555555
<trans-unit id="PreferAsyncAssertionMessageFormat">
556556
<source>Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</source>
557-
<target state="new">Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</target>
557+
<target state="translated">Usare ''Assert''.{0}invece di bloccare una chiamata asincrona in ''Assert''.{1}</target>
558558
<note />
559559
</trans-unit>
560560
<trans-unit id="PreferAsyncAssertionTitle">
561561
<source>Prefer async assertion methods</source>
562-
<target state="new">Prefer async assertion methods</target>
562+
<target state="translated">Preferire i metodi asincroni di asserzione</target>
563563
<note />
564564
</trans-unit>
565565
<trans-unit id="PreferTestMethodOverDataTestMethodAnalyzerDescription">

src/Analyzers/MSTest.Analyzers/xlf/Resources.pl.xlf

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,17 +119,17 @@ Typ deklarujący te metody powinien również przestrzegać następujących regu
119119
</trans-unit>
120120
<trans-unit id="AvoidAssertAreEqualOnCollectionsDescription">
121121
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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-
<target state="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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+
<target state="translated">Elementy `Assert.AreEqual` i `Assert.AreNotEqual` używają elementu `EqualityComparer&lt;T&gt;.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>
123123
<note />
124124
</trans-unit>
125125
<trans-unit id="AvoidAssertAreEqualOnCollectionsMessageFormat">
126126
<source>`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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-
<target state="new">`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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+
<target state="translated">`{0}` na {1} (który implementuje IEnumerable&lt;T&gt;) 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>
128128
<note />
129129
</trans-unit>
130130
<trans-unit id="AvoidAssertAreEqualOnCollectionsTitle">
131131
<source>Avoid Assert.AreEqual on collection types</source>
132-
<target state="new">Avoid Assert.AreEqual on collection types</target>
132+
<target state="translated">Unikaj metody Assert.AreEqual w przypadku typów kolekcji</target>
133133
<note />
134134
</trans-unit>
135135
<trans-unit id="AvoidAssertAreSameWithValueTypesDescription">
@@ -549,17 +549,17 @@ Typ deklarujący te metody powinien również przestrzegać następujących regu
549549
</trans-unit>
550550
<trans-unit id="PreferAsyncAssertionDescription">
551551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552-
<target state="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552+
<target state="translated">Podczas weryfikowania wyjątków z kodu asynchronicznego użyj metod asercji asynchronicznej, zamiast blokować operację asynchroniczną za pomocą metody GetAwaiter().GetResult().</target>
553553
<note />
554554
</trans-unit>
555555
<trans-unit id="PreferAsyncAssertionMessageFormat">
556556
<source>Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</source>
557-
<target state="new">Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</target>
557+
<target state="translated">Użyj instrukcji „Assert.{0}” zamiast blokować wywołanie asynchroniczne w elemencie „Assert".{1}</target>
558558
<note />
559559
</trans-unit>
560560
<trans-unit id="PreferAsyncAssertionTitle">
561561
<source>Prefer async assertion methods</source>
562-
<target state="new">Prefer async assertion methods</target>
562+
<target state="translated">Preferuj metody asercji asynchronicznych</target>
563563
<note />
564564
</trans-unit>
565565
<trans-unit id="PreferTestMethodOverDataTestMethodAnalyzerDescription">

src/Analyzers/MSTest.Analyzers/xlf/Resources.tr.xlf

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,17 +119,17 @@ Bu yöntemleri bildiren tipin ayrıca aşağıdaki kurallara uyması gerekir:
119119
</trans-unit>
120120
<trans-unit id="AvoidAssertAreEqualOnCollectionsDescription">
121121
<source>`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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-
<target state="new">`Assert.AreEqual` and `Assert.AreNotEqual` use `EqualityComparer&lt;T&gt;.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+
<target state="translated">`Assert.AreEqual` ve `Assert.AreNotEqual`, `EqualityComparer&lt;T&gt;.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>
123123
<note />
124124
</trans-unit>
125125
<trans-unit id="AvoidAssertAreEqualOnCollectionsMessageFormat">
126126
<source>`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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-
<target state="new">`{0}` on {1} (which implements IEnumerable&lt;T&gt;) 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+
<target state="translated">`{0}` üzerinde {1} (IEnumerable&lt;T&gt; 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>
128128
<note />
129129
</trans-unit>
130130
<trans-unit id="AvoidAssertAreEqualOnCollectionsTitle">
131131
<source>Avoid Assert.AreEqual on collection types</source>
132-
<target state="new">Avoid Assert.AreEqual on collection types</target>
132+
<target state="translated">Koleksiyon türleri için Assert.AreEqual kullanmaktan kaçının</target>
133133
<note />
134134
</trans-unit>
135135
<trans-unit id="AvoidAssertAreSameWithValueTypesDescription">
@@ -549,17 +549,17 @@ Bu metotları bildiren türün ayrıca aşağıdaki kurallara uyması gerekir:
549549
</trans-unit>
550550
<trans-unit id="PreferAsyncAssertionDescription">
551551
<source>When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</source>
552-
<target state="new">When verifying exceptions from asynchronous code, use the async assertion methods instead of blocking the asynchronous operation with GetAwaiter().GetResult().</target>
552+
<target state="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>
553553
<note />
554554
</trans-unit>
555555
<trans-unit id="PreferAsyncAssertionMessageFormat">
556556
<source>Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</source>
557-
<target state="new">Use 'Assert.{0}' instead of blocking an async call in 'Assert.{1}'</target>
557+
<target state="translated">'Assert.{0}' içinde zaman uyumsuz bir çağrıyı engellemek yerine 'Assert.{1}' kullanın</target>
558558
<note />
559559
</trans-unit>
560560
<trans-unit id="PreferAsyncAssertionTitle">
561561
<source>Prefer async assertion methods</source>
562-
<target state="new">Prefer async assertion methods</target>
562+
<target state="translated">Zaman uyumsuz doğrulama yöntemlerini tercih edin</target>
563563
<note />
564564
</trans-unit>
565565
<trans-unit id="PreferTestMethodOverDataTestMethodAnalyzerDescription">

src/Platform/Microsoft.Testing.Extensions.AzureDevOpsReport/Resources/xlf/AzureDevOpsResources.it.xlf

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@
119119
</trans-unit>
120120
<trans-unit id="FlakyHistoryFailureAnnotation">
121121
<source>[flaky: failed {0}/{1} in last {2}d]</source>
122-
<target state="new">[flaky: failed {0}/{1} in last {2}d]</target>
122+
<target state="translated">[flaky: failed {0}/{1} in last {2}d]</target>
123123
<note>{Locked="[flaky: failed {0}/{1} in last {2}d]"}</note>
124124
</trans-unit>
125125
<trans-unit id="FlakyHistoryLoadFailedWarning">
@@ -144,7 +144,7 @@
144144
</trans-unit>
145145
<trans-unit id="FlakyHistoryRegressionAnnotation">
146146
<source>[REGRESSION]</source>
147-
<target state="new">[REGRESSION]</target>
147+
<target state="translated">[REGRESSION]</target>
148148
<note>{Locked="[REGRESSION]"}</note>
149149
</trans-unit>
150150
<trans-unit id="FlakyHistoryResultsPagingStoppedWarning">
@@ -224,7 +224,7 @@
224224
</trans-unit>
225225
<trans-unit id="QuarantinedAnnotation">
226226
<source>[quarantined]</source>
227-
<target state="new">[quarantined]</target>
227+
<target state="translated">[quarantined]</target>
228228
<note>{Locked="[quarantined]"}</note>
229229
</trans-unit>
230230
<trans-unit id="SeverityOptionDescription">

0 commit comments

Comments
 (0)