-
Notifications
You must be signed in to change notification settings - Fork 315
/
Resources.xlf
178 lines (178 loc) · 10.5 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
<?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="DiscovererInstantiationException">
<source>Exception occurred while instantiating discoverer : {0}</source>
<note></note>
</trans-unit>
<trans-unit id="DuplicateAdaptersFound">
<source>Multiple test adapters with the same uri '{0}' were found. Ignoring adapter '{1}'. Please uninstall the conflicting adapter(s) to avoid this warning.</source>
<note>{0} is the unique identifier of test adapter. {1} is the name of the test adapter that shares a unique identifier with a previously loaded adapter.</note>
</trans-unit>
<trans-unit id="DuplicateSource">
<source>Ignoring the specified duplicate source '{0}'.</source>
<note></note>
</trans-unit>
<trans-unit id="ExceptionFromLoadTests">
<source>An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}</source>
<note></note>
</trans-unit>
<trans-unit id="ExceptionFromRunTests">
<source>An exception occurred while invoking executor '{0}': {1}</source>
<note></note>
</trans-unit>
<trans-unit id="FileNotFound">
<source>Could not find file {0}.</source>
<note></note>
</trans-unit>
<trans-unit id="HostDebuggerWarning">
<source>Host debugging is enabled. Please attach debugger to testhost process to continue.</source>
<note>Host, testhost are key words, it should not be localized</note>
</trans-unit>
<trans-unit id="IgnoringExecutorAsNoDefaultExecutorUriAttribute">
<source>Ignoring the test executor corresponding to test discoverer {0} because the discoverer does not have the DefaultExecutorUri attribute . You might need to re-install the test adapter add-in.</source>
<note></note>
</trans-unit>
<trans-unit id="InitializationFailed">
<source>Failed to initialize client proxy: could not connect to test process.</source>
<note></note>
</trans-unit>
<trans-unit id="LaunchDebugProcessNotAllowedForANonDebugRun">
<source>This operation is not allowed in the context of a non-debug run.</source>
<note></note>
</trans-unit>
<trans-unit id="NoMatchingExecutor">
<source>Could not find test executor with URI '{0}'. Make sure that the test executor is installed and supports .net runtime version {1}.</source>
<note>{0} - Executor uri String {1}- Version - .net Version Eg:-2.0.50727.00</note>
</trans-unit>
<trans-unit id="NoValidSourceFoundForDiscovery">
<source>None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again. </source>
<note></note>
</trans-unit>
<trans-unit id="StringSeperator">
<source>, </source>
<note></note>
</trans-unit>
<trans-unit id="UnsupportedPropertiesInTestCaseFilter">
<source>No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).</source>
<note></note>
</trans-unit>
<trans-unit id="NoDotnetExeFound">
<source>Could not find {0}. Make sure that the dotnet is installed on the machine.</source>
<target state="new">Could not find {0}. Make sure that the dotnet is installed on the machine.</target>
<note></note>
</trans-unit>
<trans-unit id="TestHostExitedWithError">
<source>Testhost process for source(s) '{0}' exited with error: {1}. Please check the diagnostic logs for more information.</source>
<target state="new">Testhost process exited with error: {0}</target>
<note>{0} a source, or very rarely list of sources, {1} the output error.</note>
</trans-unit>
<trans-unit id="DataCollectorDebuggerWarning">
<source>DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.</source>
<target state="new">DataCollector debugging is enabled. Please attach debugger to testhost process to continue.</target>
<note></note>
</trans-unit>
<trans-unit id="TestRunFailed_NoDiscovererFound_NoTestsAreAvailableInTheSources">
<source>No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.</source>
<target state="new">No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.</target>
<note></note>
</trans-unit>
<trans-unit id="TesthostDiagLogOutputFile">
<source>Logging TestHost Diagnostics in file: {0}</source>
<target state="new">Logging TestHost Diagnostics in file: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="FailedToLaunchTestHost">
<source>Failed to launch testhost with error: {0}</source>
<target state="new">Failed to launch testhost with error: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="ExecutionThreadApartmentStateNotSupportedForFramework">
<source>ExecutionThreadApartmentState option not supported for framework: {0}.</source>
<target state="new">ExecutionThreadApartmentState option not supported for framework: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="OldTestHostIsGettingUsed">
<source>You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.</source>
<target state="new">You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0</target>
<note></note>
</trans-unit>
<trans-unit id="NonExistingExtensions">
<source>Could not find extensions: {0}</source>
<target state="new">Could not find extensions: {0}</target>
<note></note>
</trans-unit>
<trans-unit id="DeprecatedAdapterPath">
<source>Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/main/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.</source>
<target state="new">Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/main/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.</target>
<note></note>
</trans-unit>
<trans-unit id="NoTestsAvailableForGivenTestCaseFilter">
<source>No test matches the given testcase filter `{0}` in {1}</source>
<target state="new">No test is available for testcase filter `{0}` in {1}</target>
<note></note>
</trans-unit>
<trans-unit id="TestDiscoveryCancelled">
<source>Discovery of tests cancelled.</source>
<target state="new">Discovery of tests cancelled.</target>
<note></note>
</trans-unit>
<trans-unit id="AttachDebuggerToDefaultTestHostFailure">
<source>Cannot attach the debugger to the default test host with process ID: {0}.</source>
<target state="new">Cannot attach the debugger to the default test host with process ID: {0}.</target>
<note></note>
</trans-unit>
<trans-unit id="AccessDenied">
<source>{0} Access denied while trying to create "TestResults" folder in mentioned location. You are getting this exception because you are running vstest.console.exe from a folder which requires having write access. To solve the issue: please run vstest.console.exe from a folder where you have write privileges.</source>
<target state="new">{0} Access denied while trying to create "TestResults" folder in mentioned location. You are getting this exception because you are running vstest.console.exe from a folder which requires having write access. To solve the issue: please run vstest.console.exe from a folder where you have write privileges. For more information, please look at the error message:</target>
<note></note>
</trans-unit>
<trans-unit id="NoAvailableProxyForDeque">
<source>Could not find an available proxy to deque.</source>
<target state="new">Could not find an available proxy to deque.</target>
<note></note>
</trans-unit>
<trans-unit id="NoSuchProxyId">
<source>Proxy with id {0} is not managed by the current session manager.</source>
<target state="new">Proxy with id {0} is not managed by the current session manager.</target>
<note></note>
</trans-unit>
<trans-unit id="ProxyIsAlreadyAvailable">
<source>Proxy with id {0} is already available and cannot be re-enqueued.</source>
<target state="new">Proxy with id {0} is already available and cannot be re-enqueued.</target>
<note></note>
</trans-unit>
<trans-unit id="NoTestHostProviderFound">
<source>No suitable test runtime provider was found for any source in this run.</source>
<target state="new">No suitable test runtime provider found for this run.</target>
<note></note>
</trans-unit>
<trans-unit id="NoProxyMatchesDescription">
<source>The runsettings changed between the time when the test session was established and the time of the current run/discovery request.</source>
<target state="new">Could not find an available proxy to match the original run settings.</target>
<note></note>
</trans-unit>
<trans-unit id="AttachmentOutputFormat">
<source> {0}</source>
<target state="new">{0}</target>
<note></note>
</trans-unit>
<trans-unit id="AttachmentsBanner">
<source>Attachments:</source>
<target state="new">Attachments:</target>
<note></note>
</trans-unit>
<trans-unit id="NoSuitableRuntimeProviderFound">
<source>No suitable test runtime provider was found:</source>
<target state="new">No suitable test runtime provider was found:</target>
<note></note>
</trans-unit>
<trans-unit id="SkippingSource">
<source>Skipping source:</source>
<target state="new">Skipping source:</target>
<note></note>
</trans-unit>
</body>
</file>
</xliff>