forked from microsoft/vstest
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Resources.zh-Hant.xlf
1244 lines (1218 loc) · 72 KB
/
Resources.zh-Hant.xlf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
<file datatype="xml" source-language="en" original="../Resources.resx" target-language="zh-Hant">
<body>
<trans-unit id="FileNotFound">
<source>'{0}' not found.</source>
<note></note>
<target state="translated">找不到 '{0}'。</target>
</trans-unit>
<trans-unit id="AvailableDiscoverersHeaderMessage">
<source>The following Test Discovery Add-Ins are available:</source>
<note></note>
<target state="translated">可使用下列測試探索增益集:</target>
</trans-unit>
<trans-unit id="AvailableExecutorsHeaderMessage">
<source>The following Test Execution Add-Ins are available:</source>
<note></note>
<target state="translated">可使用下列測試執行增益集:</target>
</trans-unit>
<trans-unit id="AvailableExtensionFormat">
<source> {0}</source>
<note>{Locked}</note>
<target state="new"> {0}</target>
</trans-unit>
<trans-unit id="AvailableExtensionsMetadataFormat">
<source> {0}: {1}</source>
<note></note>
<target state="translated"> {0}: {1}</target>
</trans-unit>
<trans-unit id="AvailableLoggersHeaderMessage">
<source>The following Test Logger Add-Ins are available:</source>
<note></note>
<target state="translated">可使用下列測試記錄器增益集:</target>
</trans-unit>
<trans-unit id="AvailableTestsFormat">
<source> {0}</source>
<note>{Locked}</note>
<target state="new"> {0}</target>
</trans-unit>
<trans-unit id="CommandLineError">
<source>Error: {0}</source>
<note></note>
<target state="translated">錯誤: {0}</target>
</trans-unit>
<trans-unit id="CommaSeparatedFormat">
<source>, {0}</source>
<note>Format used to comma separate a list of values.</note>
<target state="translated">，{0}</target>
</trans-unit>
<trans-unit id="DuplicateArgumentError">
<source>The parameter "{0}" should be provided only once.</source>
<note></note>
<target state="translated">參數 " {0}" 應該僅提供一次。</target>
</trans-unit>
<trans-unit id="ExceptionFromExtension">
<source>Exception occurred when instantiating extension '{0}': {1}</source>
<note></note>
<target state="translated">產生延伸模組時發生例外狀況 '{0}': {1}</target>
</trans-unit>
<trans-unit id="ListTestsHeaderMessage">
<source>The following Tests are available:</source>
<note></note>
<target state="translated">可使用下列測試:</target>
</trans-unit>
<trans-unit id="NoArgumentProcessorFound">
<source>Unrecognized parameter "{0}".</source>
<note></note>
<target state="translated">無法辨識的參數 "{0}"。</target>
</trans-unit>
<trans-unit id="TestSourceFileNotFound">
<source>The test source file "{0}" provided was not found.</source>
<note></note>
<target state="translated">找不到提供的測試來源檔案 "{0}"。</target>
</trans-unit>
<trans-unit id="LoggerUriInvalid">
<source>The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.</source>
<note></note>
<target state="translated">測試記錄器 URI '{0}' 無效。將忽略測試記錄器。</target>
</trans-unit>
<trans-unit id="CommandLineInformational">
<source>Information: {0}</source>
<note></note>
<target state="translated">資訊: {0}</target>
</trans-unit>
<trans-unit id="CommandLineWarning">
<source>Warning: {0}</source>
<note></note>
<target state="translated">警告: {0}</target>
</trans-unit>
<trans-unit id="HelpArgumentHelp">
<source>-?|--Help|/?|/Help
Display this usage message.</source>
<note></note>
<target state="translated">-?|--Help|/?|/Help
顯示此使用方式訊息。</target>
</trans-unit>
<trans-unit id="CopyrightCommandLineTitle">
<source>Copyright (c) Microsoft Corporation. All rights reserved.</source>
<note></note>
<target state="translated">Copyright (C) Microsoft Corporation. 著作權所有，並保留一切權利。</target>
</trans-unit>
<trans-unit id="MicrosoftCommandLineTitle">
<source>Microsoft (R) Test Execution Command Line Tool Version {0}</source>
<note></note>
<target state="translated">Microsoft (R) Test Execution Command Line Tool {0} 版</target>
</trans-unit>
<trans-unit id="EnableLoggersArgumentHelp">
<source>--logger|/logger:<Logger Uri/FriendlyName>
Specify a logger for test results. For example, to log results into a
Visual Studio Test Results File (TRX) use /logger:trx[;LogFileName=<Defaults to unique file name>]
Creates file in TestResults directory with given LogFileName.
Change the verbosity level in log messages for console logger as shown below
Example: /logger:console;verbosity=<Defaults to "normal">
Allowed values for verbosity: quiet, minimal, normal and detailed.
Change the diagnostic level prefix for console logger as shown below
Example: /logger:console;prefix=<Defaults to "false">
More info on Console Logger here : https://aka.ms/console-logger</source>
<note></note>
<target state="translated">--logger|/logger:<記錄器 URI/易記名稱>
指定測試結果的記錄器。例如，使用 /logger:trx[;LogFileName=<預設為唯一的檔案名稱>]，
將結果記錄至 Visual Studio 測試結果檔案 (TRX)
以指定的 LogFileName，在 TestResults 目錄中建立檔案。
變更主控台記錄器的記錄訊息詳細程度等級，如下所示
範例: /logger:console;verbosity=<預設為 "normal">
詳細程度的允許值: quiet、minimal、normal 以及 detailed。
變更主控台記錄器的診斷等級前置詞，如下所示
範例: /logger:console;prefix=<預設為 "false">
主控台記錄器詳細資訊於此: https://aka.ms/console-logger</target>
</trans-unit>
<trans-unit id="HelpDescriptionText">
<source>Description: Runs tests from the specified files.</source>
<note></note>
<target state="translated">描述: 從指定的檔案執行測試。</target>
</trans-unit>
<trans-unit id="HelpOptionsText">
<source>Options:</source>
<note>Section Header for subsequent command help listing</note>
<target state="translated">選項:</target>
</trans-unit>
<trans-unit id="HelpUsageText">
<source>Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]]</source>
<note></note>
<target state="translated">用法: vstest.console.exe [引數] [選項] [[--] <RunSettings 引數>...]]</target>
</trans-unit>
<trans-unit id="MissingTestSourceFile">
<source>No test source files were specified.</source>
<note></note>
<target state="translated">未指定測試來源檔案。</target>
</trans-unit>
<trans-unit id="NoArgumentsProvided">
<source>No arguments were specified.</source>
<note></note>
<target state="translated">未指定引數。</target>
</trans-unit>
<trans-unit id="RunTestsArgumentHelp">
<source>[TestFileNames]
Run tests from the specified files or wild card pattern. Separate multiple test file names or pattern
by spaces. Set console logger verbosity to detailed to view matched test files.
Examples: mytestproject.dll
mytestproject.dll myothertestproject.exe
testproject*.dll my*project.dll</source>
<note></note>
<target state="translated">[TestFileNames]
從指定的檔案或萬用字元模式執行測試。分隔多個測試檔名稱或模式
由空格分隔。將主控台記錄器詳細程度設定為詳細來檢視符合的測試檔案。
範例: mytestproject.dll
mytestproject.dll myothertestproject.exe
testproject*.dll my*project.dll</target>
</trans-unit>
<trans-unit id="AvailableSettingsProvidersHeaderMessage">
<source>The following Settings Providers Add-Ins are available:</source>
<note></note>
<target state="translated">可使用下列設定提供者增益集:</target>
</trans-unit>
<trans-unit id="RunSettingsArgumentHelp">
<source>--Settings|/Settings:<Settings File>
Settings to use when running tests.</source>
<note></note>
<target state="translated">--Settings|/Settings:<設定檔>
執行測試時要使用的設定。</target>
</trans-unit>
<trans-unit id="RunSettingsRequired">
<source>The /Settings parameter requires a settings file to be provided.</source>
<note></note>
<target state="translated">/Settings 參數要求必須提供設定檔。</target>
</trans-unit>
<trans-unit id="RunSettingsFileNotFound">
<source>The Settings file '{0}' could not be found.</source>
<note></note>
<target state="translated">找不到設定檔 '{0}'。</target>
</trans-unit>
<trans-unit id="TestRunFailed">
<source>Test Run Failed.</source>
<note></note>
<target state="translated">測試回合失敗。</target>
</trans-unit>
<trans-unit id="TestRunSuccessful">
<source>Test Run Successful.</source>
<note></note>
<target state="translated">測試回合成功。</target>
</trans-unit>
<trans-unit id="InvalidInIsolationCommand">
<source>Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again.</source>
<note></note>
<target state="translated">'InIsolation' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /InIsolation)，並再試一次。</target>
</trans-unit>
<trans-unit id="UseVsixExtensionsValueRequired">
<source>The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true</source>
<note></note>
<target state="translated">/UseVsixExtensions 參數需要一個值。如果為 'true'，已安裝的 VSIX 延伸模組 (如果有的話) 將用於測試回合。如果為 false，則會加以忽略。範例: /UseVsixExtensions:true</target>
</trans-unit>
<trans-unit id="InvalidUseVsixExtensionsCommand">
<source>Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again.</source>
<note></note>
<target state="translated">'UseVsixExtensions' 命令中不應該使用引數 {0}。請指定命令指出應該使用或略過 VSIX 延伸模組 (範例: vstest.console.exe myTests.dll /UseVsixExtensions:true) 並再試一次。</target>
</trans-unit>
<trans-unit id="InIsolationHelp">
<source>--InIsolation|/InIsolation
Runs the tests in an isolated process. This makes vstest.console.exe
process less likely to be stopped on an error in the tests, but tests
may run slower.</source>
<note></note>
<target state="translated">--InIsolation|/InIsolation
在隔離的處理序中執行測試。這樣會降低 vstest.console.exe
處理序在測試中發生錯誤而停止的可能性，但是測試
可能會執行得較慢。</target>
</trans-unit>
<trans-unit id="UseVsixExtensionsHelp">
<source>/UseVsixExtensions
This makes vstest.console.exe process use or skip the VSIX extensions
installed(if any) in the test run.
Example /UseVsixExtensions:true</source>
<note></note>
<target state="translated">/UseVsixExtensions
這可讓 vstest.console.exe 處理序使用或略過測試回合中
已安裝的 VSIX 延伸模組 (如果有的話)。
範例 /UseVsixExtensions:true</target>
</trans-unit>
<trans-unit id="BatchSizeRequired">
<source>The /BatchSize argument requires the size of the batch. Example: /BatchSize:10</source>
<note></note>
<target state="translated">/BatchSize 引數必須有批次的大小。範例: /BatchSize:10</target>
</trans-unit>
<trans-unit id="InvalidBatchSize">
<source>Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10</source>
<note></note>
<target state="translated">批次大小無效 {0}。批次大小應該大於零。範例: /BatchSize:10</target>
</trans-unit>
<trans-unit id="Examples">
<source> To run tests:
>vstest.console.exe tests.dll
To run tests with additional settings such as data collectors:
>vstest.console.exe tests.dll /Settings:Local.RunSettings</source>
<note></note>
<target state="translated"> 執行測試:
>vstest.console.exe tests.dll
執行測試，同時附上像是資料收集器等其他設定:
>vstest.console.exe tests.dll /Settings:Local.RunSettings</target>
</trans-unit>
<trans-unit id="ListDiscoverersHelp">
<source>/ListDiscoverers
Lists installed test discoverers.</source>
<note></note>
<target state="translated">/ListDiscoverers
列出已安裝的測試探索程式。</target>
</trans-unit>
<trans-unit id="ListExecutorsHelp">
<source>/ListExecutors
Lists installed test executors.</source>
<note></note>
<target state="translated">/ListExecutors
列出已安裝的測試執行程式。</target>
</trans-unit>
<trans-unit id="ListLoggersHelp">
<source>/ListLoggers
Lists installed test loggers.</source>
<note></note>
<target state="translated">/ListLoggers
列出已安裝的測試記錄器。</target>
</trans-unit>
<trans-unit id="ListSettingsProvidersHelp">
<source>/ListSettingsProviders
Lists installed test settings providers.</source>
<note></note>
<target state="translated">/ListSettingsProviders
列出已安裝的測試設定提供者。</target>
</trans-unit>
<trans-unit id="ListTestsHelp">
<source>-lt|--ListTests|/lt|/ListTests:<File Name>
Lists all discovered tests from the given test container.</source>
<note></note>
<target state="translated">-lt|--ListTests|/lt|/ListTests:<檔案名稱>
列出所有從指定測試容器探索到的測試。</target>
</trans-unit>
<trans-unit id="TimeElapsed">
<source>Time elapsed :</source>
<note></note>
<target state="translated">經過時間:</target>
</trans-unit>
<trans-unit id="SpecificTestsRequired">
<source>The /Tests argument requires one or more specific test names or their substrings.
Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 </source>
<note></note>
<target state="translated">/Tests 引數必須有一或多個特定的測試名稱或它們的子字串。
範例: /Tests:TestsMethod1, /Tests:TestMethod1,method2 </target>
</trans-unit>
<trans-unit id="NoTestsAvailableAfterFiltering">
<source>A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again.</source>
<note></note>
<target state="translated">已探索到總計 {0} 個測試，但沒有測試符合指定的選取準則 ({1})。請使用正確的值，並再試一次。</target>
</trans-unit>
<trans-unit id="SearchStringDelimiter">
<source>,</source>
<note></note>
<target state="translated">，</target>
</trans-unit>
<trans-unit id="RunSpecificTestsHelp">
<source>--Tests|/Tests:<Test Names>
Run tests with names that match the provided values. To provide multiple
values, separate them by commas.
Examples: /Tests:TestMethod1
/Tests:TestMethod1,testMethod2</source>
<note>Please verify if the console output looks good after modifiaction. </note>
<target state="translated">--Tests|/Tests:<測試名稱>
對名稱符合所提供值的項目執行測試。
若要提供多個值，請使用逗號將其分隔。
範例: /Tests:TestMethod1
/Tests:TestMethod1,testMethod2</target>
</trans-unit>
<trans-unit id="SwitchToNoIsolation">
<source>Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning.</source>
<note></note>
<target state="translated">使用隔離模式執行測試，因為在 runsettings 中已啟用診斷資料配接器。使用 /inIsolation 參數可隱藏這個警告。</target>
</trans-unit>
<trans-unit id="SwitchToIsolationInAppContainerMode">
<source>Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning.</source>
<note></note>
<target state="translated">使用隔離模式執行 Windows 市集應用程式的單元測試。使用 /InIsolation 參數可隱藏這個警告。</target>
</trans-unit>
<trans-unit id="DisablingDataCollectionInAppContainerTestExecution">
<source>Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings.</source>
<note></note>
<target state="translated">執行 Windows 市集應用程式的單元測試時，不支援診斷資料配接器。請從設定中移除診斷資料配接器設定。</target>
</trans-unit>
<trans-unit id="LoggerFriendlyNameFormat">
<source> FriendlyName: {0}</source>
<note></note>
<target state="translated"> FriendlyName: {0}</target>
</trans-unit>
<trans-unit id="ExtensionUriFormat">
<source> Uri: {0}</source>
<note></note>
<target state="translated"> URI: {0}</target>
</trans-unit>
<trans-unit id="SettingFormat">
<source> SettingName: {0}</source>
<note></note>
<target state="translated"> SettingName: {0}</target>
</trans-unit>
<trans-unit id="SupportedFileTypesIndicator">
<source> Supported File Types:</source>
<note></note>
<target state="translated"> 支援的檔案類型:</target>
</trans-unit>
<trans-unit id="SupportedFileWithoutSeparator">
<source> {0}</source>
<note></note>
<target state="translated"> {0}</target>
</trans-unit>
<trans-unit id="SupportedFileWithSeparator">
<source> {0},</source>
<note></note>
<target state="translated"> {0}，</target>
</trans-unit>
<trans-unit id="UriOfDefaultExecutor">
<source> Default Executor Uri: {0}</source>
<note></note>
<target state="translated"> 預設執行程式 URI: {0}</target>
</trans-unit>
<trans-unit id="LoggerUriFormat">
<source> Uri: {0}</source>
<note></note>
<target state="translated"> URI: {0}</target>
</trans-unit>
<trans-unit id="InvalidPlatformType">
<source>Invalid platform type: {0}. Valid platform types are {1}.</source>
<note>0 is the platform type e.g. x86, and 1 is a list of the built in platforms, e.g. x86, x64</note>
<target state="translated">平台類型無效: {0}。有效的平台類型為{1}。</target>
</trans-unit>
<trans-unit id="PlatformTypeRequired">
<source>The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86</source>
<note></note>
<target state="translated">/Platform 引數需要提供測試回合的目標平台類型。範例: /Platform:x86</target>
</trans-unit>
<trans-unit id="PlatformArgumentHelp">
<source>--Platform|/Platform:<Platform type>
Target platform architecture to be used for test execution.
Valid values are x86, x64 and ARM.</source>
<note></note>
<target state="translated">--Platform|/Platform:<平台類型>
用於測試執行的目標平台架構。
有效值為 x86、x64 和 ARM。</target>
</trans-unit>
<trans-unit id="SwitchToIsolationInMultiTargetingMode">
<source>Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning.</source>
<note></note>
<target state="translated">依照測試回合的有效平台 {0} 和 .Net Framework {1} 設定的要求，使用隔離模式執行測試。使用 /inIsolation 參數可隱藏這個警告。</target>
</trans-unit>
<trans-unit id="FrameworkArgumentHelp">
<source>--Framework|/Framework:<Framework Version>
Target .Net Framework version to be used for test execution.
Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc.
Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10.</source>
<note></note>
<target state="translated">--Framework|/Framework:<Framework 版本>
用於測試執行的目標.Net Framework 版本。
有效的值為 ".NETFramework,Version=v4.5.1"、".NETCoreApp,Version=v1.0" 等等。
其他支援的值為 Framework40、Framework45、FrameworkCore10 與 FrameworkUap10。</target>
</trans-unit>
<trans-unit id="FrameworkVersionRequired">
<source>The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1"</source>
<note></note>
<target state="translated">/Framework 引數需要測試回合的目標 .NET Framework 版本。 範例: /Framework:".NETFramework,Version=v4.5.1"</target>
</trans-unit>
<trans-unit id="InvalidFrameworkVersion">
<source>Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10.</source>
<note></note>
<target state="translated">.Net Framework 版本無效:{0}。請提供 TargetFramework 的全名 (例如: .NETCoreApp,Version=v2.0)。其他支援的 .Net Framework 版本為 Framework40、Framework45、FrameworkCore10 以及 FrameworkUap10。</target>
</trans-unit>
<trans-unit id="AppContainerTestPrerequisiteFail">
<source>Could not start test run for unit tests for Windows Store app: {0}.</source>
<note></note>
<target state="translated">無法針對 Windows 市集應用程式的單元測試啟動測試回合: {0}。</target>
</trans-unit>
<trans-unit id="TestCaseFilterArgumentHelp">
<source>--TestCaseFilter|/TestCaseFilter:<Expression>
Run tests that match the given expression.
<Expression> is of the format <property>Operator<value>[|&<Expression>]
where Operator is one of =, != or ~ (Operator ~ has 'contains'
semantics and is applicable for string properties like DisplayName).
Parenthesis () can be used to group sub-expressions.
Examples: /TestCaseFilter:"Priority=1"
/TestCaseFilter:"(FullyQualifiedName~Nightly
|Name=MyTestMethod)"</source>
<note></note>
<target state="translated">--TestCaseFilter|/TestCaseFilter:<Expression>
執行符合指定運算式的測試。
<Expression> 的格式為 <property>Operator<value>[|&<Expression>]
其中 Operator 是 =、!= 或 ~ 的其中之一 (運算子 ~ 具有 'contains'
語意，且適用於 DisplayName 之類的字串屬性)。
您可以使用括號 () 來分組子運算式。
範例: /TestCaseFilter:"Priority=1"
/TestCaseFilter:"(FullyQualifiedName~Nightly
|Name=MyTestMethod)"</target>
</trans-unit>
<trans-unit id="TestCaseFilterValueRequired">
<source>The /TestCaseFilter argument requires the filter value.
Filter value can be <property>=<value> type.
Examples: "Priority=1", "TestCategory=Nightly"</source>
<note></note>
<target state="translated">/TestCaseFilter 引數需要篩選值。
篩選值可以是 <property>=<value> 類型。
範例: "Priority=1", "TestCategory=Nightly"</target>
</trans-unit>
<trans-unit id="InvalidTestCaseFilterValueForSpecificTests">
<source>The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified.</source>
<note></note>
<target state="translated">/TestCaseFilter 引數無法與 /Tests 一起指定。若已指定測試，則篩選測試案例不適用。</target>
</trans-unit>
<trans-unit id="NonDefaultFrameworkAndOrArchDetected">
<source>{0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform.</source>
<note></note>
<target state="translated">{0} 為針對 {1}/{2} 所建置。回合中指定的測試組件應該具有共同的目標 .Net Framework 和平台。</target>
</trans-unit>
<trans-unit id="RunSingleAppContainerSource">
<source>Only one app package (.appx file) can be specified for running tests.</source>
<note></note>
<target state="translated">您只能為執行測試指定一個應用程式套件 (.appx 檔)。</target>
</trans-unit>
<trans-unit id="StartingDiscovery">
<source>Starting test discovery, please wait...</source>
<note></note>
<target state="translated">正在啟動測試探索，請稍候...</target>
</trans-unit>
<trans-unit id="StartingExecution">
<source>Starting test execution, please wait...</source>
<note></note>
<target state="translated">正在啟動測試執行，請稍候...</target>
</trans-unit>
<trans-unit id="DisablingDCOnExceptionWhileParsingDCInfo">
<source>Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run.</source>
<note></note>
<target state="translated">讀取診斷資料配接器設定時擲回執行中的 '{0}'。這個回合中將略過所有診斷資料配接器。</target>
</trans-unit>
<trans-unit id="EnableCodeCoverageArgumentProcessorHelp">
<source>/EnableCodeCoverage
Enables data collector 'CodeCoverage' for the test run.</source>
<note></note>
<target state="translated">/EnableCodeCoverage
為測試回合啟用資料收集器 'CodeCoverage'。</target>
</trans-unit>
<trans-unit id="InvalidEnableCodeCoverageCommand">
<source>Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again.</source>
<note></note>
<target state="translated">'EnableCodeCoverage' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /EnableCodeCoverage)，並再試一次。</target>
</trans-unit>
<trans-unit id="NoTestEntryPoint">
<source>App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project.</source>
<note></note>
<target state="translated">應用程式套件 '{0}' 沒有測試執行程式進入點。若要執行 Windows 市集應用程式的單元測試，請使用 Windows 市集應用程式單元測試程式庫專案建立應用程式套件。</target>
</trans-unit>
<trans-unit id="DisablingCodeCoverageInAppContainerTestExecution">
<source>Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run.</source>
<note></note>
<target state="translated">Windows 市集應用程式無法使用程式碼涵蓋範圍。將略過這個測試回合的程式碼涵蓋範圍分析。</target>
</trans-unit>
<trans-unit id="SomeTestsUnavailableAfterFiltering">
<source>A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again.</source>
<note></note>
<target state="translated">已探索到總計 {0} 個測試，但有些測試不符合指定的選取準則 ({1})。請使用正確的值並再試一次。</target>
</trans-unit>
<trans-unit id="TestAdapterPathHelp">
<source>--TestAdapterPath|/TestAdapterPath
This makes vstest.console.exe process use custom test adapters
from a given path (if any) in the test run.
Example /TestAdapterPath:<pathToCustomAdapters></source>
<note></note>
<target state="translated">--TestAdapterPath|/TestAdapterPath
這可讓 vstest.console.exe 處理序在測試回合中，
使用指定路徑 (如有指定) 中的自訂測試配接器。
範例 /TestAdapterPath:<自訂配接器的路徑></target>
</trans-unit>
<trans-unit id="TestAdapterPathValueRequired">
<source>The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters</source>
<note></note>
<target state="translated">/TestAdapterPath 參數需要一個值，這個值是包含自訂測試配接器之位置的路徑。範例: /TestAdapterPath:c:\MyCustomAdapters</target>
</trans-unit>
<trans-unit id="InvalidTestAdapterPathCommand">
<source>The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1}</source>
<note></note>
<target state="translated">'TestAdapterPath' 中指定的路徑 '{0}' 無效。錯誤: {1}</target>
</trans-unit>
<trans-unit id="TestAdapterPathDoesNotExist">
<source>The custom test adapter search path provided was not found, provide a valid path and try again.</source>
<note></note>
<target state="translated">找不到提供的自訂測試配接器搜尋路徑。請提供有效的路徑，並再試一次。</target>
</trans-unit>
<trans-unit id="NoAdaptersFoundInTestAdapterPath">
<source>The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again.</source>
<note></note>
<target state="translated">'TestAdapterPath' 中指定的路徑 '{0}' 不包含任何測試配接器。請提供有效的路徑，並再試一次。</target>
</trans-unit>
<trans-unit id="PhoneAppContainerTestPrerequisiteFail">
<source>Could not start test run for the tests for Windows Phone app: {0}.</source>
<note></note>
<target state="translated">無法為 Windows Phone 應用程式的測試啟動測試回合: {0}。</target>
</trans-unit>
<trans-unit id="SwitchToIsolationInPhoneAppContainerMode">
<source>Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning.</source>
<note></note>
<target state="translated">使用隔離模式執行 Windows Phone 應用程式的單元測試。使用 /InIsolation 參數可隱藏這個警告。</target>
</trans-unit>
<trans-unit id="DisablingCodeCoverageInPhoneAppContainerTestExecution">
<source>Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run.</source>
<note></note>
<target state="translated">Windows Phone 應用程式無法使用程式碼涵蓋範圍。將略過這個測試回合的程式碼涵蓋範圍分析。</target>
</trans-unit>
<trans-unit id="DisablingDataCollectionInPhoneAppContainerTestExecution">
<source>Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings.</source>
<note></note>
<target state="translated">執行 Windows Phone 應用程式的單元測試時，不支援診斷資料配接器。請從設定中移除診斷資料配接器設定。</target>
</trans-unit>
<trans-unit id="PhoneNoTestEntryPoint">
<source>App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project.</source>
<note></note>
<target state="translated">應用程式套件 '{0}' 沒有測試執行程式進入點。若要執行 Windows Phone 應用程式的單元測試，請使用 Windows Phone 單元測試應用程式專案建立應用程式套件。</target>
</trans-unit>
<trans-unit id="TestSettingsFrameworkMismatch">
<source>Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning.</source>
<note></note>
<target state="translated">使用架構 {0} 執行測試。指定 /Framework:{1} 可隱藏這個警告。</target>
</trans-unit>
<trans-unit id="AppxBundleSourceWarning">
<source>No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again.</source>
<note></note>
<target state="translated">在指定的測試容器中找不到測試。此外，Microsoft Windows 市集單元測試配接器不支援 .appxbundle 檔案。請在建立應用程式套件時建立 appx (將 [產生應用程式套件組合] 選項設定為 [永不])，並再試一次。</target>
</trans-unit>
<trans-unit id="ParallelArgumentProcessorHelp">
<source>--Parallel|/Parallel
Specifies that the tests be executed in parallel. By default up
to all available cores on the machine may be used.
The number of cores to use may be configured using a settings file.</source>
<note></note>
<target state="translated">--Parallel|/Parallel
指定平行執行測試。根據預設，最多會使用
機器上所有的可用核心。可使用設定檔設定
要使用的核心數。</target>
</trans-unit>
<trans-unit id="InvalidParallelCommand">
<source>Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again.</source>
<note></note>
<target state="translated">'Parallel' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /Parallel)，並再試一次。</target>
</trans-unit>
<trans-unit id="CannotBeNullOrEmpty">
<source>Cannot be null or empty</source>
<note></note>
<target state="translated">不可為 null 或空白</target>
</trans-unit>
<trans-unit id="PortArgumentHelp">
<source>--Port|/Port:<Port>
The Port for socket connection and receiving the event messages.</source>
<note></note>
<target state="translated">--Port|/Port:<連接埠>
通訊端連線以及接收事件訊息的連接埠。</target>
</trans-unit>
<trans-unit id="InvalidPortArgument">
<source>The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages.</source>
<note></note>
<target state="translated">--Port|/Port 引數需要整數的連接埠號碼。指定用於通訊端連線以及接收事件訊息的連接埠。</target>
</trans-unit>
<trans-unit id="AssemblyPathInvalid">
<source>Unable to find the assembly under test. Please make sure that the project is built.</source>
<note></note>
<target state="translated">找不到正在進行測試的組件。請確定已建置專案。</target>
</trans-unit>
<trans-unit id="ProjectPathNotFound">
<source>The Path {0} does not exist.</source>
<note></note>
<target state="translated">路徑 {0} 不存在。</target>
</trans-unit>
<trans-unit id="BuildBasePathArgumentHelp">
<source>--BuildBasePath|/BuildBasePath:<BuildBasePath>
The directory containing the temporary outputs.</source>
<note></note>
<target state="translated">--BuildBasePath|/BuildBasePath:<建置基底路徑>
包含暫存輸出的目錄。</target>
</trans-unit>
<trans-unit id="ConfigurationArgumentHelp">
<source>-c|--Configuration|/c|/Configuration:<Configuration>
The configuration the project is built for i.e. Debug/Release</source>
<note></note>
<target state="translated">-c|--Configuration|/c|/Configuration:<組態>
建置專案標的組態，例如，偵錯/發行</target>
</trans-unit>
<trans-unit id="InvalidConfiguration">
<source>The given configuration is invalid.</source>
<note></note>
<target state="translated">給定的組態無效。</target>
</trans-unit>
<trans-unit id="OutputArgumentHelp">
<source>-o|--Output|/o|/Output:<Output>
The directory containing the binaries to run.</source>
<note></note>
<target state="translated">-o|--Output|/o|/Output:<輸出>
包含要執行的二進位檔案的目錄。</target>
</trans-unit>
<trans-unit id="BuildBasePathNotFound">
<source>The BuildBasePath was not found, provide a valid path and try again.</source>
<note></note>
<target state="translated">找不到 BuildBasePath。請提供有效的路徑，並再試一次。</target>
</trans-unit>
<trans-unit id="OutputPathNotFound">
<source>The Output path was not found, provide a valid path and try again.</source>
<note></note>
<target state="translated">找不到輸出路徑。請提供有效的路徑，並再試一次。</target>
</trans-unit>
<trans-unit id="AddnlInfoMessagesBanner">
<source>Additional Information Messages:</source>
<note></note>
<target state="translated">其他資訊訊息:</target>
</trans-unit>
<trans-unit id="Days">
<source>Days</source>
<note></note>
<target state="translated">日</target>
</trans-unit>
<trans-unit id="ErrorMessageBanner">
<source>Error Message:</source>
<note></note>
<target state="translated">錯誤訊息:</target>
</trans-unit>
<trans-unit id="ExecutionTimeFormatString">
<source> Total time: {0:0.0000} {1}</source>
<note></note>
<target state="translated"> 時間總計: {0:0.0000} {1}</target>
</trans-unit>
<trans-unit id="Hours">
<source>Hours</source>
<note></note>
<target state="translated">小時</target>
</trans-unit>
<trans-unit id="LoggerNotFound">
<source>Could not find a test logger with URI or FriendlyName '{0}'.</source>
<note></note>
<target state="translated">找不到具有 URI 或 FriendlyName '{0}' 的測試記錄器。</target>
</trans-unit>
<trans-unit id="Minutes">
<source>Minutes</source>
<note></note>
<target state="translated">分鐘</target>
</trans-unit>
<trans-unit id="Seconds">
<source>Seconds</source>
<note></note>
<target state="translated">秒</target>
</trans-unit>
<trans-unit id="StacktraceBanner">
<source>Stack Trace:</source>
<note></note>
<target state="translated">堆疊追蹤:</target>
</trans-unit>
<trans-unit id="StdErrMessagesBanner">
<source>Standard Error Messages:</source>
<note></note>
<target state="translated">標準錯誤訊息:</target>
</trans-unit>
<trans-unit id="StdOutMessagesBanner">
<source>Standard Output Messages:</source>
<note></note>
<target state="translated">標準輸出訊息:</target>
</trans-unit>
<trans-unit id="AttachmentsBanner">
<source>Attachments:</source>
<note></note>
<target state="translated">附件:</target>
</trans-unit>
<trans-unit id="AttachmentOutputFormat">
<source> {0}</source>
<note></note>
<target state="translated"> {0}</target>
</trans-unit>
<trans-unit id="NoTestsAvailableInSources">
<source>No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.</source>
<note></note>
<target state="translated">{0} 中沒有可供使用的測試。請確定已安裝適當的測試探索程式及執行程式、平台與 Framework 版本設定，並再試一次。</target>
</trans-unit>
<trans-unit id="FailedTestIndicator">
<source>Failed</source>
<note>Message which is written to the console when a test fails.</note>
<target state="translated">失敗</target>
</trans-unit>
<trans-unit id="PassedTestIndicator">
<source>Passed</source>
<note>Message which is written to the console when a test passes.</note>
<target state="translated">已通過</target>
</trans-unit>
<trans-unit id="SkippedTestIndicator">
<source>Skipped</source>
<note></note>
<target state="translated">已跳過</target>
</trans-unit>
<trans-unit id="DiscoveryFailed">
<source>Discovery failed for given sources. Exception : {0}</source>
<note></note>
<target state="translated">給定來源的探索失敗。例外狀況: {0}</target>
</trans-unit>
<trans-unit id="ParentProcessIdArgumentHelp">
<source>--ParentProcessId|/ParentProcessId:<ParentProcessId>
Process Id of the Parent Process responsible for launching current process.</source>
<note></note>
<target state="translated">--ParentProcessId|/ParentProcessId:<父處理序識別碼>
負責啟動目前處理序的父處理序之處理序識別碼。</target>
</trans-unit>
<trans-unit id="InvalidParentProcessIdArgument">
<source>The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process.</source>
<note></note>
<target state="translated">--ParentProcessId|/ParentProcessId 引數需要整數的處理序識別碼。請為已啟動這個處理序的父處理序指定處理序識別碼。</target>
</trans-unit>
<trans-unit id="HelpArgumentsText">
<source>Arguments:</source>
<note></note>
<target state="translated">引數:</target>
</trans-unit>
<trans-unit id="EnableDiagUsage">
<source>--Diag|/Diag:<Path to log file>
Enable logs for test platform.
Logs are written to the provided file.
Change the trace level for logs as shown below
Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose">
Allowed values for tracelevel: off, error, warning, info and verbose.</source>
<note></note>
<target state="translated">--Diag|/Diag:<日誌檔路徑>
啟用測試平台的記錄檔。
記錄會寫入提供的檔案。
變更記錄檔的追蹤層級，如下所示
範例: /Diag:<日誌檔路徑>;tracelevel=<預設為 [詳細資訊]>
允許的 tracelevel 值為: 關閉、錯誤、警告、資訊與詳細資訊。</target>
</trans-unit>
<trans-unit id="LoggerFileIsReadOnly">
<source>The file {0} provided is read only</source>
<note></note>
<target state="translated">提供的檔案 {0} 為唯讀</target>
</trans-unit>
<trans-unit id="DesignModeClientTimeoutError">
<source>Timeout to connect or process request for DesignModeClient on port: {0}</source>
<target state="translated">連線或處理連接埠 {0} 上對於 DesignModeClient 之要求的逾時時間:</target>
<note></note>
</trans-unit>
<trans-unit id="NotRunTestIndicator">
<source>Not Run</source>
<target state="translated">未執行</target>
<note></note>
</trans-unit>
<trans-unit id="CLIRunSettingsArgumentHelp">
<source>RunSettings arguments:
Arguments to pass runsettings configurations through commandline. Arguments may be specified as name-value pair of the form [name]=[value] after "-- ". Note the space after --.
Use a space to separate multiple [name]=[value].
More info on RunSettings arguments support: https://aka.ms/vstest-runsettings-arguments</source>
<target state="translated">RunSettings 引數:
透過命令列傳遞 runsettings 組態的引數。引數可以接在 "-- " 之後，以 [名稱]=[值] 的格式指定名稱/值配對。請注意 -- 之後的空格。
使用空格以隔開多個 [名稱]=[值]。
RunSettings 引數支援的詳細資訊: https://aka.ms/vstest-runsettings-arguments</target>
<note></note>
</trans-unit>
<trans-unit id="MalformedRunSettingsKey">
<source>One or more runsettings provided contain invalid token</source>
<target state="translated">提供的一或多個 runsettings 包含無效的語彙基元</target>
<note></note>
</trans-unit>
<trans-unit id="ResultsDirectoryArgumentHelp">
<source>--ResultsDirectory|/ResultsDirectory
Test results directory will be created in specified path if not exists.
Example /ResultsDirectory:<pathToResultsDirectory></source>
<target state="translated">--ResultsDirectory|/ResultsDirectory
若不存在，將會於指定路徑中建立測試結果目錄。
範例 /ResultsDirectory:<結果目錄路徑></target>
<note></note>
</trans-unit>
<trans-unit id="ResultsDirectoryValueRequired">
<source>The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory</source>
<target state="translated">/ResultsDirectory 參數需要值，亦即測試結果的儲存位置。範例: /ResultsDirectory:c:\MyTestResultsDirectory</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidResultsDirectoryPathCommand">
<source>The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1}</source>
<target state="translated">'ResultsDirectory' 中指定的路徑 '{0}' 無效。錯誤: {1}</target>
<note></note>
</trans-unit>
<trans-unit id="InIsolationDeprecated">
<source>The /InIsolation flag is deprecated. The tests are always run in a separate process</source>
<target state="translated">/InIsolation 旗標已標示即將淘汰。測試一律會在個別的處理序中執行</target>
<note></note>
</trans-unit>
<trans-unit id="VstestDiagLogOutputPath">
<source>Logging Vstest Diagnostics in file: {0}</source>
<target state="translated">在檔案 {0} 中記錄 Vstest 診斷</target>
<note></note>
</trans-unit>
<trans-unit id="CollectArgumentHelp">
<source>--Collect|/Collect:<DataCollector FriendlyName>
Enables data collector for the test run. More info here : https://aka.ms/vstest-collect</source>
<target state="translated">--Collect|/Collect:<資料收集器易記名稱>
為測試回合啟用資料收集器。此處有詳細資訊: https://aka.ms/vstest-collect</target>
<note></note>
</trans-unit>
<trans-unit id="DataCollectorFriendlyNameInvalid">
<source>The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored.</source>
<target state="translated">資料收集器的易記名稱 '{0}' 無效。該資料收集器將予忽略。</target>
<note></note>
</trans-unit>
<trans-unit id="DbgTrcMessagesBanner">
<source>Debug Traces Messages:</source>
<target state="translated">偵錯追蹤訊息:</target>
<note></note>
</trans-unit>
<trans-unit id="EnableBlameUsage">
<source>--Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value]
Runs the test in blame mode. This option is helpful in isolating the problematic test causing test host crash.
It creates an output file in the current directory as "Sequence.xml",
that captures the order of execution of test before the crash.
You may optionally choose to collect process dump for the test host.
When you choose to collect dump, by default, a mini dump will be collected on a crash.
You may also choose to override this default behaviour by some optional parameters:
CollectAlways - To collect dump on exit even if there is no crash (true/false)
DumpType - To specify dump type (mini/full).
Example: /Blame
/Blame:CollectDump
/Blame:CollectDump;CollectAlways=true;DumpType=full</source>
<target state="translated">--Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value]
以 blame 模式執行測試。此選項在隔離造成測試主機當機的問題測試時相當實用。
它會在目前的目錄建立輸出檔案 "Sequence.xml"，
該檔案會擷取當機前的測試執行順序。
您也可以選擇收集測試主機的處理序傾印。
當您選擇收集傾印時，預設會在當機時收集迷你傾印／
您也可以選擇使用一些選用參數來覆寫此預設行為:
CollectAlways - 即使沒有當機，也在離開時收集傾印 (true/false)
DumpType - 指定傾印類型 (mini/full)。
範例: /Blame
/Blame:CollectDump
/Blame:CollectDump;CollectAlways=true;DumpType=full</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunAborted">
<source>Test Run Aborted.</source>
<target state="translated">測試回合已中止。</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunCanceled">
<source>Test Run Canceled.</source>
<target state="translated">測試回合已取消。</target>
<note></note>
</trans-unit>
<trans-unit id="OpenResponseFileError">
<source>Error opening response file '{0}'</source>
<target state="translated">開啟回應檔案 '{0}' 時發生錯誤</target>
<note></note>
</trans-unit>
<trans-unit id="ResponseFileArgumentHelp">
<source>@<file>
Read response file for more options.</source>
<target state="translated">@<檔案>
讀取回應檔以取得更多選項。</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummaryForCanceledOrAbortedRun">
<source>Total tests: Unknown</source>
<target state="translated">測試數總計: 未知</target>
<note></note>
</trans-unit>
<trans-unit id="StringFormatToJoinTwoStrings">
<source>{0} {1}</source>
<target state="translated">{0} {1}</target>
<note></note>
</trans-unit>
<trans-unit id="SuggestTestAdapterPathIfNoTestsIsFound">
<source>Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>.</source>
<target state="translated">此外，可使用 /TestAdapterPath 命令，指定要測試配接器的路徑。範例為 /TestAdapterPath:<自訂配接器的路徑>。</target>
<note></note>
</trans-unit>
<trans-unit id="UseVsixExtensionsDeprecation">
<source>/UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead.</source>
<target state="translated">/UseVsixExtensions 即將淘汰。請改用 /TestAdapterPath。</target>
<note></note>
</trans-unit>
<trans-unit id="DisableAutoFakesUsage">
<source>--DisableAutoFakes|/DisableAutoFakes:<true/false>
Example: /DisableAutoFakes:true</source>
<target state="translated">--DisableAutoFakes|/DisableAutoFakes:<true/false>
範例: /DisableAutoFakes:true</target>
<note></note>
</trans-unit>
<trans-unit id="CollectWithTestSettingErrorMessage">
<source>--Collect|/Collect:"{0}" is not supported if test run is configured using testsettings.</source>
<target state="translated">若使用測試設定來設定測試回合，則不支援 --Collect|/Collect:"{0}"。</target>
<note></note>
</trans-unit>
<trans-unit id="RunsettingsWithDCErrorMessage">
<source>Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}.</source>
<target state="translated">除了程式碼涵蓋範圍與 Microsoft Fakes 以外，內嵌測試設定不支援透過回合設定來設定的資料收集器。如需詳細資訊，請參閱 https://aka.ms/vstest-configure-datacollector。回合設定: {0}。</target>
<note></note>
</trans-unit>
<trans-unit id="EnableLoggerArgumentsInNetCore">
<source>--logger|/logger:<Logger Uri/FriendlyName>
Specify a logger for test results. For example, to log results into a
Visual Studio Test Results File (TRX) use /logger:trx[;LogFileName=<Defaults to unique file name>]
Creates file in TestResults directory with given LogFileName.
Change the verbosity level in log messages for console logger as shown below
Example: /logger:console;verbosity=<Defaults to "minimal">
Allowed values for verbosity: quiet, minimal, normal and detailed.
Change the diagnostic level prefix for console logger as shown below
Example: /logger:console;prefix=<Defaults to "false">
More info on Console Logger here : https://aka.ms/console-logger</source>
<target state="translated">--logger|/logger:<記錄器 URI/易記名稱>
指定測試結果的記錄器。例如，使用 /logger:trx[;LogFileName=<預設為唯一的檔案名稱>]，
將結果記錄至 Visual Studio 測試結果檔案 (TRX)
以指定的 LogFileName，在 TestResults 目錄中建立檔案。
變更主控台記錄器的記錄訊息詳細程度等級，如下所示
範例: /logger:console;verbosity=<預設為 "minimal">
詳細程度的允許值: quiet、minimal、normal 以及 detailed。
變更主控台記錄器的診斷等級前置詞，如下所示
範例: /logger:console;prefix=<預設為 "false">
主控台記錄器詳細資訊於此: https://aka.ms/console-logger</target>
<note></note>
</trans-unit>
<trans-unit id="BlameCollectDumpNotSupportedForPlatform">
<source>Collecting crash dumps by option CollectDump for Blame is not supported for this platform.</source>
<target state="translated">此平台不支援使用 CollectDump for Blame 選項收集損毀傾印。</target>
<note></note>
</trans-unit>
<trans-unit id="BlameIncorrectOption">
<source>The blame parameter specified with blame, {0} is invalid. Ignoring this parameter.</source>
<target state="translated">以 blame 指定的 blame 參數 {0} 無效，即將忽略此參數。</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidDiagFilePath">
<source>Diag file path '{0}' is not valid.</source>
<target state="translated">診斷檔案路徑 '{0}' 無效。</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidBlameArgument">