forked from microsoft/vstest
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Resources.zh-Hans.xlf
1244 lines (1218 loc) · 71.5 KB
/
Resources.zh-Hans.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-Hans">
<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">版权所有 (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) 测试执行命令行工具版本 {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:<Logger Uri/FriendlyName>
为测试结果指定一个记录器。例如，若要将结果记录到
Visual Studio 测试结果文件(TRX)中，请使用/logger:trx[;LogFileName=<Defaults to unique file name>]
使用给定的 LogFileName 在 TestResults 目录中创建文件。
更改控制台记录器的日志消息中的详细程度，如下所示
示例: /logger:console;verbosity<Defaults to "normal">
允许的详细程度的值: quiet、minimal、normal 和 detailed。
更改控制台记录器的诊断级别前缀，如下所示
示例: /logger:console;prefix=<Defaults to "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 [Arguments] [Options] [[--] <RunSettings arguments>...]]</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:<Settings File>
运行测试时要使用的设置。</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">参数 {0} 不应出现在 "InIsolation" 命令中。指定不带该参数的命令(示例: 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">参数 {0} 不应出现在 "UseVsixExtensions" 命令中.指定指示是否应使用或跳过 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:<File Name>
从给定测试容器中列出所有已发现的测试。</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:<Test Names>
运行其名称与所提供值相匹配的测试。若要提供多个
值，请用逗号将这些值分隔开。
示例: /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:<Platform type>
用于执行测试的目标平台体系结构。
有效值为 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">按照针对测试运行有效的 Platform:{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 Version>
用于执行测试的目标 .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 是 =、!= 或 ~ (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 参数需要筛选器值。
筛选器值可以是“<属性>=<值>”类型。
示例: "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">不能使用 /Tests 指定 /TestCaseFilter 参数。指定测试时无法筛选测试用例。</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">参数 {0} 不应出现在 "EnableCodeCoverage" 命令中。指定不带参数的命令(示例: 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:<pathToCustomAdapters></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">参数 {0} 不应出现在 "Parallel" 命令中。指定不带参数的命令(示例: 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:<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:<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:<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:<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">找不到 Output 路径，请提供有效的路径，然后重试。</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} 中没有可用测试。请确保安装了适当的测试发现器和执行器且平台和框架版本设置合适，然后重试。</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:<ParentProcessId>
父进程的进程 ID 负责启动当前进程。</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 参数要求整数形式的进程 ID。指定启动此进程的父进程的进程 ID。</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:<Path to log file>
启用测试平台的日志。
日志将写入所提供的文件。
更改日志的跟踪级别，如下所示
示例: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose">
允许的 tracelevel 的值: off、error、 warning、info 和 verbose。</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:<pathToResultsDirectory></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:<DataCollector FriendlyName>
启用数据收集器以运行测试。可在此处获取详细信息: 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]
在追责模式下运行测试。此选项有助于隔离导致测试主机崩溃的问题测试。
它会在当前目录中创建一个输出文件 "Sequence.xml"，
用于在崩溃之前捕获测试的执行顺序。
可以根据需要选择收集测试主机的进程转储。
选择收集转储时，默认情况下，将在崩溃时收集小型转储。
还可选择通过一些可选参数覆盖此默认行为:
CollectAlways - 若无崩溃则在退出时收集转储(true/false)
DumpType - 指定转储类型(小型/完整)。
Example: /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">@<file>
有关更多选项，请阅读响应文件。</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:<pathToCustomAdapters>。</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|/如果使用测试设置配置了测试运行，则不支持收集:“{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:<Logger Uri/FriendlyName>
为测试结果指定一个记录器。例如，若要将结果记录到
Visual Studio 测试结果文件(TRX)中，请使用 /logger:trx[;LogFileName=<Defaults to unique file name>]
使用给定的 LogFileName 在 TestResults 目录中创建文件。
更改控制台记录器的日志消息中的详细程度，如下所示
示例: /logger:console;verbosity=<Defaults to "minimal">
允许的详细程度的值: quiet、minimal、normal 和 detailed。
更改控制台记录器的诊断级别前缀，如下所示
示例: /logger:console;prefix=<Defaults to "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">追责时指定的追责参数 {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">