forked from microsoft/vstest
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Resources.xlf
847 lines (839 loc) · 40.8 KB
/
Resources.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
<?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">
<body>
<trans-unit id="FileNotFound">
<source>'{0}' not found.</source>
<note></note>
</trans-unit>
<trans-unit id="AvailableDiscoverersHeaderMessage">
<source>The following Test Discovery Add-Ins are available:</source>
<note></note>
</trans-unit>
<trans-unit id="AvailableExecutorsHeaderMessage">
<source>The following Test Execution Add-Ins are available:</source>
<note></note>
</trans-unit>
<trans-unit id="AvailableExtensionFormat">
<source> {0}</source>
<note>{Locked}</note>
</trans-unit>
<trans-unit id="AvailableExtensionsMetadataFormat">
<source> {0}: {1}</source>
<note></note>
</trans-unit>
<trans-unit id="AvailableLoggersHeaderMessage">
<source>The following Test Logger Add-Ins are available:</source>
<note></note>
</trans-unit>
<trans-unit id="AvailableTestsFormat">
<source> {0}</source>
<note>{Locked}</note>
</trans-unit>
<trans-unit id="CommandLineError">
<source>Error: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="CommaSeparatedFormat">
<source>, {0}</source>
<note>Format used to comma separate a list of values.</note>
</trans-unit>
<trans-unit id="DuplicateArgumentError">
<source>The parameter "{0}" should be provided only once.</source>
<note></note>
</trans-unit>
<trans-unit id="ExceptionFromExtension">
<source>Exception occurred when instantiating extension '{0}': {1}</source>
<note></note>
</trans-unit>
<trans-unit id="ListTestsHeaderMessage">
<source>The following Tests are available:</source>
<note></note>
</trans-unit>
<trans-unit id="NoArgumentProcessorFound">
<source>Unrecognized parameter "{0}".</source>
<note></note>
</trans-unit>
<trans-unit id="TestSourceFileNotFound">
<source>The test source file "{0}" provided was not found.</source>
<note></note>
</trans-unit>
<trans-unit id="LoggerUriInvalid">
<source>The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.</source>
<note></note>
</trans-unit>
<trans-unit id="CommandLineInformational">
<source>Information: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="CommandLineWarning">
<source>Warning: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="HelpArgumentHelp">
<source>-?|--Help|/?|/Help
Display this usage message.</source>
<note></note>
</trans-unit>
<trans-unit id="CopyrightCommandLineTitle">
<source>Copyright (c) Microsoft Corporation. All rights reserved.</source>
<note></note>
</trans-unit>
<trans-unit id="MicrosoftCommandLineTitle">
<source>Microsoft (R) Test Execution Command Line Tool Version {0}</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="HelpDescriptionText">
<source>Description: Runs tests from the specified files.</source>
<note></note>
</trans-unit>
<trans-unit id="HelpOptionsText">
<source>Options:</source>
<note>Section Header for subsequent command help listing</note>
</trans-unit>
<trans-unit id="HelpUsageText">
<source>Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]]</source>
<note></note>
</trans-unit>
<trans-unit id="MissingTestSourceFile">
<source>No test source files were specified.</source>
<note></note>
</trans-unit>
<trans-unit id="NoArgumentsProvided">
<source>No arguments were specified.</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="AvailableSettingsProvidersHeaderMessage">
<source>The following Settings Providers Add-Ins are available:</source>
<note></note>
</trans-unit>
<trans-unit id="RunSettingsArgumentHelp">
<source>--Settings|/Settings:<Settings File>
Settings to use when running tests.</source>
<note></note>
</trans-unit>
<trans-unit id="RunSettingsRequired">
<source>The /Settings parameter requires a settings file to be provided.</source>
<note></note>
</trans-unit>
<trans-unit id="RunSettingsFileNotFound">
<source>The Settings file '{0}' could not be found.</source>
<note></note>
</trans-unit>
<trans-unit id="TestRunFailed">
<source>Test Run Failed.</source>
<note></note>
</trans-unit>
<trans-unit id="TestRunSuccessful">
<source>Test Run Successful.</source>
<note></note>
</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>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="BatchSizeRequired">
<source>The /BatchSize argument requires the size of the batch. Example: /BatchSize:10</source>
<note></note>
</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>
</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>
</trans-unit>
<trans-unit id="ListDiscoverersHelp">
<source>/ListDiscoverers
Lists installed test discoverers.</source>
<note></note>
</trans-unit>
<trans-unit id="ListExecutorsHelp">
<source>/ListExecutors
Lists installed test executors.</source>
<note></note>
</trans-unit>
<trans-unit id="ListLoggersHelp">
<source>/ListLoggers
Lists installed test loggers.</source>
<note></note>
</trans-unit>
<trans-unit id="ListSettingsProvidersHelp">
<source>/ListSettingsProviders
Lists installed test settings providers.</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="TimeElapsed">
<source>Time elapsed :</source>
<note></note>
</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>
</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>
</trans-unit>
<trans-unit id="SearchStringDelimiter">
<source>,</source>
<note></note>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="LoggerFriendlyNameFormat">
<source> FriendlyName: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="ExtensionUriFormat">
<source> Uri: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="SettingFormat">
<source> SettingName: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="SupportedFileTypesIndicator">
<source> Supported File Types:</source>
<note></note>
</trans-unit>
<trans-unit id="SupportedFileWithoutSeparator">
<source> {0}</source>
<note></note>
</trans-unit>
<trans-unit id="SupportedFileWithSeparator">
<source> {0},</source>
<note></note>
</trans-unit>
<trans-unit id="UriOfDefaultExecutor">
<source> Default Executor Uri: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="LoggerUriFormat">
<source> Uri: {0}</source>
<note></note>
</trans-unit>
<trans-unit id="InvalidPlatformType">
<source>Invalid platform type:{0}. Valid platform types are x86, x64 and Arm.</source>
<note></note>
</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>
</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>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="AppContainerTestPrerequisiteFail">
<source>Could not start test run for unit tests for Windows Store app: {0}.</source>
<note></note>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="RunSingleAppContainerSource">
<source>Only one app package (.appx file) can be specified for running tests.</source>
<note></note>
</trans-unit>
<trans-unit id="StartingDiscovery">
<source>Starting test discovery, please wait...</source>
<note></note>
</trans-unit>
<trans-unit id="StartingExecution">
<source>Starting test execution, please wait...</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="EnableCodeCoverageArgumentProcessorHelp">
<source>/EnableCodeCoverage
Enables data collector 'CodeCoverage' for the test run.</source>
<note></note>
</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>
</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>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="InvalidTestAdapterPathCommand">
<source>The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1}</source>
<note></note>
</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>
</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>
</trans-unit>
<trans-unit id="PhoneAppContainerTestPrerequisiteFail">
<source>Could not start test run for the tests for Windows Phone app: {0}.</source>
<note></note>
</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>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="TestSettingsFrameworkMismatch">
<source>Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning.</source>
<note></note>
</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>
</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>
</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>
</trans-unit>
<trans-unit id="CannotBeNullOrEmpty">
<source>Cannot be null or empty</source>
<note></note>
</trans-unit>
<trans-unit id="PortArgumentHelp">
<source>--Port|/Port:<Port>
The Port for socket connection and receiving the event messages.</source>
<note></note>
</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>
</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>
</trans-unit>
<trans-unit id="ProjectPathNotFound">
<source>The Path {0} does not exist.</source>
<note></note>
</trans-unit>
<trans-unit id="BuildBasePathArgumentHelp">
<source>--BuildBasePath|/BuildBasePath:<BuildBasePath>
The directory containing the temporary outputs.</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="InvalidConfiguration">
<source>The given configuration is invalid.</source>
<note></note>
</trans-unit>
<trans-unit id="OutputArgumentHelp">
<source>-o|--Output|/o|/Output:<Output>
The directory containing the binaries to run.</source>
<note></note>
</trans-unit>
<trans-unit id="BuildBasePathNotFound">
<source>The BuildBasePath was not found, provide a valid path and try again.</source>
<note></note>
</trans-unit>
<trans-unit id="OutputPathNotFound">
<source>The Output path was not found, provide a valid path and try again.</source>
<note></note>
</trans-unit>
<trans-unit id="AddnlInfoMessagesBanner">
<source>Additional Information Messages:</source>
<note></note>
</trans-unit>
<trans-unit id="Days">
<source>Days</source>
<note></note>
</trans-unit>
<trans-unit id="ErrorMessageBanner">
<source>Error Message:</source>
<note></note>
</trans-unit>
<trans-unit id="ExecutionTimeFormatString">
<source> Total time: {0:0.0000} {1}</source>
<note></note>
</trans-unit>
<trans-unit id="Hours">
<source>Hours</source>
<note></note>
</trans-unit>
<trans-unit id="LoggerNotFound">
<source>Could not find a test logger with URI or FriendlyName '{0}'.</source>
<note></note>
</trans-unit>
<trans-unit id="Minutes">
<source>Minutes</source>
<note></note>
</trans-unit>
<trans-unit id="Seconds">
<source>Seconds</source>
<note></note>
</trans-unit>
<trans-unit id="StacktraceBanner">
<source>Stack Trace:</source>
<note></note>
</trans-unit>
<trans-unit id="StdErrMessagesBanner">
<source>Standard Error Messages:</source>
<note></note>
</trans-unit>
<trans-unit id="StdOutMessagesBanner">
<source>Standard Output Messages:</source>
<note></note>
</trans-unit>
<trans-unit id="AttachmentsBanner">
<source>Attachments:</source>
<note></note>
</trans-unit>
<trans-unit id="AttachmentOutputFormat">
<source> {0}</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="FailedTestIndicator">
<source>Failed {0}</source>
<note>Message which is written to the console when a test fails.</note>
</trans-unit>
<trans-unit id="PassedTestIndicator">
<source>Passed {0}</source>
<note>Message which is written to the console when a test passes.</note>
</trans-unit>
<trans-unit id="SkippedTestIndicator">
<source>Skipped {0}</source>
<note></note>
</trans-unit>
<trans-unit id="DiscoveryFailed">
<source>Discovery failed for given sources. Exception : {0}</source>
<note></note>
</trans-unit>
<trans-unit id="ParentProcessIdArgumentHelp">
<source>--ParentProcessId|/ParentProcessId:<ParentProcessId>
Process Id of the Parent Process responsible for launching current process.</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="HelpArgumentsText">
<source>Arguments:</source>
<note></note>
</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>
</trans-unit>
<trans-unit id="LoggerFileIsReadOnly">
<source>The file {0} provided is read only</source>
<note></note>
</trans-unit>
<trans-unit id="DesignModeClientTimeoutError">
<source>Timeout to connect or process request for DesignModeClient on port: {0}</source>
<target state="new">Timeout to connect or process request for DesignModeClient on port: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="NotRunTestIndicator">
<source>Not Run {0}</source>
<target state="new">Not Run {0}</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="new">Args:
Any extra arguments that should be passed to adapter. Arguments may be specified as name-value pair of the form <n>=<v>, where <n> is the argument name, and <v> is the argument value. Use a space to separate multiple arguments.</target>
<note></note>
</trans-unit>
<trans-unit id="MalformedRunSettingsKey">
<source>One or more runsettings provided contain invalid token</source>
<target state="new">One or more runsettings provided contain invalid token</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="new">--ResultsDirectory|/ResultsDirectory
Test results directory will be created in specified path if not exists.
Example /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="new">The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /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="new">The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {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="new">The /InIsolation flag is deprecated. The tests are always run in a separate process</target>
<note></note>
</trans-unit>
<trans-unit id="VstestDiagLogOutputPath">
<source>Logging Vstest Diagnostics in file: {0}</source>
<target state="new">Logging Vstest Diagnostics in file: {0}</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="new">CollectArgumentHelp</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="new">The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored.</target>
<note></note>
</trans-unit>
<trans-unit id="DbgTrcMessagesBanner">
<source>Debug Traces Messages:</source>
<target state="new">Debug Traces Messages:</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="new">--Blame|/Blame
Enable Blame mode to get name of the faulty test case in event of a test host crash.</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunAborted">
<source>Test Run Aborted.</source>
<target state="new">Test Run Aborted.</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunCanceled">
<source>Test Run Canceled.</source>
<target state="new">Test Run Canceled.</target>
<note></note>
</trans-unit>
<trans-unit id="OpenResponseFileError">
<source>Error opening response file '{0}'</source>
<target state="new">Error opening response file '{0}'</target>
<note></note>
</trans-unit>
<trans-unit id="ResponseFileArgumentHelp">
<source>@<file>
Read response file for more options.</source>
<target state="new">@<file>
Read response file for more options.</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummaryForCanceledOrAbortedRun">
<source>Total tests: Unknown</source>
<target state="new">Total tests: Unknown. Passed: {0}. Failed: {1}. Skipped: {2}.</target>
<note></note>
</trans-unit>
<trans-unit id="StringFormatToJoinTwoStrings">
<source>{0} {1}</source>
<target state="new">{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="new">Additionally, you can point to location of test executors and discoverers by specifying &apos;/TestAdapterPath&apos; command. Example /TestAdapterPath:&lt;pathToCustomAdapters&gt;.</target>
<note></note>
</trans-unit>
<trans-unit id="UseVsixExtensionsDeprecation">
<source>/UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead.</source>
<target state="new">/UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead.</target>
<note></note>
</trans-unit>
<trans-unit id="DisableAutoFakesUsage">
<source>--DisableAutoFakes|/DisableAutoFakes:<true/false>
Example: /DisableAutoFakes:true</source>
<target state="new">--DisableAutoFakes|/DisableAutoFakes:<true/false>
Example: /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="new">--Collect|/Collect:"{0}" is not supported if test run is configured using testsettings.</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="new">DataCollector:"{0}" in runsettings in not supported if test run is configured using testsettings.</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="new">--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
To publish test results to Team Foundation Server, use TfsPublisher as shown below
Example: /logger:TfsPublisher;
Collection=<team project collection url>;
BuildName=<build name>;
TeamProject=<team project name>
[;Platform=<Defaults to "Any CPU">]
[;Flavor=<Defaults to "Debug">]
[;RunTitle=<title>]</target>
<note></note>
</trans-unit>
<trans-unit id="BlameCollectDumpNotSupportedForPlatform">
<source>CollectDump option for Blame is not supported for this platform.</source>
<target state="new">CollectDump option for Blame is not supported for this platform.</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="new">The option specified with blame, {0} is invalid. This will be ignored.</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidDiagFilePath">
<source>Diag file path '{0}' is not valid.</source>
<target state="new">Diag file path '{0}' is not valid.</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidBlameArgument">
<source>Blame argument '{0}' is not valid.</source>
<target state="new">Blame argument '{0}' in invalid.</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidDiagArgument">
<source>Diag argument '{0}' is not valid.</source>
<target state="new">Diag argument '{0}' is invalid.</target>
<note></note>
</trans-unit>
<trans-unit id="InvalidLoggerArgument">
<source>Logger argument '{0}' is not valid.</source>
<target state="new">Logger argument '{0}' is invalid.</target>
<note></note>
</trans-unit>
<trans-unit id="Framework35NotSupported">
<source>Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode".</source>
<target state="new">Framework35 not supported. Use Framework40 or above to run tests in CLR 4.0 "compatibly mode".</target>
<note></note>
</trans-unit>
<trans-unit id="ProgressIndicatorString">
<source>Test run in progress</source>
<target state="new">Test run in progress</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummaryTotalTests">
<source>Total tests: {0}</source>
<target state="new">Total tests: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummaryFailedTests">
<source> Failed: {0}</source>
<target state="new"> Failed: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummaryPassedTests">
<source> Passed: {0}</source>
<target state="new"> Passed: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunSummarySkippedTests">
<source> Skipped: {0}</source>
<target state="new"> Skipped: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="TestSourcesDiscovered">
<source>A total of {0} test files matched the specified pattern.</source>
<target state="new">A total of {0} test source files are discovered.</target>
<note></note>
</trans-unit>
</body>
</file>
</xliff>