diff --git a/scripts/build.ps1 b/scripts/build.ps1
index 3b2c582554..6fc449f54c 100644
--- a/scripts/build.ps1
+++ b/scripts/build.ps1
@@ -759,6 +759,7 @@ function Create-VsixPackage
$testPlatformExternalsVersion = ([xml](Get-Content $env:TP_ROOT_DIR\scripts\build\TestPlatform.Dependencies.props)).Project.PropertyGroup.TestPlatformExternalsVersion
$testPlatformMsDiaVersion = ([xml](Get-Content $env:TP_ROOT_DIR\scripts\build\TestPlatform.Dependencies.props)).Project.PropertyGroup.TestPlatformMSDiaVersion
$codeCoverageExternalsVersion = ([xml](Get-Content $env:TP_ROOT_DIR\scripts\build\TestPlatform.Dependencies.props)).Project.PropertyGroup.CodeCoverageExternalsVersion
+ $vsWebSiteInteropVersion = ([xml](Get-Content $env:TP_ROOT_DIR\scripts\build\TestPlatform.Dependencies.props)).Project.PropertyGroup.VsWebSiteInteropVersion
# Copy Microsoft.VisualStudio.TraceDataCollector to Extensions
$traceDataCollectorPackageDirectory = Join-Path $env:TP_PACKAGES_DIR "Microsoft.VisualStudio.TraceDataCollector\$codeCoverageExternalsVersion\lib\$TPB_TargetFramework472"
@@ -816,7 +817,7 @@ function Create-VsixPackage
Copy-Item -Recurse $internalDiaInterop\* $packageDir -Force
# Copy VsWebSite.Interop
- $vsWebSiteInterop = Join-Path $env:TP_PACKAGES_DIR "VsWebSite.Interop\$testPlatformExternalsVersion\lib\net45"
+ $vsWebSiteInterop = Join-Path $env:TP_PACKAGES_DIR "VsWebSite.Interop\$vsWebSiteInteropVersion\lib\net45"
Copy-Item -Recurse $vsWebSiteInterop\* $packageDir -Force
# Copy COM Components and their manifests over to Extensions Test Impact directory
diff --git a/scripts/build/TestPlatform.Dependencies.props b/scripts/build/TestPlatform.Dependencies.props
index ac49c3940f..2e85f6aa0a 100644
--- a/scripts/build/TestPlatform.Dependencies.props
+++ b/scripts/build/TestPlatform.Dependencies.props
@@ -33,8 +33,9 @@
9.0.14.7.63
- 16.11.31527.49
- 16.11.31523.174
+ 16.11.31528.385
+ 16.11.31528.385
+ 16.11.31527.4916.10.0-beta.21270.216.11.230815
diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.cs.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.cs.xlf
index cfcbf205b2..85d86292da 100644
--- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.cs.xlf
+++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.cs.xlf
@@ -5,32 +5,27 @@
An exception occurred while collecting final entries from the event log '{0}': {1}Došlo k výjimce při shromažďování finálních položek z protokolu událostí {0}: {1}
-
-
+ Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0}DataCollector pro protokol událostí nenašel eventLogContext pro DataCollectionContext: {0}
-
-
+ The '{0}' event log may have been cleared during collection; some events may not have been collectedProtokol událostí {0} byl pravděpodobně při shromažďování vyčištěn. Některé události nemusely být shromážděny.
-
-
+ Unable to read event log '{0}' from computer '{1}'Nepodařilo se přečíst protokol událostí {0} z počítače {1}
-
-
+ The '{0}' event log has encountered an exception, some events might get lost. Error : {1}U protokolu událostí {0} došlo k výjimce. Některé události se mohly ztratit. Chyba: {1}
-
-
+
The test run could not be executed because the initial state was invalid.
-
-
+ Testovací běh nešlo spustit, protože byl neplatný počáteční stav.Wait for completion operation is not allowed when there is no active test run.
-
-
+ V případě, že nejsou aktivní žádné testovací běhy, se operace čekání na dokončení nepovoluje. Aborting test run: test run timeout of {0} milliseconds exceeded.Testovací běh se ruší: byl překročen časový limit testovacího běhu ({0} ms).
-
-
+ No suitable test runtime provider found for this run.Pro tento běh se nenašel žádný vhodný zprostředkovatel testů v režimu runtime.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ Der Testlauf konnte nicht ausgeführt werden, weil der Anfangszustand ungültig war.Wait for completion operation is not allowed when there is no active test run.
-
-
+ Das Warten auf den Fertigstellungsvorgang ist unzulässig, wenn kein aktiver Testlauf vorhanden ist. Aborting test run: test run timeout of {0} milliseconds exceeded.Der Testlauf wird abgebrochen: Das Timeout von {0} Millisekunden für den Testlauf wurde überschritten.
-
-
+ No suitable test runtime provider found for this run.Für diese Ausführung wurde kein geeigneter Testlaufzeitanbieter gefunden.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ No se pudo ejecutar la serie de pruebas porque el estado inicial no era válido.Wait for completion operation is not allowed when there is no active test run.
-
-
+ La operación “Esperar que termine” no se permite cuando no hay ninguna serie de pruebas activa. Aborting test run: test run timeout of {0} milliseconds exceeded.Anulando la serie de pruebas: se superó el tiempo de espera de {0} milisegundos para la serie de pruebas.
-
-
+ No suitable test runtime provider found for this run.No se encontró un proveedor de tiempo de ejecución de prueba adecuado para esta ejecución.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ Impossible d'exécuter la série de tests, car l'état initial est non valide.Wait for completion operation is not allowed when there is no active test run.
-
-
+ L'attente de la fin de l'exécution d'une opération n'est pas autorisée quand il n'existe aucune série de tests active. Aborting test run: test run timeout of {0} milliseconds exceeded.Abandon de la série de tests : dépassement du délai d'expiration de la série de tests fixé à {0} millisecondes.
-
-
+ No suitable test runtime provider found for this run.Aucun fournisseur d'exécution de tests approprié n'a été trouvé pour cette série.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ Non è stato possibile completare l'esecuzione dei test perché lo stato iniziale non era valido.Wait for completion operation is not allowed when there is no active test run.
-
-
+ L'operazione di attesa completamento non è consentita se non sono presenti esecuzioni dei test attive. Aborting test run: test run timeout of {0} milliseconds exceeded.Interruzione dell'esecuzione dei test: è stato superato il timeout dell'esecuzione dei test, pari a {0} millisecondi.
-
-
+ No suitable test runtime provider found for this run.Non è stato trovato alcun provider di runtime dei test adatto per questa esecuzione.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ 初期状態が無効なため、テストの実行を実行できませんでした。Wait for completion operation is not allowed when there is no active test run.
-
-
+ アクティブなテストの実行がない場合、完了の待機操作は許可されません。Aborting test run: test run timeout of {0} milliseconds exceeded.テストの実行を中止しています: テスト実行のタイムアウト {0} ミリ秒を超過しました。
-
-
+ No suitable test runtime provider found for this run.この実行に対して適切なテスト ランタイム プロバイダーが見つかりませんでした。
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ 초기 상태가 잘못되어 테스트 실행을 실행할 수 없습니다.Wait for completion operation is not allowed when there is no active test run.
-
-
+ 활성 테스트 실행이 없으면 완료 작업을 대기할 수 없습니다. Aborting test run: test run timeout of {0} milliseconds exceeded.테스트 실행 중단 중: 테스트 실행 시간 제한 {0}밀리초가 초과되었습니다.
-
-
+ No suitable test runtime provider found for this run.이 실행에 적합한 테스트 런타임 공급자를 찾지 못했습니다.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ Nie można wykonać przebiegu testu, ponieważ stan początkowy jest nieprawidłowy.Wait for completion operation is not allowed when there is no active test run.
-
-
+ Oczekiwanie na operację zakończenia nie jest dozwolone, gdy nie ma aktywnego przebiegu testu. Aborting test run: test run timeout of {0} milliseconds exceeded.Przerywanie przebiegu testu: przekroczono limit czasu dla przebiegu testu równy {0}.
-
-
+ No suitable test runtime provider found for this run.Nie znaleziono odpowiedniego dostawcy testowego środowiska uruchomieniowego dla tego uruchomienia.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ A execução de teste não pôde ser realizada porque o estado inicial era inválido.Wait for completion operation is not allowed when there is no active test run.
-
-
+ A operação esperar conclusão não é permitida quando não há nenhuma execução de teste ativa. Aborting test run: test run timeout of {0} milliseconds exceeded.Anulando a execução de teste: o tempo limite da execução de teste de {0} milissegundos foi excedido.
-
-
+ No suitable test runtime provider found for this run.Nenhum provedor de runtime de teste encontrado para esta execução.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ Не удалось выполнить тестовый запуск из-за недопустимого начального состояния.Wait for completion operation is not allowed when there is no active test run.
-
-
+ Операция "Ожидать завершения" запрещена, если нет активного тестового запуска.Aborting test run: test run timeout of {0} milliseconds exceeded.Тестовый запуск отменяется: превышено допустимое время ожидания в {0} мс.
-
-
+ No suitable test runtime provider found for this run.Не найден подходящий поставщик среды выполнения теста для этого запуска.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ İlk durum geçersiz olduğundan test çalıştırması yürütülemedi.Wait for completion operation is not allowed when there is no active test run.
-
-
+ Etkin bir test çalıştırması olmadığında tamamlanmasını bekleme işlemine izin verilmez. Aborting test run: test run timeout of {0} milliseconds exceeded.Test çalıştırması durduruluyor: Test çalıştırması için {0} milisaniyelik zaman aşımına ulaşıldı.
-
-
+ No suitable test runtime provider found for this run.Bu çalıştırma için uygun bir test çalışma zamanı sağlayıcısı yok.
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ 由于初始状态无效,无法执行测试运行。Wait for completion operation is not allowed when there is no active test run.
-
-
+ 没有活动的测试运行时不允许等待完成操作。Aborting test run: test run timeout of {0} milliseconds exceeded.中止测试运行: 测试运行超时时间超出 {0} 毫秒。
-
-
+ No suitable test runtime provider found for this run.对于此运行,未找到适合的测试运行时提供程序。
-
-
+ The test run could not be executed because the initial state was invalid.
-
-
+ 因為初始狀態無效,所以無法執行測試回合。Wait for completion operation is not allowed when there is no active test run.
-
-
+ 沒有使用中的測試回合時,不允許等候完成作業。Aborting test run: test run timeout of {0} milliseconds exceeded.正在中止測試回合: 超過了測試回合逾時 ({0} 毫秒)。
-
-
+ No suitable test runtime provider found for this run.找不到適用於此回合的測試執行階段提供者。
-
-
+ Data collection : {0}
-
-
+ Shromažďování dat: {0}Data collector '{0}' message: {1}.
-
-
+ Zpráva kolekce dat {0}: {1}Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ Duplicitní identifikátor URI testu rozšíření {0}. Duplicitní rozšíření se ignoruje.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Duplicitní poskytovatel nastavení s názvem {0}. Duplicitní poskytovatel se ignoruje.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Našel se duplicitní oddíl nastavení běhu s názvem {0}. Duplicitní nastavení se ignoruje.Error: Empty parenthesis ( )
-
-
+ Chyba: Prázdné závorky ( )Error: Invalid Condition '{0}'
-
-
+ Chyba: Neplatná podmínka {0}Test Extension has an invalid URI '{0}': {1}
-
-
+ Rozšíření testu má neplatný identifikátor URI {0}: {1}Error: Invalid operator '{0}'
-
-
+ Chyba: Neplatný operátor {0}Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Během inicializace protokolovače s {0}: {1} došlo k výjimce. Protokolovač se nepoužije. Výjimka: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Nepovedlo se najít protokolovač testu s kvalifikovaným názvem sestavení (AssemblyQualifiedName), identifikátorem URI (uri) nebo popisným názvem (FriendlyName) {0}.Error: Missing ')'
-
-
+ Chyba: Chybí ).Error: Missing '('
-
-
+ Chyba: Chybí (.Error: Missing operand
-
-
+ Chyba: Chybí operand.Missing Operator '|' or '&'
-
-
+ Chybějící operátor | nebo &The Run Settings have already been loaded.
-
-
+ Parametry spouštění jsou už načtené.An error occurred while loading the run settings. Error: {0}
-
-
+ Při načítání parametrů spouštění se stala chyba. Chyba: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Zadal se neplatný uzel nastavení. Vlastnost name uzlu nastavení nesmí být prázdná.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Při inicializaci poskytovatele nastavení s názvem {0} se stala chyba. Chyba: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Poskytovatel nastavení s názvem {0} se nenašel. Nastavení nešlo načíst.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Nesprávný formát pro TestCaseFilter {0}. Zadejte správný formát a zkuste to znovu. Poznámka: Nesprávný formát může vést k tomu, že se nespustí žádný test.Data collector '{0}' failed to provide initialization information. Error: {1}Kolekce dat {0} neposkytla informace o inicializaci. Chyba: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.Kolekce dat {0} během načítání typu, konstrukce nebo inicializace vyvolala výjimku: {1}
-
-
+ Could not find data collector '{0}'Nepovedlo se najít kolekci dat {0}.
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.Kolekce dat {0} si v prostředí provedení testu vyžádala nastavení proměnné prostředí {1} na hodnotu {2}, ale jiná kolekce dat {3} si už vyžádala stejnou proměnnou prostředí s rozdílnou hodnotou {4}.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Existuje více konfigurací, které mají popisný název kolekce dat {0}. Duplicitní konfigurace se budou v testovacím běhu ignorovat.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.Kolekce dat zachytila výjimku typu {0}: {1}. Další podrobnosti: {2}
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Typy odvozené z kontextu shromažďování dat nelze použít pro posílání zpráv a dat. DataCollectionContext použitý pro posílání dat a zpráv musí pocházet z jedné z událostí vyvolaných na kolekci dat.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.Identifikátor URI {0} protokolovače testu není platný. Protokolovač testu se bude ignorovat.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Nepovedlo se najít seznam nainstalovaných rozšíření testu jednotek. Důvod: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Tato možnost funguje jenom se souborem vstest.console.exe nainstalovaným jako součást sady Visual Studio.
-
-
+ An error occurred while creating Fast filter.Při vytváření rychlého filtru došlo k chybě.
-
-
+ Cancelling the operation as requested.Operace se ruší na základě žádosti.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Nepovedlo se najít datacollector s popisným názvem {0}.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Nepovedlo se načíst rozšíření ze souboru {0}. Další informace získáte pomocí parametru /diag.
-
-
+ {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:{0} Při pokusu o vytvoření složky TestResults v uvedeném umístění došlo k odepření přístupu. Tato výjimka se vyvolala, protože spouštíte vstest.console.exe ze složky, která vyžaduje, abyste měli přístup pro zápis. Pokud chcete problém vyřešit, spusťte prosím vstest.console.exe ze složky, ve které máte oprávnění k zápisu. Další informace najdete v chybové zprávě:
-
-
+ Inner exception:Vnitřní výjimka:
-
-
+ Stack trace:Trasování zásobníku:
-
-
+ Data collection : {0}
-
-
+ Datensammlung: {0}Data collector '{0}' message: {1}.
-
-
+ Datensammler "{0}" – Meldung: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ Doppelter Testerweiterungs-URI "{0}". Die doppelte Erweiterung wird ignoriert.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Doppelter Einstellungsanbieter namens "{0}". Der doppelte Anbieter wird ignoriert.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Duplizierter Abschnitt mit Ausführungseinstellungen "{0}". Die Einstellungsduplikate werden ignoriert.Error: Empty parenthesis ( )
-
-
+ Fehler: Leere Klammern ( )Error: Invalid Condition '{0}'
-
-
+ Fehler: Ungültige Bedingung "{0}".Test Extension has an invalid URI '{0}': {1}
-
-
+ Die Testerweiterung weist einen ungültigen URI "{0}" auf: {1}Error: Invalid operator '{0}'
-
-
+ Fehler: Ungültiger Operator "{0}".Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Ausnahme beim Initialisieren der Protokollierung mit "{0}": "{1}". Die Protokollierung wird nicht verwendet. Ausnahme: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Es wurde keine Testprotokollierung mit AssemblyQualifiedName, URI oder FriendlyName "{0}" gefunden.Error: Missing ')'
-
-
+ Fehler: Fehlende Klammer ")"Error: Missing '('
-
-
+ Fehler: Fehlende Klammer "("Error: Missing operand
-
-
+ Fehler: Fehlender Operand.Missing Operator '|' or '&'
-
-
+ Operator "|" oder "&" fehltThe Run Settings have already been loaded.
-
-
+ Die Laufzeiteinstellungen wurden bereits geladen.An error occurred while loading the run settings. Error: {0}
-
-
+ Fehler beim Laden der Laufzeiteinstellungen. Fehler: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Es wurde ein ungültiger Einstellungsknoten angegebenen. Die Eigenschaft "name" eines Einstellungsknotens darf nicht leer sein.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Fehler beim Initialisieren des Einstellungsanbieters namens "{0}". Fehler: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Der Einstellungsanbieter namens "{0}" wurde nicht gefunden. Die Einstellungen können nicht geladen werden.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Ungültiges Format für TestCaseFilter {0}. Geben Sie das richtige Format an, und versuchen Sie es erneut. Beachten Sie, dass das falsche Format dazu führen kann, dass kein Test ausgeführt wird.Data collector '{0}' failed to provide initialization information. Error: {1}Vom Datensammler "{0}" wurden keine Initialisierungsinformationen bereitgestellt. Fehler: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.Der Datensammler "{0}" hat beim Laden, bei der Konstruktion oder bei der Initialisierung des Typs eine Ausnahme ausgelöst: {1}.
-
-
+ Could not find data collector '{0}'Datensammler "{0}" wurde nicht gefunden
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.Der Datensammler "{0}" hat das Festlegen der Umgebungsvariablen "{1}" mit dem Wert "{2}" in der Testausführungsumgebung angefordert, ein anderer Datensammler "{3}" hat jedoch die gleiche Umgebungsvariable mit dem anderen Wert "{4}" angefordert.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Es gibt mehrere Konfigurationen mit dem Datensammler-FriendlyName "{0}". Doppelte Konfigurationen werden beim Testlauf ignoriert.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.Der Datensammler hat eine Ausnahme vom Typ "{0}" aufgefangen: "{1}". Weitere Informationen: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Typen, die vom Datensammlungskontext abgeleitet werden, können nicht zum Senden von Daten und Meldungen verwendet werden. Der DataCollectionContext für das Senden von Daten und Meldungen muss aus einem der Ereignisse stammen, die für den Datensammler ausgelöst wurden.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.Der Testprotokollierungs-URI "{0}" ist ungültig. Die Testprotokollierung wird ignoriert.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Die Liste installierter Komponententesterweiterungen wurde nicht gefunden. Ursache: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Diese Option funktioniert nur, wenn "vstest.console.exe" als Teil von Visual Studio installiert wurde.
-
-
+ An error occurred while creating Fast filter.Fehler beim Erstellen eines Schnellfilters.
-
-
+ Cancelling the operation as requested.Der Vorgang wird gemäß Anforderung abgebrochen.
-
-
+ Unable to find a datacollector with friendly name '{0}'.datacollector mit dem Anzeigenamen "{0}" wurde nicht gefunden.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Fehler beim Laden von Erweiterungen aus der Datei "{0}". Verwenden Sie "/diag", um weitere Informationen zu erhalten.
-
-
+ {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:{0} Beim Erstellen des Ordners "TestResults" am angegebenen Speicherort wurde der Zugriff verweigert. Sie erhalten diese Ausnahme, weil Sie "vstest.console.exe" von einem Ordner aus ausführen, für den Schreibzugriff erforderlich ist. So beheben Sie das Problem: Führen Sie "vstest.console.exe" in einem Ordner aus, für den Sie Schreibberechtigungen besitzen. Weitere Informationen finden Sie in der Fehlermeldung:
-
-
+ Inner exception:Innere Ausnahme:
-
-
+ Stack trace:Stapelüberwachung:
-
-
+ Data collection : {0}
-
-
+ Recopilación de datos: {0}Data collector '{0}' message: {1}.
-
-
+ Mensaje del recopilador de datos "{0}": {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ URI de extensión de pruebas duplicado ({0}). Se omitirá la extensión duplicada.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Proveedor de configuración duplicado con el nombre '{0}'. Se omitirá el proveedor duplicado.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Sección de parámetros de ejecución duplicada con el nombre "{0}". Se omitirán los parámetros duplicados.Error: Empty parenthesis ( )
-
-
+ Error: Paréntesis vacío ( )Error: Invalid Condition '{0}'
-
-
+ Error: Condición '{0}' no válidaTest Extension has an invalid URI '{0}': {1}
-
-
+ La extensión de pruebas tiene un URI no válido ({0}): {1}Error: Invalid operator '{0}'
-
-
+ Error: Operador no válido ({0})Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Se produjo una excepción al inicializar el registrador con {0}: "{1}". No se usará el registrador. Excepción: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ No se encuentra ningún registrador de pruebas con AssemblyQualifiedName, URI o FriendlyName "{0}".Error: Missing ')'
-
-
+ Error: Falta ')'Error: Missing '('
-
-
+ Error: Falta '('Error: Missing operand
-
-
+ Error: Falta un operandoMissing Operator '|' or '&'
-
-
+ Falta el operador "|" o "&"The Run Settings have already been loaded.
-
-
+ Los parámetros de ejecución ya se han cargado.An error occurred while loading the run settings. Error: {0}
-
-
+ Error al cargar los parámetros de ejecución. Error: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Se especificó un nodo de configuración no válido. La propiedad de nombre del nodo de configuración no debe estar vacía.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Error al inicializar el proveedor de configuración '{0}'. Error: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ No se encuentra el proveedor de configuración '{0}'. No se puede cargar la configuración.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Formato incorrecto de TestCaseFilter {0}. Especifique el formato correcto y vuelva a intentarlo. Tenga en cuenta que un formato incorrecto puede dar lugar a que no se ejecute ninguna prueba.Data collector '{0}' failed to provide initialization information. Error: {1}El recopilador de datos "{0}" no pudo proporcionar información de inicialización. Error: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.El recopilador de datos "{0}" produjo una excepción durante la carga, creación o inicialización del tipo: {1}.
-
-
+ Could not find data collector '{0}'No se pudo encontrar el recopilador de datos "{0}"
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.El recopilador de datos "{0}" solicitó que la variable de entorno "{1}" con el valor "{2}" se estableciera en el entorno de ejecución de pruebas, pero otro recopilador de datos "{3}" ya ha solicitado la misma variable de entorno con otro valor "{4}".
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Hay varias configuraciones que tienen el nombre descriptivo del recopilador de datos "{0}". Se omitirán las configuraciones duplicadas en la serie de pruebas.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.El recopilador de datos detectó una excepción de tipo "{0}": "{1}". Más detalles: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Los tipos derivados del contexto de recolección de datos no se pueden usar para enviar datos y mensajes. El elemento DataCollectionContext usado para enviar datos y mensajes debe proceder de alguno de los eventos generados para el recolector de datos.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.El URI de registrador de pruebas '{0}' no es válido. Se omitirá el registrador de pruebas.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}No se pudo encontrar la lista de extensiones de prueba unitaria instaladas. Motivo: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Esta opción funciona solo con vstest.console.exe instalado como parte de Visual Studio.
-
-
+ An error occurred while creating Fast filter.Error al crear el filtro rápido.
-
-
+ Cancelling the operation as requested.La operación se cancelará como se ha solicitado.
-
-
+ Unable to find a datacollector with friendly name '{0}'.No se encuentra ningún objeto datacollector con el nombre descriptivo "{0}".
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.No se pudieron cargar las extensiones del archivo "{0}". Use /diag para obtener más información.
-
-
+ {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:{0} Se denegó el acceso al intentar crear la carpeta "TestResults" en la ubicación mencionada. Está recibiendo esta excepción porque está ejecutando vstest.console.exe desde una carpeta que requiere acceso de escritura. Para solucionar el problema: ejecute vstest.console.exe desde una carpeta en la que tenga privilegios de escritura. Para obtener más información, consulte el mensaje de error:
-
-
+ Inner exception:Excepción interna:
-
-
+ Stack trace:Seguimiento de la pila:
-
-
+ Data collection : {0}
-
-
+ Collecte de données : {0}Data collector '{0}' message: {1}.
-
-
+ Message du collecteur de données '{0}' : {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ L'URI d'extension de test '{0}' est dupliquée. L'extension dupliquée est ignorée.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Le fournisseur de paramètres nommé '{0}' est dupliqué. Le fournisseur dupliqué est ignoré.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ La section de paramètres d'exécution nommée '{0}' est dupliquée. Les paramètres dupliqués sont ignorés.Error: Empty parenthesis ( )
-
-
+ Erreur : parenthèses vides ( )Error: Invalid Condition '{0}'
-
-
+ Erreur : condition non valide '{0}'Test Extension has an invalid URI '{0}': {1}
-
-
+ L'URI d'extension de test est non valide '{0}' : {1}Error: Invalid operator '{0}'
-
-
+ Erreur : opérateur non valide '{0}'Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Une exception s'est produite durant l'initialisation de l'enregistreur d'événements avec {0} : '{1}'. L'enregistreur d'événements ne sera pas utilisé. Exception : {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Impossible de localiser un enregistreur d'événements de test ayant pour AssemblyQualifiedName, URI ou FriendlyName '{0}'.Error: Missing ')'
-
-
+ Erreur : ')' manquanteError: Missing '('
-
-
+ Erreur : '(' manquanteError: Missing operand
-
-
+ Erreur : opérande manquantMissing Operator '|' or '&'
-
-
+ Opérateur manquant '|' ou '&'The Run Settings have already been loaded.
-
-
+ Les paramètres d'exécution ont déjà été chargés.An error occurred while loading the run settings. Error: {0}
-
-
+ Une erreur s'est produite durant le chargement des paramètres d'exécution. Erreur : {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Le nœud de paramètres spécifié est non valide. La propriété name du nœud de paramètres ne doit pas être vide.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Une erreur s'est produite durant l'initialisation du fournisseur de paramètres nommé '{0}'. Erreur : {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Le fournisseur de paramètres nommé '{0}' est introuvable. Impossible de charger les paramètres.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Format incorrect pour le TestCaseFilter {0}. Spécifiez le format approprié, puis réessayez. Notez que si le format est incorrect, aucun test n'est exécuté.Data collector '{0}' failed to provide initialization information. Error: {1}Le collecteur de données '{0}' n'a pas pu fournir les informations d'initialisation. Erreur : {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.Le collecteur de données '{0}' a levé une exception pendant le chargement, la construction ou l'initialisation du type : {1}.
-
-
+ Could not find data collector '{0}'Collecteur de données '{0}' introuvable
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.Le collecteur de données '{0}' exige que la variable d'environnement '{1}' avec la valeur '{2}' soit définie dans un environnement d'exécution de test, mais un autre collecteur de données '{3}' a déjà exigé la même variable d'environnement avec une autre valeur '{4}'.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Plusieurs configurations ont comme FriendlyName de collecteur de données '{0}'. Les configurations dupliquées seront ignorées dans la série de tests.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.Le collecteur de données a intercepté une exception de type '{0}' : '{1}'. Plus de détails : {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Impossible d'utiliser les types qui dérivent du contexte de collecte de données pour envoyer des données et des messages. La valeur DataCollectionContext utilisée pour envoyer des données et des messages doit provenir de l'un des événements déclenchés par le collecteur de données.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.L'URI de l'enregistreur d'événements de tests '{0}' est non valide. L'enregistreur d'événements de tests va être ignoré.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}La liste des extensions de test unitaire installées est introuvable. Raison : {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Cette option fonctionne uniquement si vstest.console.exe est installé dans le cadre de Visual Studio.
-
-
+ An error occurred while creating Fast filter.Une erreur s'est produite durant la création du filtre rapide.
-
-
+ Cancelling the operation as requested.Annulation de l'opération, comme demandé.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Le datacollector ayant le nom convivial '{0}' est introuvable.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Le chargement des extensions à partir du fichier '{0}' a échoué. Pour plus d'informations, utilisez /diag.
-
-
+ {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:{0} Accès refusé durant la tentative de création du dossier "TestResults" à l'emplacement indiqué. Vous obtenez cette exception, car vous exécutez vstest.console.exe à partir d'un dossier qui nécessite un accès en écriture. Pour résoudre le problème, exécutez vstest.console.exe à partir d'un dossier sur lequel vous disposez de privilèges d'accès en écriture. Pour plus d'informations, consultez le message d'erreur :
-
-
+ Inner exception:Exception interne :
-
-
+ Stack trace:Arborescence des appels de procédure :
-
-
+ Data collection : {0}
-
-
+ Raccolta dei dati: {0}Data collector '{0}' message: {1}.
-
-
+ Messaggio '{0}' dell'agente di raccolta dati: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ L'URI dell'estensione di test '{0}' è duplicato. L'estensione duplicata verrà ignorata.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Il provider di impostazioni denominato '{0}' è duplicato. Il provider duplicato verrà ignorato.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ La sezione delle impostazioni esecuzione test denominata '{0}' è duplicata. Le impostazioni duplicate verranno ignorate.Error: Empty parenthesis ( )
-
-
+ Errore: parentesi vuote ( )Error: Invalid Condition '{0}'
-
-
+ Errore: condizione non valida '{0}'Test Extension has an invalid URI '{0}': {1}
-
-
+ L'URI '{0}' dell'estensione di test non è valido: {1}Error: Invalid operator '{0}'
-
-
+ Errore: operatore non valido '{0}'Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Si è verificata un'eccezione durante l'inizializzazione del logger con {0}: '{1}'. Il logger non verrà usato. Eccezione: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Non è stato trovato alcun logger di test con AssemblyQualifiedName, URI o FriendlyName '{0}'.Error: Missing ')'
-
-
+ Errore: manca ')'Error: Missing '('
-
-
+ Errore: manca '('Error: Missing operand
-
-
+ Errore: manca l'operandoMissing Operator '|' or '&'
-
-
+ Manca l'operatore '|' o '&'The Run Settings have already been loaded.
-
-
+ Le impostazioni esecuzione test sono già state caricate.An error occurred while loading the run settings. Error: {0}
-
-
+ Errore durante il caricamento delle impostazioni esecuzione test. Errore: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Il nodo impostazioni specificato non è valido. La proprietà del nome del nodo impostazioni non deve essere vuota.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Si è verificato un errore durante l'inizializzazione del provider di impostazioni denominato '{0}'. Errore: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Il provider di impostazioni denominato '{0}' non è stato trovato. Non è possibile caricare le impostazioni.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Il formato per TestCaseFilter {0} non è corretto. Specificare il formato corretto e riprovare. Se il formato non è corretto, potrebbe non essere eseguito alcun test.Data collector '{0}' failed to provide initialization information. Error: {1}L'agente di raccolta dati '{0}' non ha fornito le informazioni di inizializzazione. Errore: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.L'agente di raccolta dati '{0}' ha generato un'eccezione durante la costruzione, l'inizializzazione o il caricamento dei tipi: {1}.
-
-
+ Could not find data collector '{0}'L'agente di raccolta dati '{0}' non è stato trovato
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.L'agente di raccolta dati '{0}' ha richiesto che la variabile di ambiente '{1}' con valore '{2}' fosse impostata nell'ambiente di esecuzione dei test, ma un altro agente di raccolta dati '{3}' ha già richiesto la stessa variabile di ambiente con un valore diverso '{4}'.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Sono presenti più configurazioni in cui il nome descrittivo dell'agente di raccolta dati è '{0}'. Le configurazioni duplicate verranno ignorate nell'esecuzione dei test.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.L'agente di raccolta dati ha rilevato un'eccezione di tipo '{0}': '{1}'. Altri dettagli: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Non è possibile usare i tipi che derivano da DataCollectionContext per inviare dati e messaggi. L'elemento DataCollectionContext usato per inviare dati e messaggi deve provenire da uno degli eventi generati per l'agente di raccolta dati.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.L'URI del logger di test '{0}' non è valido. Il logger di test verrà ignorato.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}L'elenco delle estensioni degli unit test installate non è stato trovato. Motivo: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Questa opzione funziona solo se vstest.console.exe è installato con Visual Studio.
-
-
+ An error occurred while creating Fast filter.Si è verificato un errore durante la creazione del filtro Fast.
-
-
+ Cancelling the operation as requested.L'operazione verrà annullata come richiesto.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Non è possibile trovare un oggetto datacollector con nome descrittivo '{0}'.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Non è stato possibile caricare le estensioni dal file '{0}'. Per altre informazioni, usare /diag.
-
-
+ {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:{0} Accesso negato durante il tentativo di creare la cartella "TestResults" nel percorso indicato. Si riceve questa eccezione perché si esegue vstest.console.exe da una cartella per cui è necessario l'accesso in scrittura. Per risolvere il problema, eseguire vstest.console.exe da una cartella per cui si hanno privilegi di scrittura. Per altre informazioni, vedere il messaggio di errore:
-
-
+ Inner exception:Eccezione interna:
-
-
+ Stack trace:Analisi dello stack:
-
-
+ Data collection : {0}
-
-
+ データ コレクション : {0}Data collector '{0}' message: {1}.
-
-
+ データ コレクター '{0}' メッセージ: {1}。Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ テスト拡張 URI '{0}' は重複しています。重複する拡張を無視しています。Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ '{0}' という名前の設定プロバイダーが重複しています。重複するプロバイダーを無視しています。Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ '{0}' という名前の重複した実行設定セクションが見つかりました。重複する設定を無視しています。Error: Empty parenthesis ( )
-
-
+ エラー: かっこ ( ) が空ですError: Invalid Condition '{0}'
-
-
+ エラー: 条件 '{0}' が無効ですTest Extension has an invalid URI '{0}': {1}
-
-
+ テスト拡張に無効な URI '{0}' があります: {1}Error: Invalid operator '{0}'
-
-
+ エラー: 演算子 '{0}' が無効ですException occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ {0}: '{1}' でのロガーの初期化中に例外が発生しました。ロガーは使用されません。例外: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ AssemblyQualifiedName、URI または FriendlyName が '{0}' のテスト ロガーは見つかりませんでした。Error: Missing ')'
-
-
+ エラー: ')' がありませんError: Missing '('
-
-
+ エラー: '(' がありませんError: Missing operand
-
-
+ エラー: オペランドがありませんMissing Operator '|' or '&'
-
-
+ 演算子 '|' または '&' がありませんThe Run Settings have already been loaded.
-
-
+ 実行設定は既に読み込まれています。An error occurred while loading the run settings. Error: {0}
-
-
+ 実行設定の読み込み中にエラーが発生しました。エラー: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ 無効な設定ノードが指定されました。設定ノードの名前プロパティを空白にしないようにしてください。An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ '{0}' という名前の設定プロバイダーを初期化中にエラーが発生しました。エラー: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ '{0}' という名前の設定プロバイダーが見つかりませんでした。設定を読み込めません。Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ TestCaseFilter {0} の形式が正しくありません。正しい形式を指定してもう一度お試しください。形式が正しくないと、テストが実行されないことがあります。Data collector '{0}' failed to provide initialization information. Error: {1}データ コレクター '{0}' で初期化情報を表示できませんでした。エラー: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.データ コレクター '{0}' が型の読み込み、作成、または初期化中に例外をスローしました: {1}。
-
-
+ Could not find data collector '{0}'データ コレクター '{0}' が見つかりませんでした
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.データ コレクター '{0}' が値 '{2}' の環境変数 '{1}' をテスト実行時環境で設定するように要求しましたが、別のデータ コレクター '{3}' が既に別の値 '{4}' を持つ同じ環境変数を要求しています。
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.データ コレクターの FriendlyName が '{0}' の構成が複数あります。テストの実行では、重複した構成は無視されます。
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.データ コレクターが型 '{0}' の例外をキャッチしました: '{1}'。詳細: {2}。
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.データ コレクション コンテキストから派生する型をデータおよびメッセージの送信に使用することはできません。データおよびメッセージの送信に使用される DataCollectionContext は、データ コレクターに対して発生したイベントの 1 つからのものである必要があります。
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.テスト ロガーの URI '{0}' は無効です。テスト ロガーは無視されます。
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}インストール済みの単体テスト拡張の一覧が見つかりませんでした。理由: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.このオプションは Visual Studio の一部として vstest.console.exe がインストールされている場合のみ使用できます。
-
-
+ An error occurred while creating Fast filter.高速フィルターを作成中にエラーが発生しました。
-
-
+ Cancelling the operation as requested.操作のキャンセルが要求されたため、キャンセルしています。
-
-
+ Unable to find a datacollector with friendly name '{0}'.フレンドリ名が '{0}' の datacollector が見つかりません。
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.ファイル '{0}' から拡張機能を読み込めませんでした。詳細な情報を得るには、/diag をご使用ください。
-
-
+ {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:{0} 記載した場所に "TestResults" フォルダーを作成しようとしたときにアクセスが拒否されました。書き込みアクセスを必要とするフォルダーから vstest.console.exe を実行しているため、この例外が発生しています。この問題を解決するには、書き込み権限のあるフォルダーから vstest.console.exe を実行してください。詳細については、次のエラー メッセージをご覧ください。
-
-
+ Inner exception:内部例外:
-
-
+ Stack trace:スタック トレース:
-
-
+ Data collection : {0}
-
-
+ 데이터 수집: {0}Data collector '{0}' message: {1}.
-
-
+ 데이터 수집기 '{0}' 메시지: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ 테스트 확장 URI '{0}'이(가) 중복됩니다. 중복 확장을 무시합니다.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ 설정 공급자 '{0}'이(가) 중복됩니다. 중복 공급자를 무시합니다.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ 중복 실행 설정 섹션 '{0}'이(가) 있습니다. 중복 설정을 무시합니다.Error: Empty parenthesis ( )
-
-
+ 오류: 빈 괄호 ( )Error: Invalid Condition '{0}'
-
-
+ 오류: 잘못된 조건 '{0}'Test Extension has an invalid URI '{0}': {1}
-
-
+ 테스트 확장의 URI '{0}'이(가) 잘못되었습니다. {1}Error: Invalid operator '{0}'
-
-
+ 오류: 잘못된 연산자 '{0}'Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ {0}: '{1}'인 로거를 초기화하는 동안 예외가 발생했습니다. 로거가 사용되지 않습니다. 예외: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ AssemblyQualifiedName, URI 또는 FriendlyName이 '{0}'인 테스트 로거를 찾을 수 없습니다.Error: Missing ')'
-
-
+ 오류: ')' 누락Error: Missing '('
-
-
+ 오류: '(' 누락Error: Missing operand
-
-
+ 오류: 피연산자 누락Missing Operator '|' or '&'
-
-
+ '|' 또는 '&' 연산자 누락The Run Settings have already been loaded.
-
-
+ 실행 설정이 이미 로드되었습니다.An error occurred while loading the run settings. Error: {0}
-
-
+ 실행 설정을 로드하는 동안 오류가 발생했습니다. 오류: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ 잘못된 설정 노드를 지정했습니다. 설정 노드의 이름 속성이 비어 있어서는 안 됩니다.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ 설정 공급자 '{0}'을(를) 초기화하는 동안 오류가 발생했습니다. 오류: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ 설정 공급자 '{0}'을(를) 찾을 수 없습니다. 설정을 로드할 수 없습니다.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ TestCaseFilter {0}의 형식이 잘못되었습니다. 올바른 형식을 지정하고 다시 시도하세요. 잘못된 형식을 사용하면 테스트가 실행되지 않을 수 있습니다.Data collector '{0}' failed to provide initialization information. Error: {1}데이터 수집기 '{0}'에서 초기화 정보를 제공하지 못했습니다. 오류: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.형식 로드, 생성 또는 초기화 중에 데이터 수집기 '{0}'에서 예외를 throw했습니다. {1}.
-
-
+ Could not find data collector '{0}'데이터 수집기 '{0}'을(를) 찾을 수 없습니다.
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.데이터 수집기 '{0}'에서 값이 '{2}'인 환경 변수 '{1}'을(를) 테스트 실행 환경에서 설정하도록 요청했는데, 다른 데이터 수집기 '{3}'이(가) 다른 값('{4}')을 포함하는 동일 환경 변수를 이미 요청했습니다.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.데이터 수집기 FriendlyName이 '{0}'인 여러 개의 구성이 있습니다. 중복 구성은 테스트 실행에서 무시됩니다.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.데이터 수집기에서 '{0}': '{1}' 형식의 예외를 catch했습니다. 자세한 정보: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.데이터 컬렉션 컨텍스트에서 파생된 형식을 사용하여 데이터 및 메시지를 보낼 수 없습니다. 데이터 및 메시지를 보내는 데 사용되는 DataCollectionContext는 데이터에 대해 발생한 이벤트 중 하나에서 가져와야 합니다.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.테스트 로거 URI '{0}'이(가) 잘못되었습니다. 테스트 로거를 무시합니다.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}설치된 단위 테스트 확장 목록을 찾지 못했습니다. 이유: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.이 옵션은 Visual Studio의 일부로 설치된 vstest.console.exe에서만 실행됩니다.
-
-
+ An error occurred while creating Fast filter.빠른 필터를 만드는 중 오류가 발생했습니다.
-
-
+ Cancelling the operation as requested.요청한 대로 작업을 취소하는 중입니다.
-
-
+ Unable to find a datacollector with friendly name '{0}'.이름이 '{0}'인 datacollector를 찾을 수 없습니다.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.'{0}' 파일에서 확장을 로드하지 못했습니다. 자세한 내용을 보려면 /diag를 사용하세요.
-
-
+ {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:{0} "TestResults" 폴더를 언급된 위치에 만드는 동안 액세스가 거부되었습니다. 쓰기 권한이 필요한 폴더에서 vstest.console.exe를 실행하고 있으므로 이 예외가 발생했습니다. 이 문제를 해결하려면 쓰기 권한이 있는 폴더에서 vstest.console.exe를 실행하세요. 자세한 내용은 다음 오류 메시지를 확인하세요.
-
-
+ Inner exception:내부 예외:
-
-
+ Stack trace:스택 추적:
-
-
+ Data collection : {0}
-
-
+ Zbieranie danych: {0}Data collector '{0}' message: {1}.
-
-
+ Komunikat modułu zbierającego dane „{0}”: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ Zduplikowany identyfikator URI rozszerzenia testu „{0}”. Zduplikowane rozszerzenie zostanie zignorowane.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Zduplikowany dostawca ustawień o nazwie „{0}”. Zduplikowany dostawca zostanie zignorowany.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Znaleziono zduplikowaną sekcję parametrów uruchomieniowych o nazwie „{0}”. Zduplikowane ustawienia zostaną zignorowane.Error: Empty parenthesis ( )
-
-
+ Błąd: puste nawiasy ( )Error: Invalid Condition '{0}'
-
-
+ Błąd: nieprawidłowy warunek „{0}”Test Extension has an invalid URI '{0}': {1}
-
-
+ Rozszerzenie testu ma nieprawidłowy identyfikator URI „{0}”: {1}Error: Invalid operator '{0}'
-
-
+ Błąd: nieprawidłowy operator „{0}”Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Wystąpił wyjątek podczas inicjowania rejestratora o identyfikatorze {0}: „{1}”. Rejestrator nie będzie używany. Wyjątek: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Nie można odnaleźć rejestratora testów z atrybutem AssemblyQualifiedName, identyfikatorem URI lub przyjazną nazwą „{0}”.Error: Missing ')'
-
-
+ Błąd: brak znaku „)”Error: Missing '('
-
-
+ Błąd: brak znaku „(”Error: Missing operand
-
-
+ Błąd: brak argumentu operacjiMissing Operator '|' or '&'
-
-
+ Brak operatora „|” lub „&”The Run Settings have already been loaded.
-
-
+ Parametry uruchomieniowe zostały już załadowane.An error occurred while loading the run settings. Error: {0}
-
-
+ Wystąpił błąd podczas ładowania parametrów uruchomieniowych. Błąd: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Określono nieprawidłowy węzeł ustawień. Właściwość name węzła ustawień nie może być pusta.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Wystąpił błąd podczas inicjowania dostawcy ustawień o nazwie „{0}”. Błąd: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Nie znaleziono dostawcy ustawień o nazwie „{0}”. Nie można załadować ustawień.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Niepoprawny format elementu TestCaseFilter {0}. Określ poprawny format i spróbuj ponownie. Należy pamiętać, że niepoprawny format może spowodować, że żadne testy nie zostaną wykonane.Data collector '{0}' failed to provide initialization information. Error: {1}Dostarczenie informacji o inicjowaniu przez moduł zbierający dane „{0}” nie powiodło się. Błąd: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.Moduł zbierający dane „{0}” zgłosił wyjątek w trakcie ładowania, konstruowania lub inicjowania typu: {1}.
-
-
+ Could not find data collector '{0}'Nie można znaleźć modułu zbierającego dane „{0}”
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.Moduł zbierający dane „{0}” zażądał ustawienia zmiennej środowiskowej „{1}” o wartości „{2}” w środowisku wykonywania testu, ale inny moduł zbierający dane „{3}” już zażądał ustawienia tej zmiennej środowiskowej na wartość „{4}”.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Istnieje wiele konfiguracji, które zawierają przyjazną nazwę modułu zbierającego dane „{0}”. Zduplikowane konfiguracje będą ignorowane w przebiegu testu.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.Moduł zbierający dane przechwycił wyjątek typu „{0}”: „{1}”. Więcej szczegółów: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Typy pochodzące od kontekstu kolekcji danych nie mogą być używane do wysyłania danych i komunikatów. Element DataCollectionContext służący do wysyłania danych i komunikatów musi pochodzić z jednego ze zdarzeń wywołanych dla modułu zbierającego dane.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.Podany identyfikator URI rejestratora testów „{0}” jest nieprawidłowy. Rejestrator testów zostanie zignorowany.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Nie można znaleźć listy zainstalowanych rozszerzeń testów jednostkowych. Przyczyna: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Ta opcja działa wyłącznie z elementem vstest.console.exe zainstalowanym jako część programu Visual Studio.
-
-
+ An error occurred while creating Fast filter.Wystąpił błąd podczas tworzenia szybkiego filtru.
-
-
+ Cancelling the operation as requested.Anulowanie operacji zgodnie z żądaniem.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Nie można znaleźć elementu datacollector o przyjaznej nazwie „{0}”.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Nie można załadować rozszerzeń z pliku „{0}”. Aby uzyskać więcej informacji, użyj opcji /diag.
-
-
+ {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:{0} Odmowa dostępu podczas próby utworzenia folderu „TestResults” w określonej lokalizacji. Widzisz ten wyjątek, ponieważ program vstest.console.exe został uruchomiony z folderu wymagającego dostępu do zapisu. Aby rozwiązać ten problem: uruchom program vstest.console.exe z folderu, w którym masz uprawnienia do zapisu. Więcej informacji można znaleźć w komunikacie o błędzie:
-
-
+ Inner exception:Wewnętrzny wyjątek:
-
-
+ Stack trace:Ślad stosu:
-
-
+ Data collection : {0}
-
-
+ Coleção de dados: {0}Data collector '{0}' message: {1}.
-
-
+ Coletor de dados '{0}' mensagem: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ URI da extensão do teste '{0}' duplicada. Ignorando a extensão duplicada.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Provedor de configurações denominado '{0}' duplicado. Ignorando o provedor duplicado.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Foi encontrada uma seção de configurações de execução denominada '{0}' duplicada. Ignorando as configurações duplicadas.Error: Empty parenthesis ( )
-
-
+ Erro: parênteses vazios ( )Error: Invalid Condition '{0}'
-
-
+ Erro: condição inválida '{0}'Test Extension has an invalid URI '{0}': {1}
-
-
+ A Extensão do Teste tem um URI inválido '{0}': {1}Error: Invalid operator '{0}'
-
-
+ Erro: operador inválido '{0}'Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Ocorreu uma exceção durante a inicialização do agente com {0}: ‘{1}’. O agente não será usado. Exceção: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Não foi possível localizar um agente de teste com o AssemblyQualifiedName, o URI ou o FriendlyName '{0}'.Error: Missing ')'
-
-
+ Erro: ')' ausenteError: Missing '('
-
-
+ Erro: '(' ausenteError: Missing operand
-
-
+ Erro: operando ausenteMissing Operator '|' or '&'
-
-
+ Faltando operador '|' ou '&'The Run Settings have already been loaded.
-
-
+ As Configurações de Execução já foram carregadas.An error occurred while loading the run settings. Error: {0}
-
-
+ Ocorreu um erro ao carregar as configurações de execução. Erro: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Nó de configurações inválido especificado. A propriedade de nome do nó de configurações não deve estar vazia.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ Ocorreu um erro ao inicializar o provedor de configurações denominado '{0}'. Erro: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ O Provedor de Configurações denominado '{0}' não foi encontrado. Não é possível carregar as configurações.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Formato incorreto para TestCaseFilter {0}. Especifique o formato correto e tente novamente. Observe que o formato incorreto pode fazer com que nenhum teste seja executado.Data collector '{0}' failed to provide initialization information. Error: {1}O coletor de dados '{0}' falhou ao fornecer informações de inicialização. Erro: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.O coletor de dados '{0}' lançou uma exceção durante a inicialização, construção ou carregamento de tipo: {1}.
-
-
+ Could not find data collector '{0}'Não foi possível encontrar o coletor de dados '{0}'
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.O coletor de dados '{0}' solicitou a variável de ambiente '{1}' com valor '{2}' para ser definida no ambiente de execução de teste, mas outro coletor de dados '{3}' já solicitou a mesma variável de ambiente com um valor diferente '{4}'.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Existem várias configurações que têm o FriendlyName do coletor de dados como '{0}'. Configurações duplicadas serão ignoradas na execução de teste.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.O coletor de dados capturou uma exceção do tipo '{0}': '{1}'. Mais detalhes: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Tipos derivados de DataCollectionContext não podem ser usados para enviar dados e mensagens. Os DataCollectionContext usado para enviar dados e mensagens devem vir de um dos eventos adicionados ao coletor de dados.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.O URI do Agente de Teste '{0}' não é válido. O Agente de Teste será ignorado.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Falha ao encontrar a lista de extensões de teste de unidade. Motivo: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Essa opção funciona somente com vstest.console.exe instalado como parte do Visual Studio.
-
-
+ An error occurred while creating Fast filter.Ocorreu um erro ao criar o filtro Rápido.
-
-
+ Cancelling the operation as requested.Cancelando a operação conforme solicitado.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Não é possível localizar um datacollector com o nome amigável '{0}'.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Falha ao carregar as extensões do arquivo '{0}'. Use /diag para obter mais informações.
-
-
+ {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:{0} Acesso negado ao tentar criar a pasta "TestResults" no local mencionado. Você está recebendo esta exceção porque está executando o vstest.console.exe em uma pasta que requer acesso para gravação. Para resolver o problema: execute vstest.console.exe em uma pasta na qual você tenha privilégios de gravação. Para obter mais informações, verifique a mensagem de erro:
-
-
+ Inner exception:Exceção interna:
-
-
+ Stack trace:Rastreamento de pilha:
-
-
+ Data collection : {0}
-
-
+ Сбор данных: {0}Data collector '{0}' message: {1}.
-
-
+ Сообщение сборщика данных "{0}": {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ Повторяющийся URI расширения теста "{0}". Повторяющееся расширение пропускается.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ Повторяющийся поставщик параметров с именем "{0}". Повторяющийся поставщик пропускается.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ Обнаружен повторяющийся раздел параметров запуска с именем "{0}". Повторяющиеся параметры пропускаются.Error: Empty parenthesis ( )
-
-
+ Ошибка: пустые круглые скобки ()Error: Invalid Condition '{0}'
-
-
+ Ошибка: недопустимое условие "{0}"Test Extension has an invalid URI '{0}': {1}
-
-
+ Расширение теста имеет недопустимый URI "{0}": {1}Error: Invalid operator '{0}'
-
-
+ Ошибка: недопустимый оператор "{0}"Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Возникло исключение при инициализации средства ведения журнала с {0}: "{1}". Средство ведения журнала не будет использоваться. Исключение: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ Не удалось найти средство ведения журнала тестирования с AssemblyQualifiedName, URI или FriendlyName "{0}".Error: Missing ')'
-
-
+ Ошибка: отсутствует ")"Error: Missing '('
-
-
+ Ошибка: отсутствует "("Error: Missing operand
-
-
+ Ошибка: отсутствует операндMissing Operator '|' or '&'
-
-
+ Отсутствует оператор "|" или "&"The Run Settings have already been loaded.
-
-
+ Параметры запуска уже загружены.An error occurred while loading the run settings. Error: {0}
-
-
+ Произошла ошибка при загрузке параметров запуска. Ошибка: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Указан недопустимый узел параметров. Узел параметров должен иметь допустимое значение для свойства имени.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ При инициализации поставщика параметров с именем "{0}" произошла ошибка. Ошибка: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ Поставщик параметров с именем "{0}" не найден. Невозможно загрузить параметры.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ Неверный формат фильтра TestCaseFilter {0}. Задайте правильный формат и повторите попытку. Обратите внимание, что использование неверного формата может привести к тому, что ни один из тестов не будет выполнен.Data collector '{0}' failed to provide initialization information. Error: {1}Сборщик данных "{0}" не предоставил сведения для инициализации. Ошибка: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.В сборщике данных "{0}" возникло исключение во время загрузки типа, создания или инициализации: {1}.
-
-
+ Could not find data collector '{0}'Не удалось найти сборщик данных "{0}"
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.Сборщик данных "{0}" запросил, чтобы в окружении выполнения тестов была установлена переменная окружения "{1}" со значением "{2}", но другой сборщик данных "{3}" уже запросил эту переменную окружения со значением "{4}".
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Существует несколько конфигураций со значением "{0}" для FriendlyName сборщика данных. Повторяющиеся конфигурации будут пропущены в тестовом запуске.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.В сборщике данных возникло исключение типа "{0}": "{1}". Дополнительные сведения: {2}.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Нельзя использовать типы, производные от контекста сбора данных, для отправки данных и сообщений. Используемый для отправки данных и сообщений DataCollectionContext должен происходить от одного из событий, возникших для сборщика данных.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.URI средства ведения журнала тестирования "{0}" недопустимо. Это средство ведения журнала тестирования будет игнорироваться.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Не удалось найти список установленных расширений модульных тестов. Причина: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Этот параметр работает, только если в рамках Visual Studio установлена служебная программа vstest.console.exe.
-
-
+ An error occurred while creating Fast filter.При создании быстрого фильтра произошла ошибка.
-
-
+ Cancelling the operation as requested.Операция отменяется в соответствии с запросом.
-
-
+ Unable to find a datacollector with friendly name '{0}'.Не удается найти datacollector с понятным именем "{0}".
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Не удалось загрузить расширения из файла "{0}". Для получения дополнительных сведений используйте /diag.
-
-
+ {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:{0} Отказано в доступе при попытке создания папки "TestResults" в указанном расположении. Это исключение возникло, так как вы запускаете файл vstest.console.exe из папки, для которой требуется доступ на запись. Чтобы устранить эту проблему, запустите vstest.console.exe из папки, для которой у вас есть разрешения на запись. Дополнительные сведения см. в сообщении об ошибке:
-
-
+ Inner exception:Внутреннее исключение:
-
-
+ Stack trace:Трассировка стека:
-
-
+ Data collection : {0}
-
-
+ Veri toplama: {0}Data collector '{0}' message: {1}.
-
-
+ '{0}' veri toplayıcısı iletisi: {1}.Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ Yinelenen test uzantısı URI’si '{0}'. Yinelenen uzantı yoksayılıyor.Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ '{0}' adlı yinelenen ayar sağlayıcısı. Yinelenen sağlayıcı yoksayılıyor.Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ '{0}' adlı yinelenen çalıştırma ayarları bölümü bulundu. Yinelenen ayarlar yoksayılıyor.Error: Empty parenthesis ( )
-
-
+ Hata: Boş ayraç ( )Error: Invalid Condition '{0}'
-
-
+ Hata: Geçersiz Koşul '{0}'Test Extension has an invalid URI '{0}': {1}
-
-
+ Test Uzantısı geçersiz bir '{0}' URI’sine sahip: {1}Error: Invalid operator '{0}'
-
-
+ Hata: Geçersiz işleç '{0}'Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ Günlükçü, '{0}' ile başlatılırken özel durum oluştu: '{1}'. Günlükçü kullanılmayacak. Özel durum: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ AssemblyQualifiedName, URI veya FriendlyName değeri '{0}' olan bir test günlükçüsü bulunamadı.Error: Missing ')'
-
-
+ Hata: ')' eksikError: Missing '('
-
-
+ Hata: '(' eksikError: Missing operand
-
-
+ Hata: İşlenen eksikMissing Operator '|' or '&'
-
-
+ '|' veya '&' işleci eksikThe Run Settings have already been loaded.
-
-
+ Çalıştırma Ayarları zaten yüklendi.An error occurred while loading the run settings. Error: {0}
-
-
+ Çalıştırma ayarları yüklenirken bir hata oluştu. Hata: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ Belirtilen ayar düğümü geçersiz. Ayar düğümünün ad özelliği boş olmamalıdır.An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ '{0}' adlı ayar sağlayıcısı başlatılırken bir hata oluştu. Hata: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ '{0}' adlı Ayar Sağlayıcısı bulunamadı. Ayarlar yüklenemiyor.Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ TestCaseFilter {0} için yanlış biçim. Doğru biçimi belirtin ve yeniden deneyin. Yanlış biçim hiçbir testin yürütülmemesine neden olabilir.Data collector '{0}' failed to provide initialization information. Error: {1}'{0}' veri toplayıcısı başlatma bilgilerini sağlayamadı. Hata: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.'{0}' veri toplayıcısı tür yükleme, oluşturma veya başlatma sırasında bir özel durum oluşturdu: {1}.
-
-
+ Could not find data collector '{0}''{0}' veri toplayıcısı bulunamadı
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.'{0}' veri toplayıcısı, test yürütme ortamında değeri '{2}' olan '{1}' ortam değişkeninin ayarlanması için istekte bulundu, ancak başka bir veri toplayıcısı ('{3}') zaten farklı bir değerle ('{4}') aynı ortam değişkeni için istekte bulunmuştu.
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.Veri toplayıcısı FriendlyName değeri '{0}' olan birden çok yapılandırma var. Yinelenen yapılandırmalar test çalıştırmasında yoksayılacak.
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.Veri toplayıcısı '{0}' türünde bir özel durum yakaladı: '{1}'. Diğer ayrıntılar:'{2}'.
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.Veri koleksiyonu bağlamından türetilen türler, veri ve ileti göndermek için kullanılamaz. Veri ve ileti göndermek için kullanılan DataCollectionContext veri toplayıcısı yükseltilmiş olayların birinden gelmelidir.
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.Test Günlükçüsünün '{0}' URI’si geçerli değil. Test Günlükçüsü yoksayılacak.
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}Yüklenen birim testi uzantılarının listesi bulunamadı. Neden: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.Bu seçenek yalnızca Visual Studio’nun bir parçası olarak yüklenen vstest.console.exe ile birlikte çalışır.
-
-
+ An error occurred while creating Fast filter.Hızlı filtre oluşturulurken bir hata oluştu.
-
-
+ Cancelling the operation as requested.İşlem istek üzerine iptal ediliyor.
-
-
+ Unable to find a datacollector with friendly name '{0}'.'{0}' kolay adına sahip bir datacollector bulunamadı.
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.Uzantılar '{0}' dosyasından yüklenemedi. Daha fazla bilgi için lütfen /diag kullanın.
-
-
+ {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:{0} Belirtilen konumda "TestResults" klasörü oluşturulmaya çalışılırken erişim engellendi. Yazma erişimi gerektiren bir klasörden vstest.console.exe çalıştırdığınız için bu özel durumu aldınız. Sorunu çözmek için: Lütfen yazma ayrıcalıklarına sahip olduğunuz bir klasörden vstest.console.exe dosyasını çalıştırın. Daha fazla bilgi için lütfen hata iletisine bakın:
-
-
+ Inner exception:Özel iç durum:
-
-
+ Stack trace:Yığın izleme:
-
-
+ Data collection : {0}
-
-
+ 数据收集: {0}Data collector '{0}' message: {1}.
-
-
+ 数据收集器“{0}”消息: {1}。Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ 测试扩展 URI“{0}”重复。忽略重复的扩展。Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ 名为“{0}”的设置提供程序重复。忽略重复的提供程序。Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ 名为“{0}”的运行设置部分重复。请忽略重复的设置。Error: Empty parenthesis ( )
-
-
+ 错误: 空括号 ( )Error: Invalid Condition '{0}'
-
-
+ 错误: 无效条件“{0}”Test Extension has an invalid URI '{0}': {1}
-
-
+ 测试扩展具有无效的 URI“{0}”: {1}Error: Invalid operator '{0}'
-
-
+ 错误: 运算符“{0}”无效Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ 初始化带有 {0} 的记录器时发生异常: "{1}"。将不会使用该记录器。异常: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ 找不到 AssemblyQualifiedName、URI 或 FriendlyName 为 "{0}" 的测试记录器。Error: Missing ')'
-
-
+ 错误: 缺少 ")"Error: Missing '('
-
-
+ 错误: 缺少 "("Error: Missing operand
-
-
+ 错误: 缺少操作数Missing Operator '|' or '&'
-
-
+ 缺少运算符 '|' 或 '&'The Run Settings have already been loaded.
-
-
+ 已加载运行设置。An error occurred while loading the run settings. Error: {0}
-
-
+ 加载运行设置时出错。错误: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ 指定了无效的设置节点。设置节点的名称属性必须为非空。An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ 初始化名为“{0}”的设置提供程序时出错。错误: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ 找不到名为“{0}”的设置提供程序。无法加载设置。Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ TestCaseFilter {0} 的格式不正确。请指定正确的格式并重试。请注意,格式不正确会导致不执行任何测试。Data collector '{0}' failed to provide initialization information. Error: {1}数据收集器“{0}”未能提供初始化信息。错误: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.在类型加载、构造或初始化期间,数据收集器“{0}”引发了异常: {1}。
-
-
+ Could not find data collector '{0}'找不到数据收集器“{0}”
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.数据收集器“{0}”已请求具有将在测试执行环境中设置的值“{2}”的环境变量“{1}”,但另一个数据收集器“{3}”已请求具有其他值“{4}”的同一环境变量。
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.有多个配置的数据收集器 FriendlyName 为“{0}”。测试运行中将忽略重复的配置。
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.数据收集器已捕获类型为“{0}”的异常:“{1}”。更多详细信息: {2}。
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.从数据收集上下文派生的类型不能用于发送数据和消息。 用于发送数据和消息的 DataCollectionContext 必须来自向数据收集器引发的某个事件。
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.测试记录器 URI“{0}”无效。将忽略该测试记录器。
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}找不到已安装的单元测试扩展列表。原因: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.此选项仅适用于作为 Visual Studio 一部分安装的 vstest.console.exe。
-
-
+ An error occurred while creating Fast filter.创建“快”筛选器时遇到错误。
-
-
+ Cancelling the operation as requested.按要求取消该操作。
-
-
+ Unable to find a datacollector with friendly name '{0}'.找不到友好名称为“{0}”的 datacollector。
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.未能从文件 "{0}" 加载扩展。有关详细信息,请使用 /diag。
-
-
+ {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:{0} 尝试在所述位置创建 "TestResults" 文件夹时,访问被拒。你收到此异常是因为你正在从需要具有写入权限的文件夹运行 vstest.console.exe。若要解决此问题,请从你具有写入权限的文件夹运行 vstest.console.exe。有关详细信息,请查看错误消息:
-
-
+ Inner exception:内部异常:
-
-
+ Stack trace:堆栈跟踪:
-
-
+ Data collection : {0}
-
-
+ 資料收集: {0}Data collector '{0}' message: {1}.
-
-
+ 資料收集器 '{0}' 的訊息: {1}。Duplicate test extension URI '{0}'. Ignoring the duplicate extension.
-
-
+ 重複的測試延伸模組 URI '{0}'。忽略重複的延伸模組。Duplicate settings provider named '{0}'. Ignoring the duplicate provider.
-
-
+ 名為 '{0}' 的重複的設定提供者。忽略重複的提供者。Duplicate run settings section named '{0}' found. Ignoring the duplicate settings.
-
-
+ 找到名為 '{0}' 的重複執行設定區段。忽略重複的設定。Error: Empty parenthesis ( )
-
-
+ 錯誤: 空的括弧 ( )Error: Invalid Condition '{0}'
-
-
+ 錯誤: 條件 '{0}' 無效Test Extension has an invalid URI '{0}': {1}
-
-
+ 測試延伸模組的 URI '{0}' 無效: {1}Error: Invalid operator '{0}'
-
-
+ 錯誤: 運算子 '{0}' 無效Exception occurred while initializing logger with {0}: '{1}'. The logger will not be used. Exception: {2}
-
-
+ 初始化具有 '{0}' 的記錄器時,發生例外狀況: '{1}'。將不會使用此記錄器。例外狀況: {2}Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName '{0}'.
-
-
+ 找不到具有 AssemblyQualifiedName、URI 或 FriendlyName '{0}' 的測試記錄器。Error: Missing ')'
-
-
+ 錯誤: 遺漏 ')'Error: Missing '('
-
-
+ 錯誤: 遺漏 '('Error: Missing operand
-
-
+ 錯誤: 遺漏運算元Missing Operator '|' or '&'
-
-
+ 遺漏運算子 '|' 或 '&'The Run Settings have already been loaded.
-
-
+ 已載入 [回合設定]。An error occurred while loading the run settings. Error: {0}
-
-
+ 載入回合設定時發生錯誤。錯誤: {0}Invalid settings node specified. The name property of the settings node must be non-empty.
-
-
+ 指定的設定節點無效。設定節點的名稱屬性必須為非空白。An error occurred while initializing the settings provider named '{0}'. Error: {1}
-
-
+ 將名為 '{0}' 的設定提供者初始化時發生錯誤。錯誤: {1}Settings Provider named '{0}' was not found. The settings can not be loaded.
-
-
+ 找不到名為 '{0}' 的設定提供者。無法載入設定。Incorrect format for TestCaseFilter {0}. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed.
-
-
+ TestCaseFilter {0} 的格式不正確。請指定正確的格式後再試一次。請注意,格式不正確可能會導致無法執行測試。Data collector '{0}' failed to provide initialization information. Error: {1}資料收集器 '{0}' 無法提供初始化資訊。錯誤: {1}
-
-
+ Data collector '{0}' threw an exception during type loading, construction, or initialization: {1}.載入、建構或初始化類型期間,資料收集器 '{0}'擲回例外狀況: {1}。
-
-
+ Could not find data collector '{0}'找不到資料收集器 '{0}'
-
-
+ The data collector '{0}' requested environment variable '{1}' with value '{2}' to be set in test execution environment, but another data collector '{3}' has already requested same environment variable with different value '{4}'.資料收集器 '{0}' 要求要在測試執行環境中將環境變數 '{1}' 的值設為 '{2}',但另一個資料收集器 '{3}' 已要求了同一個環境變數,但具有不同的值 '{4}'。
-
-
+ There are multiple configurations that have data collector FriendlyName as '{0}'. Duplicate configurations will be ignored in the test run.有多個組態的資料收集器 FriendlyName 為 '{0}'。在測試回合中,重複的組態將予忽略。
-
-
+ Data collector caught an exception of type '{0}': '{1}'. More details: {2}.資料收集器攔截到類型為 '{0}' 的例外狀況: '{1}'。更多詳細資料: {2}。
-
-
+ Types deriving from the data collection context cannot be used for sending data and messages. The DataCollectionContext used for sending data and messages must come from one of the events raised to the data collector.衍生自資料收集內容的類型無法用於傳送資料和訊息。用於傳送資料和訊息的 DataCollectionContext 必須來自其中一個引發資料收集器的事件。
-
-
+ The Test Logger URI '{0}' is not valid. The Test Logger will be ignored.測試記錄器 URI '{0}' 無效。將忽略測試記錄器。
-
-
+ Failed to find the list of installed unit test extensions. Reason: {0}無法找到已安裝之單元測試延伸模組的清單。原因: {0}
-
-
+ This option works only with vstest.console.exe installed as part of Visual Studio.此選項僅適用於隨 Visual Studio 安裝的 vstest.console.exe。
-
-
+ An error occurred while creating Fast filter.建立快速篩選時發生錯誤。
-
-
+ Cancelling the operation as requested.正在應要求取消作業。
-
-
+ Unable to find a datacollector with friendly name '{0}'.找不到易記名稱為 '{0}' 的 datacollector。
-
-
+ Failed to load extensions from file '{0}'. Please use /diag for more information.無法從檔案 '{0}' 載入延伸模組。如需詳細資訊,請使用 /diag。
-
-
+ {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:{0} 嘗試在提及的位置上建立 "TestResults" 資料夾時存取被拒。因為您正從需要寫入存取權的資料夾執行 vstest.console.exe,所以收到此例外狀況。若要解決此問題: 請從您有權寫入的資料夾執行 vstest.console.exe。如需詳細資訊,請參閱錯誤訊息:
-
-
+ Inner exception:內部例外狀況:
-
-
+ Stack trace:堆疊追蹤:
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Aktivní testovací běh se přerušil. Důvod: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Vzdálený hostitel vynutil ukončení existujícího připojení.The active test discovery was aborted. Reason: {0}
-
-
+ Aktivní zjišťování testu se přerušilo. Důvod: {0}Unable to communicate with test host process.
-
-
+ Nepovedlo se navázat komunikaci s procesem hostitele testu.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Byla přijata neočekávaná zpráva. Očekávaný typ zprávy: {0} Skutečný typ zprávy: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Kontrola verze protokolu selhala. Ověřte, jestli je spouštěč testů kompatibilní s hostitelem.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Nepodařilo se vyjednat protokol. Po {0} s vypršel časový limit čekání na odezvu. Důvodem může být pomalý počítač. Nastavením proměnné prostředí {1} prosím časový limit prodlužte.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Procesu {0} se nepovedlo připojit k procesu {1} ani po {2} s. Důvodem může být pomalý počítač. Nastavením proměnné prostředí {3} prosím časový limit prodlužte.
-
-
+ Test host process crashedProces testovacího hostitele se chybově ukončil.
-
-
+ Cannot attach the debugger to the default test host.Ladicí program se nedá připojit k výchozímu hostiteli testů.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Der aktive Testlauf wurde abgebrochen. Grund: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Das Schließen einer vorhandenen Verbindung wurde vom Remotehost erzwungen.The active test discovery was aborted. Reason: {0}
-
-
+ Die aktive Testermittlung wurde abgebrochen. Grund: {0}Unable to communicate with test host process.
-
-
+ Die Kommunikation mit dem Testhostprozess ist nicht möglich.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Unerwartete Meldung empfangen. Erwarteter MessageType: {0}. Tatsächlicher MessageType: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Fehler beim Überprüfen der Protokollversion. Der Test Runner und der Host müssen kompatibel sein.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Fehler beim Verhandeln des Protokolls. Timeout beim Warten auf Antwort nach {0} Sekunden. Möglicherweise ist der Computer langsam. Legen Sie die Umgebungsvariable "{1}" fest, um den Timeoutwert zu erhöhen.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Fehler beim Herstellen einer Verbindung des Prozesses "{0}" mit dem Prozess "{1}" nach {2} Sekunden. Möglicherweise ist der Computer langsam. Legen Sie die Umgebungsvariable "{3}" fest, um den Timeoutwert zu erhöhen.
-
-
+ Test host process crashedDer Testhostprozess ist abgestürzt.
-
-
+ Cannot attach the debugger to the default test host.Der Debugger kann nicht an den Standardtesthost angefügt werden.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Se ha anulado la serie de pruebas activa. Motivo: {0}An existing connection was forcibly closed by the remote host.
-
-
+ El host remoto forzó el cierre de una conexión.The active test discovery was aborted. Reason: {0}
-
-
+ Se ha anulado la detección de pruebas activa. Motivo: {0}Unable to communicate with test host process.
-
-
+ No se puede establecer comunicación con el proceso del host de pruebas.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Se ha recibido un mensaje inesperado. Tipo de mensaje esperado: {0} Tipo de mensaje real: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Error en la comprobación de la versión del protocolo. Asegúrese de que el ejecutor de pruebas y el host son compatibles.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.No se pudo negociar el protocolo, se agotó el tiempo de espera para la respuesta después de {0} segundos. Esto puede deberse a la lentitud de la máquina, configure la variable de entorno {1} para aumentar el tiempo de espera.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.El proceso {0} no pudo conectar con el proceso {1} después de {2} segundos. Esto puede deberse a la lentitud de la máquina, configure la variable de entorno {3} para aumentar el tiempo de espera.
-
-
+ Test host process crashedProceso de host de pruebas bloqueado
-
-
+ Cannot attach the debugger to the default test host.No se puede asociar el depurador al host de prueba predeterminado.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ La série de tests active a été abandonnée. Raison : {0}An existing connection was forcibly closed by the remote host.
-
-
+ Une connexion existante a été fermée de force par l'hôte distant.The active test discovery was aborted. Reason: {0}
-
-
+ La découverte de tests active a été abandonnée. Raison : {0}Unable to communicate with test host process.
-
-
+ Impossible de communiquer avec le processus hôte du test.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Message inattendu reçu. MessageType attendu : {0} MessageType réel : {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Échec de la vérification de la version du protocole. Vérifiez que Test Runner et l'hôte sont compatibles.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Échec de négociation du protocole, en attente d’une réponse dont le délai expire après {0} secondes. Cette situation peut se produire à cause de la lenteur de la machine. Définissez la variable d’environnement {1} de sorte à augmenter le délai d’expiration.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Le processus {0} n’a pas réussi à se connecter au processus {1} après {2} secondes. Cette situation peut se produire à cause de la lenteur de la machine. Définissez la variable d’environnement {3} de sorte à augmenter le délai d’expiration.
-
-
+ Test host process crashedPlantage du processus hôte de test
-
-
+ Cannot attach the debugger to the default test host.Impossible d'attacher le débogueur à l'hôte de test par défaut.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ L'esecuzione dei test attivi è stata interrotta. Motivo: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Una connessione esistente è stata chiusa forzatamente dall'host remoto.The active test discovery was aborted. Reason: {0}
-
-
+ L'individuazione dei test attivi è stata interrotta. Motivo: {0}Unable to communicate with test host process.
-
-
+ Non è possibile comunicare con il processo host dei test.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}È stato ricevuto un messaggio imprevisto. Tipo di messaggio previsto: {0}. Tipo di messaggio effettivo: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Il controllo della versione del protocollo non è riuscito. Assicurarsi che runner e host dei test siano compatibili.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Non è stato possibile negoziare il protocollo: in attesa del timeout della risposta dopo {0} secondi. Questo problema può verificarsi a causa della lentezza del computer. Impostare la variabile di ambiente {1} in modo da incrementare il timeout.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Il processo {0} non è riuscito a connettersi al processo {1} dopo {2} secondi. Questo problema può verificarsi a causa della lentezza del computer. Impostare la variabile di ambiente {3} in modo da incrementare il timeout.
-
-
+ Test host process crashedArresto anomalo del processo host di test
-
-
+ Cannot attach the debugger to the default test host.Non è possibile collegare il debugger all'host di test predefinito.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ アクティブなテストの実行が中止されました。理由: {0}An existing connection was forcibly closed by the remote host.
-
-
+ 既存の接続はリモート ホストに強制的に切断されました。The active test discovery was aborted. Reason: {0}
-
-
+ アクティブなテスト探索が中止されました。理由: {0}Unable to communicate with test host process.
-
-
+ テスト ホスト プロセスと通信できません。Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}予期しないメッセージを受信しました。予想されたメッセージの種類: {0} 実際のメッセージの種類: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.プロトコルのバージョンを確認できませんでした。テスト ランナーとホストに互換性があることをご確認ください。
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.プロトコルをネゴシエートできませんでした。応答への待機が {0} 秒後にタイムアウトしました。これはマシンの遅さが原因で発生する可能性があるため、環境変数 {1} を設定してタイムアウト時間を増やしてください。
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.{0} プロセスでは、{2} 秒後に {1} プロセスへ接続できませんでした。これは、マシンの遅さが原因で発生する可能性があるため、環境変数 {3} を設定してタイムアウト時間を増やしてください。
-
-
+ Test host process crashedテストのホスト プロセスがクラッシュしました
-
-
+ Cannot attach the debugger to the default test host.デバッガーを既定のテスト ホストにアタッチできません。
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ 활성 테스트 실행이 중단되었습니다. 이유: {0}An existing connection was forcibly closed by the remote host.
-
-
+ 원격 호스트에 의해 기존 연결이 강제로 종료되었습니다.The active test discovery was aborted. Reason: {0}
-
-
+ 활성 테스트 검색이 중단되었습니다. 이유: {0}Unable to communicate with test host process.
-
-
+ 테스트 호스트 프로세스와 통신할 수 없습니다.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}예기치 않은 메시지를 수신했습니다. 필요한 MessageType: {0} 실제 MessageType: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.프로토콜 버전을 확인하지 못했습니다. Test Runner와 호스트가 호환되는지 확인하세요.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.프로토콜을 협상하지 못했습니다. {0}초 후 응답 시간이 초과될 때까지 기다리는 중입니다. 이런 오류는 컴퓨터가 느려서 발생할 수 있습니다. 환경 변수 {1}을(를) 설정하여 시간 제한을 늘리세요.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.{0} 프로세스가 {2}초 후 {1} 프로세스에 연결하지 못했습니다. 이런 오류는 컴퓨터가 느려서 발생할 수 있습니다. 환경 변수 {3}을(를) 설정하여 시간 제한을 늘리세요.
-
-
+ Test host process crashed테스트 호스트 프로세스 작동이 중단됨
-
-
+ Cannot attach the debugger to the default test host.기본 테스트 호스트에 디버거를 연결할 수 없습니다.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Aktywny przebieg testu został przerwany. Przyczyna: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Zamknięcie istniejącego połączenia zostało wymuszone przez host zdalny.The active test discovery was aborted. Reason: {0}
-
-
+ Aktywny proces wykrywania testu został przerwany. Przyczyna: {0}Unable to communicate with test host process.
-
-
+ Nie można nawiązać komunikacji z procesem hosta.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Otrzymano nieoczekiwany komunikat. Oczekiwany typ komunikatu: {0}, otrzymany typ komunikatu: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Sprawdzanie wersji protokołu nie powiodło się. Upewnij się, że moduł uruchamiający testy i host są zgodne.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Negocjowanie protokołu nie powiodło się, po upływie {0} sekund został przekroczony limit czasu oczekiwania na odpowiedź. Przyczyną może być wolne działanie maszyny. Zwiększ limit czasu, ustawiając zmienną środowiskową {1}.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Proces {0} nie mógł połączyć się z procesem {1} w ciągu {2} sekund. Przyczyną może być wolne działanie maszyny. Zwiększ limit czasu, ustawiając zmienną środowiskową {3}.
-
-
+ Test host process crashedWystąpiła awaria procesu hosta testu
-
-
+ Cannot attach the debugger to the default test host.Nie można dołączyć debugera do domyślnego hosta testowego.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ A execução de teste ativa foi anulada. Motivo: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Uma conexão existente foi fechada à força pelo host remoto.The active test discovery was aborted. Reason: {0}
-
-
+ A descoberta de teste ativa foi anulada. Motivo: {0}Unable to communicate with test host process.
-
-
+ Não é possível se comunicar com o processo de host de teste.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Mensagem inesperada recebida. MessageType esperada: {0} MessageType real: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Falha na verificação da versão do protocolo. Verifique se o executor de testes e o host são compatíveis.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Falha ao negociar o protocolo, aguardando pelo tempo limite de resposta após {0} segundos. Isso pode ocorrer devido à lentidão do computador. Defina a variável de ambiente {1} para aumentar o tempo limite.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.O processo {0} falha ao se conectar ao processo {1} após {2} segundos. Isso pode ocorrer devido à lentidão do computador. Defina a variável de ambiente {3} para aumentar o tempo limite.
-
-
+ Test host process crashedFalha no processo do host de teste
-
-
+ Cannot attach the debugger to the default test host.Não é possível anexar o depurador ao host de teste padrão.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Активный тестовый запуск прерван. Причина: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Существующее подключение принудительно закрыто удаленным узлом.The active test discovery was aborted. Reason: {0}
-
-
+ Активное обнаружение тестов прервано. Причина: {0}Unable to communicate with test host process.
-
-
+ Не удалось связаться с хост-процессом теста.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Получено непредвиденное сообщение. Ожидаемый тип сообщения (MessageType): {0}, фактический тип сообщения (MessageType): {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Проверка версии протокола не пройдена. Убедитесь, что средство запуска теста и узел совместимы.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Не удалось согласовать протокол, превышено время ожидания ответа по прошествии {0} с. Это может происходить из-за медленной работы компьютера. Увеличьте время ожидания в переменной среды {1}.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.Процесс {0} не смог подключиться к процессу {1} по прошествии {2} с. Это может происходить из-за медленной работы компьютера. Увеличьте время ожидания в переменной среды {3}.
-
-
+ Test host process crashedСбой хост-процесса теста
-
-
+ Cannot attach the debugger to the default test host.Не удается подключить отладчик к узлу тестирования по умолчанию.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ Etkin test çalıştırması iptal edildi. Nedeni: {0}An existing connection was forcibly closed by the remote host.
-
-
+ Mevcut bir bağlantı uzak konak tarafından zorla kapatıldı.The active test discovery was aborted. Reason: {0}
-
-
+ Etkin test bulma iptal edildi. Nedeni: {0}Unable to communicate with test host process.
-
-
+ Test ana bilgisayarı işlemi ile iletişim kurulamıyor.Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}Beklenmeyen ileti alındı. Beklenen MessageType: {0} Gerçek MessageType: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.Protokol sürümü denetlenemedi. Test çalıştırıcısı ve ana bilgisayarının uyumlu olduğundan emin olun.
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.Protokol üzerinde anlaşmaya varılamadı, yanıt bekleme süresi {0} saniyenin ardından zaman aşımına uğradı. Bu durum makinenin yavaşlığından kaynaklanıyor olabilir, zaman aşımı süresini artırmak için lütfen ortam değişkenini {1} olarak ayarlayın.
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.{0} işlemi, {2} saniye sonra {1} işlemine bağlanamadı. Bu durum makinenin yavaşlığından kaynaklanıyor olabilir, zaman aşımı süresini artırmak için lütfen ortam değişkenini {3} olarak ayarlayın.
-
-
+ Test host process crashedTest ana işlemi kilitlendi
-
-
+ Cannot attach the debugger to the default test host.Hata ayıklayıcı, varsayılan test ana bilgisayarına eklenemiyor.
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ 活动的测试运行已中止。原因: {0}An existing connection was forcibly closed by the remote host.
-
-
+ 现有连接被远程主机强制关闭。The active test discovery was aborted. Reason: {0}
-
-
+ 活动的测试发现已中止。原因: {0}Unable to communicate with test host process.
-
-
+ 无法与测试宿主进程通信。Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}收到意外消息。意外 MessageType: {0} 实际 MessageType: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.协议版本检查失败。请确保测试运行程序和主机兼容。
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.未能协商协议,等待响应在 {0} 秒后超时。出现此问题可能是因为计算机性能较低,请设置环境变量 {1},增加超时时间值。
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.{0} 进程未能在 {2} 秒后连接到 {1} 进程。出现此问题可能是因为计算机性能较低,请设置环境变量 {3},增加超时时间值。
-
-
+ Test host process crashed测试主机进程崩溃
-
-
+ Cannot attach the debugger to the default test host.无法将调试程序附加到默认测试主机。
-
-
+ The active test run was aborted. Reason: {0}
-
-
+ 使用中的測試回合已中止。原因: {0}An existing connection was forcibly closed by the remote host.
-
-
+ 遠端主機已強制關閉現有連線。The active test discovery was aborted. Reason: {0}
-
-
+ 使用中的測試探索已中止。原因: {0}Unable to communicate with test host process.
-
-
+ 無法與測試主機處理序通訊。Unexpected message received. Expected MessageType : {0} Actual MessageType: {1}收到未預期的訊息。需要的訊息類型: {0},實際的訊息類型: {1}
-
-
+ Protocol version check failed. Make sure test runner and host are compatible.通訊協定版本檢查失敗。請確定測試執行器與主機相容。
-
-
+ Failed to negotiate protocol, waiting for response timed out after {0} seconds. This may occur due to machine slowness, please set environment variable {1} to increase timeout.無法交涉通訊協定,等待回應在 {0} 秒後已逾時。原因可能是電腦太慢,請設定環境變數 {1},加長逾時。
-
-
+ {0} process failed to connect to {1} process after {2} seconds. This may occur due to machine slowness, please set environment variable {3} to increase timeout.在 {2} 秒後,{0} 處理序無法連線到 {1} 處理序。原因可能是電腦太慢,請設定環境變數 {3},加長逾時。
-
-
+ Test host process crashed測試主機處理序當機
-
-
+ Cannot attach the debugger to the default test host.無法將偵錯工具連結到預設測試主機。
-
-
+ The parameter cannot be null or empty.
-
-
+ Parametr nemůže být null nebo prázdný.Error: {0}
-
-
+ Chyba: {0}Information: {0}
-
-
+ Informace: {0}Warning: {0}
-
-
+ Upozornění: {0}The specified argument cannot be empty.
-
-
+ Zadaný argument nemůže být prázdný.The specified argument cannot be negative.
-
-
+ Zadaný argument nemůže být záporný.The specified argument must have the following type: {0}.
-
-
+ Zadaný argument musí být tohoto typu: {0}The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ Zadaný argument má následující vlastnost, která nemůže být prázdný řetězec: {0}The specified argument has the following property, which cannot be negative: {0}.
-
-
+ Zadaný argument má následující vlastnost, která nemůže být záporná: {0}The specified argument has the following property, which cannot be null: {0}.
-
-
+ Zadaný argument má následující vlastnost, která nemůže být null: {0}The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ Zadaný argument má následující vlastnost: {0}. Tato vlastnost musí být tohoto typu: {1}Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Při zpracování úlohy z fronty {0} došlo k neošetřené výjimce: {1}The {0} queue has already been disposed.
-
-
+ Fronta {0} se už uvolnila.The {0} queue cannot be disposed while paused.
-
-
+ Frontu {0} nejde uvolnit, když je pozastavená.Error getting process name.
-
-
+ Při získávání názvu procesu se stala chyba.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.Hostitele {0} nešlo najít. Ujistěte se, jestli je {0} nainstalovaný na počítači a dostupný v cestě určené proměnnou prostředí PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ Der Parameter darf nicht NULL oder leer sein.Error: {0}
-
-
+ Fehler: {0}Information: {0}
-
-
+ Informationen: {0}Warning: {0}
-
-
+ Warnung: {0}The specified argument cannot be empty.
-
-
+ Das angegebene Argument darf nicht leer sein.The specified argument cannot be negative.
-
-
+ Das angegebene Argument darf nicht negativ sein.The specified argument must have the following type: {0}.
-
-
+ Das angegebene Argument muss den folgenden Typ aufweisen: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ Das angegebene Argument weist die folgende Eigenschaft auf, die keine leere Zeichenfolge sein darf: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ Das angegebene Argument weist die folgende Eigenschaft auf, die nicht negativ sein darf: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ Das angegebene Argument weist die folgende Eigenschaft auf, die nicht NULL sein darf: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ Das angegebene Argument weist die folgende Eigenschaft auf: {0}. Diese Eigenschaft muss den folgenden Typ aufweisen: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Ausnahmefehler beim Verarbeiten eines Auftrags aus der Warteschlange "{0}": {1}The {0} queue has already been disposed.
-
-
+ Die Warteschlange {0} wurde bereits verworfen.The {0} queue cannot be disposed while paused.
-
-
+ Die Warteschlange {0} kann nicht verworfen werden, während sie angehalten ist.Error getting process name.
-
-
+ Fehler beim Abrufen des Prozessnamens.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.Der Host "{0}" wurde nicht gefunden. Stellen Sie sicher, dass "{0}" auf dem Computer installiert und in der PATH-Umgebungsvariablen verfügbar ist.
-
-
+ The parameter cannot be null or empty.
-
-
+ El parámetro no puede ser nulo ni estar vacío.Error: {0}
-
-
+ Error: {0}Information: {0}
-
-
+ Información: {0}Warning: {0}
-
-
+ Advertencia: {0}The specified argument cannot be empty.
-
-
+ El argumento especificado no puede estar vacío.The specified argument cannot be negative.
-
-
+ El argumento especificado no puede ser negativo.The specified argument must have the following type: {0}.
-
-
+ El argumento especificado debe tener el tipo {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ El argumento especificado tiene la siguiente propiedad, que no puede ser una cadena vacía: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ El argumento especificado tiene la siguiente propiedad, que no puede ser negativa: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ El argumento especificado tiene la siguiente propiedad, que no puede ser nula: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ El argumento especificado tiene la siguiente propiedad: {0}. Esta propiedad debe tener el tipo {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Se produjo una excepción no controlada al procesar un trabajo de la cola '{0}': {1}The {0} queue has already been disposed.
-
-
+ La cola {0} ya se ha eliminado.The {0} queue cannot be disposed while paused.
-
-
+ La cola {0} no se puede eliminar mientras está en pausa.Error getting process name.
-
-
+ Error al obtener el nombre del proceso.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.No se pudo encontrar el host "{0}". Asegúrese de que "{0}" está instalado en el equipo y está disponible en la variable de entorno PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ Le paramètre ne peut pas avoir une valeur null ou être vide.Error: {0}
-
-
+ Erreur : {0}Information: {0}
-
-
+ Informations : {0}Warning: {0}
-
-
+ Avertissement : {0}The specified argument cannot be empty.
-
-
+ L'argument spécifié ne peut pas être vide.The specified argument cannot be negative.
-
-
+ L'argument spécifié ne peut pas être négatif.The specified argument must have the following type: {0}.
-
-
+ L'argument spécifié doit être du type suivant : {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ L'argument spécifié a la propriété suivante, laquelle ne peut pas être une chaîne vide : {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ L'argument spécifié a la propriété suivante, laquelle ne peut pas être négative : {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ L'argument spécifié a la propriété suivante, laquelle ne peut pas être une valeur null : {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ L'argument spécifié a la propriété suivante : {0}. Cette propriété doit avoir le type suivant : {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Une exception non prise en charge s'est produite durant le traitement d'un travail à partir de la file d'attente '{0}' : {1}The {0} queue has already been disposed.
-
-
+ La file d'attente {0} a déjà été supprimée.The {0} queue cannot be disposed while paused.
-
-
+ Impossible de supprimer la file d'attente {0} pendant qu'elle est en pause.Error getting process name.
-
-
+ Erreur d'obtention du nom du processus.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.L'hôte '{0}' est introuvable. Vérifiez que '{0}' est installé sur la machine et qu'il est disponible dans la variable d'environnement PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ Il parametro non può essere vuoto o Null.Error: {0}
-
-
+ Errore: {0}Information: {0}
-
-
+ Informazioni: {0}Warning: {0}
-
-
+ Avviso: {0}The specified argument cannot be empty.
-
-
+ L'argomento specificato non può essere vuoto.The specified argument cannot be negative.
-
-
+ L'argomento specificato non può essere negativo.The specified argument must have the following type: {0}.
-
-
+ L'argomento specificato deve essere del tipo seguente: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ L'argomento specificato presenta la proprietà seguente, che non può essere una stringa vuota: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ L'argomento specificato presenta la proprietà seguente, che non può essere negativa: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ L'argomento specificato presenta la proprietà seguente, che non può essere Null: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ L'argomento specificato presenta la proprietà seguente: {0}. Tale proprietà deve essere del tipo seguente: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Si è verificata un'eccezione non gestita durante l'elaborazione di un processo dalla coda di '{0}': {1}The {0} queue has already been disposed.
-
-
+ La coda {0} è già stata eliminata.The {0} queue cannot be disposed while paused.
-
-
+ Non è possibile eliminare la coda {0} mentre è in sospeso.Error getting process name.
-
-
+ Si è verificato un errore durante il recupero del nome del processo.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.L'host '{0}' non è stato trovato. Assicurarsi che '{0}' sia installato nel computer e che sia disponibile nella variabile di ambiente PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ パラメーターを null または空にすることはできません。Error: {0}
-
-
+ エラー: {0}Information: {0}
-
-
+ 情報: {0}Warning: {0}
-
-
+ 警告: {0}The specified argument cannot be empty.
-
-
+ 指定した引数を空にすることはできません。The specified argument cannot be negative.
-
-
+ 指定した引数を負の値にすることはできません。The specified argument must have the following type: {0}.
-
-
+ 指定された引数は次の型でなければなりません: {0}。The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ 指定された引数には次のプロパティがあり、これを空の文字列にすることはできません: {0}。The specified argument has the following property, which cannot be negative: {0}.
-
-
+ 指定した引数には次のプロパティがあります。このプロパティを負の値にすることはできません: {0}。The specified argument has the following property, which cannot be null: {0}.
-
-
+ 指定した引数には次のプロパティがあります。このプロパティを null にすることはできません: {0}。The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ 指定された引数には次のプロパティがあります: {0}。このプロパティは次の型でなければなりません: {1}。Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ '{0}' キューからジョブを処理中にハンドルされない例外が発生しました: {1}。The {0} queue has already been disposed.
-
-
+ {0} キューは既に破棄されています。The {0} queue cannot be disposed while paused.
-
-
+ {0} キューは一時停止中に破棄できません。Error getting process name.
-
-
+ プロセス名の取得エラーです。Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.'{0}' ホストが見つかりませんでした。'{0}' がコンピューターにインストールされており、PATH 環境変数で使用できることを確認してください。
-
-
+ The parameter cannot be null or empty.
-
-
+ 매개 변수는 null이거나 비워 둘 수 없습니다.Error: {0}
-
-
+ 오류: {0}Information: {0}
-
-
+ 정보: {0}Warning: {0}
-
-
+ 경고: {0}The specified argument cannot be empty.
-
-
+ 지정한 인수는 비워 둘 수 없습니다.The specified argument cannot be negative.
-
-
+ 지정한 인수는 음수일 수 없습니다.The specified argument must have the following type: {0}.
-
-
+ 지정한 인수는 {0} 형식이어야 합니다.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ 지정한 인수에 {0} 속성이 있습니다. 이 속성은 빈 문자열일 수 없습니다.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ 지정한 인수에 {0} 속성이 있습니다. 이 속성은 음수일 수 없습니다.The specified argument has the following property, which cannot be null: {0}.
-
-
+ 지정한 인수에 {0} 속성이 있습니다. 이 속성은 null일 수 없습니다.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ 지정한 인수에 {0} 속성이 있습니다. 이 속성은 {1} 형식이어야 합니다.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ '{0}' 큐에서 작업을 처리하는 동안 처리되지 않은 예외가 발생했습니다. {1}The {0} queue has already been disposed.
-
-
+ {0} 큐가 이미 삭제되었습니다.The {0} queue cannot be disposed while paused.
-
-
+ 일시 중지된 동안에는 {0} 큐를 삭제할 수 없습니다.Error getting process name.
-
-
+ 프로세스 이름을 가져오는 동안 오류가 발생했습니다.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.‘{0}’ 호스트를 찾을 수 없습니다. ‘{0}’이(가) 컴퓨터에 설치되어 있고 PATH 환경 변수에서 사용할 수 있는지 확인하세요.
-
-
+ The parameter cannot be null or empty.
-
-
+ Parametr nie może mieć wartości null ani być pusty.Error: {0}
-
-
+ Błąd: {0}Information: {0}
-
-
+ Informacje: {0}Warning: {0}
-
-
+ Ostrzeżenie: {0}The specified argument cannot be empty.
-
-
+ Określony argument nie może być pusty.The specified argument cannot be negative.
-
-
+ Określony argument nie może być ujemny.The specified argument must have the following type: {0}.
-
-
+ Określony argument musi być następującego typu: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ Określony argument ma następującą właściwość, która nie może być pustym ciągiem: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ Określony argument ma następującą właściwość, która nie może być ujemna: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ Określony argument ma następującą właściwość, która nie może mieć wartości null: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ Określony argument ma następującą właściwość: {0}. Ta właściwość musi być następującego typu: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Wystąpił nieobsługiwany wyjątek podczas przetwarzania zadania z kolejki „{0}”: {1}The {0} queue has already been disposed.
-
-
+ Kolejka {0} została już usunięta.The {0} queue cannot be disposed while paused.
-
-
+ Nie można usunąć kolejki {0} podczas wstrzymania.Error getting process name.
-
-
+ Błąd podczas pobierania nazwy procesu.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.Nie można znaleźć hosta „{0}”. Upewnij się, że element „{0}” jest zainstalowany na maszynie i jest dostępny w zmiennej środowiskowej PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ O parâmetro não pode ser nulo ou estar vazio.Error: {0}
-
-
+ Erro: {0}Information: {0}
-
-
+ Informações: {0}Warning: {0}
-
-
+ Aviso: {0}The specified argument cannot be empty.
-
-
+ O argumento especificado não pode estar vazio.The specified argument cannot be negative.
-
-
+ O argumento especificado não pode ser negativo.The specified argument must have the following type: {0}.
-
-
+ O argumento especificado deve ter o seguinte tipo: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ O argumento especificado tem a seguinte propriedade, que não pode ser uma cadeia de caracteres vazia: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ O argumento especificado tem a seguinte propriedade, que não pode ser negativa: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ O argumento especificado tem a seguinte propriedade, que não pode ser nula: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ O argumento especificado tem a seguinte propriedade: {0}. Esta propriedade deve ter o seguinte tipo: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ Ocorreu uma exceção sem tratamento ao processar um trabalho da fila '{0}': {1}The {0} queue has already been disposed.
-
-
+ A fila {0} já foi descartada.The {0} queue cannot be disposed while paused.
-
-
+ A fila {0} não pode ser descartada enquanto está em pausa.Error getting process name.
-
-
+ Erro ao obter o nome do processo.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.Não foi possível encontrar o host '{0}'. Verifique se o '{0}' está instalado no computador e está disponível na variável de ambiente PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ Параметр не может быть пустым или иметь значение null.Error: {0}
-
-
+ Ошибка: {0}Information: {0}
-
-
+ Сведения: {0}Warning: {0}
-
-
+ Предупреждение: {0}The specified argument cannot be empty.
-
-
+ Указанный аргумент не может быть пустым.The specified argument cannot be negative.
-
-
+ Указанный аргумент не может быть отрицательным.The specified argument must have the following type: {0}.
-
-
+ Указанный аргумент должен иметь следующий тип: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ Указанный аргумент имеет следующее свойство, которое не может быть пустой строкой: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ Указанный аргумент имеет следующее свойство, которое не может быть отрицательным: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ Указанный аргумент имеет следующее свойство, которое не может иметь значение null: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ Указанный аргумент имеет следующее свойство: {0}. Это свойство должно относиться к следующему типу: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ При обработке задания из очереди "{0}" возникло необработанное исключение: {1}The {0} queue has already been disposed.
-
-
+ Очередь {0} уже удалена.The {0} queue cannot be disposed while paused.
-
-
+ Нельзя удалить приостановленную очередь {0}.Error getting process name.
-
-
+ Ошибка при получении имени процесса.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.Не удалось найти хост "{0}". Убедитесь, что "{0}" установлен на компьютере и доступен в переменной среды PATH.
-
-
+ The parameter cannot be null or empty.
-
-
+ Parametre null veya boş olamaz.Error: {0}
-
-
+ Hata: {0}Information: {0}
-
-
+ Bilgi: {0}Warning: {0}
-
-
+ Uyarı: {0}The specified argument cannot be empty.
-
-
+ Belirtilen bağımsız değişken boş olamaz.The specified argument cannot be negative.
-
-
+ Belirtilen bağımsız değişken negatif olamaz.The specified argument must have the following type: {0}.
-
-
+ Belirtilen bağımsız değişken şu türde olmalıdır: {0}.The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ Belirtilen bağımsız değişken, boş dize olamayacak olan şu özelliğe sahiptir: {0}.The specified argument has the following property, which cannot be negative: {0}.
-
-
+ Belirtilen bağımsız değişken, negatif olamayacak olan şu özelliğe sahiptir: {0}.The specified argument has the following property, which cannot be null: {0}.
-
-
+ Belirtilen bağımsız değişken, null olamayacak olan şu özelliğe sahiptir: {0}.The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ Belirtilen bağımsız değişken şu özelliğe sahiptir: {0}. Bu özellik şu türde olmalıdır: {1}.Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ '{0}' kuyruğundan bir iş işlenirken, işlenmeyen özel durum oluştu: {1}The {0} queue has already been disposed.
-
-
+ {0} kuyruğu zaten atıldı.The {0} queue cannot be disposed while paused.
-
-
+ {0} kuyruğu duraklatılmış durumdayken atılamaz.Error getting process name.
-
-
+ İşlem adı alınırken hata oluştu.Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.'{0}' konağı bulunamadı. '{0}' konağının makinede yüklü olduğundan ve PATH ortam değişkeninde bulunduğundan emin olun.
-
-
+ The parameter cannot be null or empty.
-
-
+ 参数不能为 NULL 或为空。Error: {0}
-
-
+ 错误: {0}Information: {0}
-
-
+ 信息: {0}Warning: {0}
-
-
+ 警告: {0}The specified argument cannot be empty.
-
-
+ 指定的参数不能为空。The specified argument cannot be negative.
-
-
+ 指定的参数不能为负。The specified argument must have the following type: {0}.
-
-
+ 指定的参数都必须具有以下类型: {0}。The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ 指定的参数具有以下属性: {0},且不能为空字符串。The specified argument has the following property, which cannot be negative: {0}.
-
-
+ 指定的参数具有以下属性: {0},且不能为负。The specified argument has the following property, which cannot be null: {0}.
-
-
+ 指定的参数具有以下属性: {0},且不能为 null。The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ 指定的参数具有以下属性: {0}。此属性必须具有以下类型: {1}。Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ 处理“{0}”队列中的作业时发生未处理的异常: {1}The {0} queue has already been disposed.
-
-
+ 已处置 {0} 队列。The {0} queue cannot be disposed while paused.
-
-
+ 暂停时无法处置 {0} 队列。Error getting process name.
-
-
+ 获取进程名称时出错。Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.找不到“{0}”主机。请确保计算机上已安装“{0}”且位于 PATH 环境变量中。
-
-
+ The parameter cannot be null or empty.
-
-
+ 參數不可為 null 或空白。Error: {0}
-
-
+ 錯誤: {0}Information: {0}
-
-
+ 資訊: {0}Warning: {0}
-
-
+ 警告: {0}The specified argument cannot be empty.
-
-
+ 指定的引數不可為空白。The specified argument cannot be negative.
-
-
+ 指定的引數不可為負數。The specified argument must have the following type: {0}.
-
-
+ 指定的引數必須具備下列類型: {0}。The specified argument has the following property, which cannot be an empty string: {0}.
-
-
+ 指定的引數具有下列屬性,且不可為空字串: {0}。The specified argument has the following property, which cannot be negative: {0}.
-
-
+ 指定的引數具有下列屬性,且不可為負數: {0}。The specified argument has the following property, which cannot be null: {0}.
-
-
+ 指定的引數具有下列屬性,且不可為 null: {0}。The specified argument has the following property: {0}. This property must have the following type: {1}.
-
-
+ 指定的引數具有下列屬性: {0}。此屬性必須具有下列類型: {1}。Unhandled exception occurred while processing a job from the '{0}' queue: {1}
-
-
+ 從 '{0}' 佇列處理工作時,發生未處理的例外狀況: {1}The {0} queue has already been disposed.
-
-
+ 已處置 {0} 佇列。The {0} queue cannot be disposed while paused.
-
-
+ 暫停時無法處置 {0} 佇列。Error getting process name.
-
-
+ 取得處理序名稱時發生錯誤。Could not find '{0}' host. Make sure that '{0}' is installed on the machine and is available in PATH environment variable.找不到 '{0}' 主機。請確認 '{0}' 已安裝在機器上,而且可在 PATH 環境變數中使用。
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Při vytváření instance nástroje zjišťování došlo k výjimce: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Ignoruje se zadaný duplicitní zdroj {0}.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ V době, kdy nástroj zjišťování testů {0} načítal testy, došlo k výjimce. Výjimka: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Při volání prováděcího modulu {0} došlo k výjimce: {1}Could not find file {0}.
-
-
+ Nepovedlo se najít soubor {0}.
@@ -44,20 +39,17 @@
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.
-
-
+ Ignoruje se prováděcí modul testování, který odpovídá nástroji zjišťování testů {0}, protože nástroj zjišťování nemá atribut DefaultExecutorUri. Možná bude nutné přeinstalovat doplněk adaptéru testu.Failed to initialize client proxy: could not connect to test process.
-
-
+ Nepovedlo se inicializovat proxy klienta: nešlo se připojit k procesu testu.This operation is not allowed in the context of a non-debug run.
-
-
+ Tato operace se v kontextu běhu bez ladění nepovoluje.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Žádný ze zadaných zdrojů {0} není platný. Opravte chyby/upozornění výše a zkuste to znovu. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Filtru neodpovídá žádný test, protože obsahuje nejméně jednu vlastnost, která není platná ({0}). Zadejte výraz filtru, který obsahuje platné vlastnosti ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.Nejde najít {0}. Ujistěte se, že na počítači je nainstalovaný dotnet.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Proces testhost se ukončil s chybou: {0}. Další informace najdete v diagnostických protokolech.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.Je povolené ladění kolekce dat. Pokud chcete pokračovat, připojte prosím ladicí program k procesu kolekce dat.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.V {0} nejsou dostupné žádné testy. Ujistěte se, že nástroje pro zjišťování a provádění testů jsou zaregistrované a že jsou vhodně zvolená nastavení verzí platformy a architektury, a zkuste to znovu.
-
-
+ Logging TestHost Diagnostics in file: {0}Protokolování diagnostiky TestHost v souboru: {0}
-
-
+ Failed to launch testhost with error: {0}Nepovedlo se spustit hostitele testu kvůli této chybě: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.Možnost ExecutionThreadApartmentState se pro rozhraní nepodporuje: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Používáte starší verzi sady Microsoft.NET.Test.Sdk. Přejděte prosím na verzi 15.3.0 nebo vyšší.
-
-
+ Could not find extensions: {0}Nepovedlo se najít rozšíření: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Mění se vyhledávání adaptéru. Další informace najdete tady: https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap.
-
-
+ No test matches the given testcase filter `{0}` in {1}Žádný test neodpovídá danému filtru testovacích případů {0} v: {1}
-
-
+ Discovery of tests cancelled.Zjišťování testů bylo zrušeno.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Ladicí program se nedá připojit k výchozímu hostiteli testů s ID procesu {0}.
-
-
+ {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.{0} Při pokusu o vytvoření složky TestResults v uvedeném umístění došlo k odepření přístupu. Tato výjimka se vyvolala, protože spouštíte vstest.console.exe ze složky, která vyžaduje, abyste měli přístup pro zápis. Pokud chcete problém vyřešit, spusťte prosím vstest.console.exe ze složky, ve které máte oprávnění k zápisu.
-
-
+ Could not find an available proxy to deque.Nepovedlo se najít dostupný proxy server, který se má odebrat z fronty.
-
-
+ Proxy with id {0} is not managed by the current session manager.Aktuální správce relace nespravuje proxy s ID {0}.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Proxy s ID {0} je už k dispozici a nedá se znovu zařadit do fronty.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Ausnahme beim Instanziieren des Discoverers: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Die angegebene doppelte Quelle "{0}" wird ignoriert.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Ausnahme beim Laden von Tests durch den Testdiscoverer "{0}". Ausnahme: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Ausnahme beim Aufrufen von Executor "{0}": {1}Could not find file {0}.
-
-
+ Die Datei "{0}" wurde nicht gefunden.
@@ -44,20 +39,17 @@
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.
-
-
+ Der Testexecutor, der dem Testdiscoverer "{0}" entspricht, wird ignoriert, weil der Discoverer nicht das DefaultExecutorUri-Attribut aufweist. Sie müssen ggf. das Testadapter-Add-In erneut installieren.Failed to initialize client proxy: could not connect to test process.
-
-
+ Fehler beim Initialisieren des Clientproxys: Es konnte keine Verbindung mit dem Testprozess hergestellt werden.This operation is not allowed in the context of a non-debug run.
-
-
+ Dieser Vorgang ist im Kontext einer Nichtdebugausführung unzulässig.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Keine der angegebenen Quellen "{0}" ist gültig. Beheben Sie die oben aufgeführten Fehler/Warnungen, und versuchen Sie es erneut. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Es stimmten keine Tests mit dem Filter überein, weil er mindestens eine ungültige Eigenschaft enthält ({0}). Geben Sie einen Filterausdruck mit gültigen Eigenschaften an ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.{0} wurde nicht gefunden. Stellen Sie sicher, dass das dotnet auf dem Computer installiert ist.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Der TestHost-Prozess wurde mit folgendem Fehler beendet: {0}. Weitere Informationen finden Sie in den Diagnoseprotokollen.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.DataCollector-Debugging ist aktiviert. Fügen Sie den Debugger an den Datensammlerprozess an, um den Vorgang fortzusetzen.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.In "{0}" ist kein Test verfügbar. Stellen Sie sicher, dass die Testdiscoverer und -executors registriert und die Versionseinstellungen für Plattform und Framework richtig sind, und wiederholen Sie den Vorgang.
-
-
+ Logging TestHost Diagnostics in file: {0}Die TestHost-Diagnose wird in der Datei {0} protokolliert.
-
-
+ Failed to launch testhost with error: {0}Fehler beim Starten von Testhost: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.Die ExecutionThreadApartmentState-Option wird für das Framework nicht unterstützt: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Sie verwenden eine ältere Version von Microsoft.NET.Test.Sdk. Wechseln Sie zu Version 15.3.0 oder höher.
-
-
+ Could not find extensions: {0}Erweiterungen nicht gefunden: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Die Adaptersuche wird gerade geändert. Weitere Informationen finden Sie unter https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap.
-
-
+ No test matches the given testcase filter `{0}` in {1}Kein Test entspricht dem angegebenen Testfallfilter "{0}" in "{1}".
-
-
+ Discovery of tests cancelled.Die Ermittlung von Tests wurde abgebrochen.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Der Debugger kann nicht an den Standardtesthost mit der Prozess-ID {0} angefügt werden.
-
-
+ {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.{0} Beim Erstellen des Ordners "TestResults" am angegebenen Speicherort wurde der Zugriff verweigert. Sie erhalten diese Ausnahme, weil Sie "vstest.console.exe" in einem Ordner ausführen, für den Schreibzugriff erforderlich ist. So beheben Sie das Problem: Führen Sie "vstest.console.exe" in einem Ordner aus, für den Sie Schreibberechtigungen besitzen.
-
-
+ Could not find an available proxy to deque.Es wurde kein verfügbarer Proxy für die Deque gefunden.
-
-
+ Proxy with id {0} is not managed by the current session manager.Der Proxy mit der ID {0} wird nicht vom aktuellen Sitzungs-Manager verwaltet.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Der Proxy mit der ID {0} ist bereits verfügbar und kann nicht erneut in die Warteschlange eingereiht werden.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Se produjo una excepción al crear una instancia del programa de detección: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Se omitirá el origen duplicado especificado ({0}).An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Se produjo una excepción cuando el programa de detección de pruebas '{0}' estaba cargando pruebas. Excepción: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Se produjo una excepción al invocar al ejecutor '{0}': {1}Could not find file {0}.
-
-
+ No se encuentra el archivo {0}.
@@ -44,20 +39,17 @@
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.
-
-
+ Se omitirá el ejecutor de pruebas correspondiente al programa de detección de pruebas {0}, porque este último no tiene el atributo DefaultExecutorUri. Puede ser necesario reinstalar el complemento del adaptador de prueba.Failed to initialize client proxy: could not connect to test process.
-
-
+ No se pudo inicializar el proxy de cliente: no se puede conectar al proceso de prueba.This operation is not allowed in the context of a non-debug run.
-
-
+ Esta operación no se permite en el contexto de una ejecución que no sea de depuración.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Ninguno de los orígenes especificados ({0}) es válido. Corrija los errores o advertencias y vuelva a intentarlo. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Ninguna prueba coincide con el filtro porque contiene una o varias propiedades no válidas ({0}). Especifique una expresión de filtro que contenga propiedades válidas ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.No se pudo encontrar {0}. Asegúrese de que dotnet esté instalado en la máquina.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.El proceso del host de prueba finalizó con el siguiente error: {0}. Consulte los registros de diagnóstico para obtener más información.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.La depuración del recopilador de datos está habilitada. Asocie el depurador al proceso del recopilador de datos para continuar.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.No hay ninguna prueba disponible en {0}. Asegúrese de que los detectores y ejecutores de pruebas están registrados y de que la configuración de versión de la plataforma y de Framework es correcta y vuelva a intentarlo.
-
-
+ Logging TestHost Diagnostics in file: {0}Registrando diagnóstico de TestHost en el archivo: {0}
-
-
+ Failed to launch testhost with error: {0}No se pudo iniciar el host de prueba con el error: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.Opción ExecutionThreadApartmentState de ejecución no admitida para el marco: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Está utilizando una versión anterior de Microsoft.NET.Test.Sdk. Cámbiese a una versión igual o superior a 15.3.0.
-
-
+ Could not find extensions: {0}No se pudieron encontrar las extensiones {0}.
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Se está cambiando la búsqueda de adaptador. Siga https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap para obtener más detalles.
-
-
+ No test matches the given testcase filter `{0}` in {1}Ninguna prueba coincide con el filtro de casos de prueba proporcionado "{0}" en {1}
-
-
+ Discovery of tests cancelled.Se ha cancelado la detección de las pruebas.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.No se puede asociar el depurador al host de prueba predeterminado con el id. de proceso: {0}.
-
-
+ {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.{0} Se denegó el acceso al intentar crear la carpeta "TestResults" en la ubicación mencionada. Está recibiendo esta excepción porque está ejecutando vstest.console.exe desde una carpeta que requiere acceso de escritura. Para solucionar la incidencia: ejecute vstest.console.exe desde una carpeta en la que tenga privilegios de escritura.
-
-
+ Could not find an available proxy to deque.No se encontró ningún proxy disponible para quitar de la cola.
-
-
+ Proxy with id {0} is not managed by the current session manager.El administrador de la sesión actual no administra el proxy con el identificador {0}.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.El proxy con el identificador {0} ya está disponible y no se puede volver a poner en cola.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Une exception s'est produite durant l'instanciation du découvreur : {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ La source dupliquée spécifiée '{0}' est ignorée.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Une exception s'est produite durant le chargement des tests par le découvreur de tests '{0}'. Exception : {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Une exception s'est produite durant l'appel de l'exécuteur '{0}' : {1}Could not find file {0}.
-
-
+ Fichier {0} introuvable.
@@ -44,20 +39,17 @@
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.
-
-
+ L'exécuteur de tests correspondant au découvreur de tests {0} est ignoré, car le découvreur n'a pas l'attribut DefaultExecutorUri. Vous devrez peut-être réinstaller le complément d'adaptateur de test.Failed to initialize client proxy: could not connect to test process.
-
-
+ Échec d'initialisation du proxy client : connexion impossible au processus de test.This operation is not allowed in the context of a non-debug run.
-
-
+ Cette opération n'est pas autorisée dans le contexte d'une exécution qui ne sert pas au débogage.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Aucune des sources spécifiées '{0}' n'est valide. Corrigez les erreurs/avertissements ci-dessus, puis réessayez. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Aucun test ne correspond au filtre, car il contient une ou plusieurs propriétés non valides ({0}). Spécifiez une expression de filtre contenant des propriétés valides ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.{0} est introuvable. Vérifiez que le dotnet est installé sur la machine.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Le processus Testhost s'est arrêté. Erreur : {0}. Pour plus d'informations, consultez les journaux de diagnostic.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.Le débogage de collecteur de données est activé. Attachez le débogueur au processus datacollector pour continuer.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.Aucun test n'est disponible dans {0}. Vérifiez que les découvreurs et exécuteurs de tests sont inscrits. Vérifiez également que les paramètres de version de plateforme et de framework sont appropriés, puis réessayez.
-
-
+ Logging TestHost Diagnostics in file: {0}Journalisation des diagnostics TestHost dans le fichier : {0}
-
-
+ Failed to launch testhost with error: {0}Échec du lancement de l'hôte de test. Erreur : {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.L'option ExecutionThreadApartmentState n'est pas prise en charge pour le framework : {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Vous utilisez une ancienne version de Microsoft.NET.Test.Sdk. Passez à une version égale ou supérieure à la version 15.3.0.
-
-
+ Could not find extensions: {0}Extensions introuvables : {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.La fonctionnalité de recherche d’adaptateur fait actuellement l’objet de modifications. Pour plus d’informations, consultez https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap.
-
-
+ No test matches the given testcase filter `{0}` in {1}Aucun test ne correspond au filtre testcase donné `{0}` dans {1}
-
-
+ Discovery of tests cancelled.Découverte de tests annulée.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Impossible d'attacher le débogueur à l'hôte de test par défaut ayant l'ID de processus : {0}.
-
-
+ {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.{0} Accès refusé durant la tentative de création du dossier "TestResults" à l'emplacement indiqué. Vous obtenez cette exception, car vous exécutez vstest.console.exe à partir d'un dossier qui nécessite un accès en écriture. Pour résoudre le problème, exécutez vstest.console.exe à partir d'un dossier sur lequel vous disposez de privilèges d'accès en écriture.
-
-
+ Could not find an available proxy to deque.Impossible de localiser un proxy disponible à dépiler.
-
-
+ Proxy with id {0} is not managed by the current session manager.Le proxy ayant l'ID {0} n'est pas géré par le gestionnaire de session actuel.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Le proxy ayant l'ID {0} est déjà disponible et ne peut pas être empilé à nouveau.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Si è verificata un'eccezione durante la creazione dell'istanza dell'agente di individuazione: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ L'origine duplicata specificata verrà ignorata: '{0}'.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Si è verificata un'eccezione durante il caricamento dei test da parte dell'agente di individuazione test '{0}'. Eccezione: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Si è verificata un'eccezione durante la chiamata dell'executor '{0}': {1}Could not find file {0}.
-
-
+ Il file {0} non è stato trovato.
@@ -44,20 +39,17 @@
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.
-
-
+ L'executor di test corrispondente all'agente di individuazione del test {0} verrà ignorato perché manca l'attributo DefaultExecutorUri dell'agente di individuazione. Potrebbe essere necessario reinstallare il componente aggiuntivo dell'adattatore di test.Failed to initialize client proxy: could not connect to test process.
-
-
+ Inizializzazione del proxy client non riuscita: non è stato possibile connettersi al processo di test.This operation is not allowed in the context of a non-debug run.
-
-
+ Questa operazione non è consentita nel contesto di un'esecuzione non di debug.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Nessuna delle origini specificate '{0}' è valida. Correggere gli errori/avvisi precedenti e riprovare. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Nessun test corrisponde al filtro perché contiene una o più proprietà non valide ({0}). Specificare un'espressione di filtro contenente proprietà valide ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.{0} non è stato trovato. Assicurarsi che dotnet sia installato nel computer.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Il processo testhost è terminato con l'errore {0}. Per altre informazioni, vedere i log di diagnostica.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.Il debug dell'agente di raccolta dati è abilitato. Per continuare, collegare il debugger al processo dell'agente di raccolta dati.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.Non ci sono test disponibili in {0}. Assicurarsi che l'agente di individuazione test e gli executor di test siano registrati e che le impostazioni delle versioni di piattaforma e framework siano appropriate, quindi riprovare.
-
-
+ Logging TestHost Diagnostics in file: {0}Registrazione della diagnostica di TestHost nel file: {0}
-
-
+ Failed to launch testhost with error: {0}Non è stato possibile avviare testhost. Errore: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.L'opzione ExecutionThreadApartmentState non è supportata per il framework: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.La versione di Microsoft.NET.Test.Sdk è obsoleta. Passare alla versione 15.3.0 o a una versione successiva.
-
-
+ Could not find extensions: {0}Non è stato possibile trovare le estensioni: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.La ricerca degli adattatori verrà modificata a breve. Per maggiori dettagli, vedere https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap.
-
-
+ No test matches the given testcase filter `{0}` in {1}Nessun test corrisponde al filtro di test case specificato `{0}` in {1}
-
-
+ Discovery of tests cancelled.Individuazione dei test annullata.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Non è possibile collegare il debugger all'host di test predefinito con ID processo {0}.
-
-
+ {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.{0} Accesso negato durante il tentativo di creare la cartella "TestResults" nel percorso indicato. Si riceve questa eccezione perché si esegue vstest.console.exe da una cartella per cui è necessario l'accesso in scrittura. Per risolvere il problema, eseguire vstest.console.exe da una cartella per cui si hanno privilegi di scrittura.
-
-
+ Could not find an available proxy to deque.Non è stato possibile trovare un proxy disponibile da rimuovere dalla coda.
-
-
+ Proxy with id {0} is not managed by the current session manager.Il proxy con ID {0} non è gestito dallo strumento di gestione sessioni corrente.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Il proxy con ID {0} è già disponibile e non può essere riaccodato.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ 探索プログラムのインスタンス化中に例外が発生しました: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ 指定された重複データ ソース '{0}' を無視します。An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ テスト探索プログラム '{0}' がテストを読み込んでいるときに例外が発生しました。例外: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ 実行プログラム '{0}' の呼び出し中に例外が発生しました: {1}Could not find file {0}.
-
-
+ ファイル {0} は見つかりませんでした。
@@ -44,20 +39,17 @@
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.
-
-
+ テスト探索プログラム {0} には DefaultExecutorUri 属性が含まれていないため、このテスト探索プログラムに対応するテスト実行プログラムを無視しています。テスト アダプター アドインの再インストールが必要になる場合があります。Failed to initialize client proxy: could not connect to test process.
-
-
+ クライアント プロキシを初期化できませんでした。テスト プロセスに接続できませんでした。This operation is not allowed in the context of a non-debug run.
-
-
+ この操作は、非デバッグ実行のコンテキストでは許可されていません。
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ 指定されたソース '{0}' がいずれも有効ではありません。上記のエラーおよび警告を修正してから、もう一度お試しください。,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ フィルターに一致するテストがありません。フィルターに無効なプロパティが 1 つ以上含まれています ({0})。有効なプロパティを含むフィルター式 ({1}) を指定してください。Could not find {0}. Make sure that the dotnet is installed on the machine.{0} が見つかりませんでした。dotnet がマシンにインストールされていることを確認してください。
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Testhost プロセスがエラーで終了しました: {0}。詳細については、診断ログを確認してください。
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.DataCollector のデバッグが有効です。続行するにはデバッガーを datacollector プロセスにアタッチしてください。
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.{0} で使用できるテストはありません。テスト探索プログラムおよび実行プログラムが登録されており、プラットフォームおよびフレームワークのバージョン設定が適切であることを確認してから、もう一度お試しください。
-
-
+ Logging TestHost Diagnostics in file: {0}次のファイルで TestHost 診断をログ記録しています: {0}
-
-
+ Failed to launch testhost with error: {0}エラーが発生したため、TestHost を起動できませんでした: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.フレームワークでの ThreadApartmentState オプションの実行はサポートされていません: {0}。
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Microsoft.NET.Test.Sdk の古いバージョンを使用しています。15.3.0 以降のバージョンに移行することをお勧めします。
-
-
+ Could not find extensions: {0}拡張機能が見つかりませんでした: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.アダプター検索は変更中です。詳細については、https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap をご覧ください。
-
-
+ No test matches the given testcase filter `{0}` in {1}指定のテストケース フィルター `{0}` に一致するテストは {1} にありません
-
-
+ Discovery of tests cancelled.テストの検出が取り消されました。
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.デバッガーをプロセス ID: {0} の既定のテスト ホストにアタッチできません。
-
-
+ {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.{0} 記載した場所に "TestResults" フォルダーを作成しようとしたときにアクセスが拒否されました。書き込みアクセスを必要とするフォルダーから vstest.console.exe を実行しているため、この例外が発生しています。この問題を解決するには、書き込み特権のあるフォルダーから vstest.console.exe を実行してください。
-
-
+ Could not find an available proxy to deque.デキューするために使用できるプロキシが見つかりませんでした。
-
-
+ Proxy with id {0} is not managed by the current session manager.ID が {0} のプロキシは、現在のセッション マネージャーで管理されません。
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.ID が {0} のプロキシは、既に使用可能になっているため、再度エンキューすることはできません。
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ {0} Discoverer를 인스턴스화하는 중 예외가 발생했습니다.
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ 지정한 중복되는 '{0}' 소스를 무시합니다.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ 테스트 Discoverer '{0}'에서 테스트를 로드하는 동안 예외가 발생했습니다. 예외: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ '{0}' Executor를 호출하는 동안 예외가 발생했습니다. {1}Could not find file {0}.
-
-
+ {0} 파일을 찾을 수 없습니다.
@@ -44,20 +39,17 @@
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.
-
-
+ Discoverer에 DefaultExecutorUri 특성이 없으므로 테스트 Discoverer {0}에 해당하는 테스트 Executor를 무시합니다. 테스트 어댑터 추가 기능을 다시 설치해야 할 수 있습니다.Failed to initialize client proxy: could not connect to test process.
-
-
+ 클라이언트 프록시를 초기화하지 못했습니다. 테스트 프로세스에 연결할 수 없습니다.This operation is not allowed in the context of a non-debug run.
-
-
+ 디버그가 아닌 실행의 컨텍스트에서는 이 작업을 수행할 수 없습니다.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ 지정한 '{0}' 소스가 올바르지 않습니다. 위의 오류/경고를 해결한 후 다시 시도하세요. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ 필터에 잘못된 속성({0})이 하나 이상 포함되어 있으므로 해당 필터와 일치하는 테스트가 없습니다. 유효한 속성({1})을 포함하는 필터 식을 지정하세요.Could not find {0}. Make sure that the dotnet is installed on the machine.{0}을(를) 찾을 수 없습니다. 컴퓨터에 dotnet이 설치되어 있는지 확인하세요.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Testhost 프로세스가 종료되었습니다(오류: {0}). 자세한 내용은 진단 로그를 확인하세요.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.DataCollector 디버깅을 사용하도록 설정했습니다. datacollector 프로세스를 계속하려면 디버거를 연결하세요.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.{0}에서 테스트를 사용할 수 없습니다. 테스트 Discoverer 및 Executor가 등록되고 플랫폼 및 프레임워크 버전 설정이 적절한지 확인하고 다시 시도하세요.
-
-
+ Logging TestHost Diagnostics in file: {0}{0} 파일에 TestHost Diagnostics 로깅 중
-
-
+ Failed to launch testhost with error: {0}Testhost를 시작하지 못했습니다(오류: {0}).
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.프레임워크 {0}에 대해 ExecutionThreadApartmentState 옵션이 지원되지 않습니다.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.이전 버전의 Microsoft.NET.Test.Sdk를 사용하고 있습니다. 15.3.0 이상 버전으로 이동하세요.
-
-
+ Could not find extensions: {0}확장을 찾을 수 없음: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.어댑터 조회가 변경됩니다. 자세한 내용은 https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap을 참조하세요.
-
-
+ No test matches the given testcase filter `{0}` in {1}{1}에 지정된 테스트 사례 필터 `{0}`과(와) 일치하는 테스트가 없습니다.
-
-
+ Discovery of tests cancelled.테스트 검색이 취소되었습니다.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.프로세스 ID가 {0}인 기본 테스트 호스트에 디버거를 연결할 수 없습니다.
-
-
+ {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.{0} "TestResults" 폴더를 언급된 위치에 만드는 동안 액세스가 거부되었습니다. 쓰기 권한이 필요한 폴더에서 vstest.console.exe를 실행하고 있으므로 이 예외가 발생했습니다. 이 문제를 해결하려면 쓰기 권한이 있는 폴더에서 vstest.console.exe를 실행하세요.
-
-
+ Could not find an available proxy to deque.큐에서 제거하기 위해 사용할 수 있는 프록시를 찾을 수 없습니다.
-
-
+ Proxy with id {0} is not managed by the current session manager.ID가 {0}인 프록시가 현재 세션 관리자에서 관리되지 않습니다.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.ID가 {0}인 프록시를 이미 사용할 수 있으며 큐에 다시 넣을 수 없습니다.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Wystąpił wyjątek podczas tworzenia wystąpienia wykrywacza: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Określone zduplikowane źródło „{0}” zostanie zignorowane.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Wystąpił wyjątek podczas ładowania testów przez wykrywacz testów „{0}”. Wyjątek: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Wystąpił wyjątek podczas wywoływania modułu wykonywania „{0}”: {1}Could not find file {0}.
-
-
+ Nie można odnaleźć pliku {0}.
@@ -44,20 +39,17 @@
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.
-
-
+ Moduł wykonywania testów odpowiadający wykrywaczowi testów {0} zostanie zignorowany, ponieważ wykrywacz nie ma atrybutu DefaultExecutorUri. Konieczna może być ponowna instalacja dodatku adaptera testowego.Failed to initialize client proxy: could not connect to test process.
-
-
+ Zainicjowanie serwera proxy klienta nie powiodło się: nie można nawiązać połączenia z procesem testowania.This operation is not allowed in the context of a non-debug run.
-
-
+ Ta operacja jest niedozwolona w kontekście uruchamiania bez debugowania.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Wszystkie określone źródła „{0}” są nieprawidłowe. Napraw powyższe błędy/ostrzeżenia i spróbuj ponownie. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Brak testów zgodnych z filtrem, ponieważ zawiera on co najmniej jedną nieprawidłową właściwość ({0}). Określ wyrażenie filtru zawierające prawidłowe właściwości ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.Nie znaleziono elementu {0}. Upewnij się, że program dotnet jest zainstalowany na maszynie.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Zakończono proces testhost z powodu błędu: {0}. Sprawdź dzienniki diagnostyczne, aby uzyskać więcej informacji.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.Debugowanie modułu zbierającego dane zostało włączone. Dołącz debuger do procesu datacollector, aby kontynuować.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.W elemencie {0} nie są dostępne żadne testy. Upewnij się, że wykrywacze i moduły wykonywania testów są zarejestrowane oraz że ustawienia wersji platformy i struktury są odpowiednie, a następnie spróbuj ponownie.
-
-
+ Logging TestHost Diagnostics in file: {0}Rejestrowanie diagnostyki TestHost w pliku: {0}
-
-
+ Failed to launch testhost with error: {0}Nie można uruchomić hosta testów. Błąd: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.Opcja ExecutionThreadApartmentState nie jest obsługiwana dla platformy: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Używamy starszej wersji zestawu Microsoft.NET.Test.Sdk. Przejdź na wersję 15.3.0 lub nowszą.
-
-
+ Could not find extensions: {0}Nie można znaleźć rozszerzeń: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Wyszukiwanie adaptera jest zmieniane, zobacz https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap w celu uzyskania dalszych szczegółów.
-
-
+ No test matches the given testcase filter `{0}` in {1}Żaden test nie jest zgodny z podanym filtrem przypadku testowego „{0}” w elemencie {1}
-
-
+ Discovery of tests cancelled.Odnajdywanie testów zostało anulowane.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Nie można dołączyć debugera do domyślnego hosta testowego z identyfikatorem procesu: {0}.
-
-
+ {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.{0} Odmowa dostępu podczas próby utworzenia folderu „TestResults” w określonej lokalizacji. Widzisz ten wyjątek, ponieważ program vstest.console.exe został uruchomiony z folderu wymagającego dostępu do zapisu. Aby rozwiązać ten problem: uruchom program vstest.console.exe z folderu, w którym masz uprawnienia do zapisu.
-
-
+ Could not find an available proxy to deque.Nie można było znaleźć dostępnego serwera proxy do umieszczenia w kolejce dwukierunkowej.
-
-
+ Proxy with id {0} is not managed by the current session manager.Serwer proxy o identyfikatorze {0} nie jest zarządzany przez bieżącego menedżera sesji.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Serwer proxy o identyfikatorze {0} jest już dostępny i nie można go ponownie umieścić w kolejce.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Ocorreu uma exceção ao criar uma instância do discoverer: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Ignorando a fonte duplicada especificada '{0}'.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ Ocorreu uma exceção enquanto o discoverer de testes '{0}' estava carregando testes. Exceção: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ Ocorreu uma exceção ao chamar o executor '{0}': {1}Could not find file {0}.
-
-
+ Não foi possível localizar o arquivo {0}.
@@ -44,20 +39,17 @@
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.
-
-
+ Ignorando o executor de teste correspondente ao discoverer de teste {0} porque o discoverer não tem o atributo DefaultExecutorUri. Talvez seja necessário instalar novamente o suplemento do adaptador de teste.Failed to initialize client proxy: could not connect to test process.
-
-
+ Falha ao inicializar o proxy do cliente: não foi possível se conectar ao processo de teste.This operation is not allowed in the context of a non-debug run.
-
-
+ Esta operação não é permitida no contexto de uma execução sem depuração.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Nenhuma das fontes especificadas '{0}' é válida. Corrija os erros/avisos acima e tente novamente. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Nenhum teste correspondeu ao filtro porque ele contém uma ou mais propriedades que não são válidas ({0}). Especifique a expressão de filtro contendo as propriedades válidas ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.Não foi possível localizar {0}. Certifique-se de que o dotnet esteja instalado no computador.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.O processo do testhost foi encerrado com o erro: {0}. Verifique os logs de diagnóstico para obter mais informações.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.A depuração do DataCollector está habilitada. Anexe o depurador ao processo datacollector para continuar.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.Não há nenhum teste disponível em {0}. Verifique se o detector e os executores de teste estão registrados e se as configurações de versão da estrutura da plataforma & são apropriadas e tente novamente.
-
-
+ Logging TestHost Diagnostics in file: {0}Registro em log do diagnóstico TestHost no arquivo: {0}
-
-
+ Failed to launch testhost with error: {0}Falha ao iniciar o host de teste com o erro: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.A opção ExecutionThreadApartmentState não tem suporte para a estrutura: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Você está usando uma versão mais antiga do Microsoft.NET.Test.Sdk. Mude para uma versão igual ou maior que 15.3.0.
-
-
+ Could not find extensions: {0}Não foi possível encontrar as extensões: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.A pesquisa do adaptador está sendo alterada, siga https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap para obter mais detalhes.
-
-
+ No test matches the given testcase filter `{0}` in {1}Nenhum teste corresponde ao filtro de testcase `{0}` determinado no {1}
-
-
+ Discovery of tests cancelled.Descoberta de testes cancelada.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Não é possível anexar o depurador ao host de teste padrão com a ID de processo: {0}.
-
-
+ {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.{0} Acesso negado ao tentar criar a pasta "TestResults" no local mencionado. Você está recebendo esta exceção porque está executando o vstest.console.exe em uma pasta que requer acesso para gravação. Para resolver o problema: execute vstest.console.exe em uma pasta na qual você tenha privilégios de gravação.
-
-
+ Could not find an available proxy to deque.Não foi possível encontrar um proxy disponível para deque.
-
-
+ Proxy with id {0} is not managed by the current session manager.O proxy com a ID {0} não é gerenciado pelo gerenciador de sessão atual.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.O proxy com a ID {0} já está disponível e não pode ser enfileirado novamente.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ При создании экземпляра средства обнаружения возникло исключение: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Указанный повторяющийся источник "{0}" игнорируется.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ При загрузке тестов средством обнаружения тестов "{0}" возникло исключение. Исключение: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ При вызове исполнителя "{0}" возникло исключение: {1}Could not find file {0}.
-
-
+ Не удалось найти файл {0}.
@@ -44,20 +39,17 @@
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.
-
-
+ Исполнитель теста, соответствующий средству обнаружения тестов {0}, пропускается, так как у средства обнаружения нет атрибута DefaultExecutorUri. Возможно, необходимо переустановить надстройку адаптера теста.Failed to initialize client proxy: could not connect to test process.
-
-
+ Не удалось инициализировать прокси клиента: не удалось подключиться к процессу теста.This operation is not allowed in the context of a non-debug run.
-
-
+ Эта операция запрещена в контексте неотладочного запуска.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Ни один из указанных источников "{0}" не является допустимым. Исправьте эти ошибки и предупреждения и повторите попытку. ,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Соответствующих фильтру тестов нет, так как фильтр содержит одно недопустимое свойство или несколько ({0}). Укажите выражение фильтра, содержащее допустимые свойства ({1}).Could not find {0}. Make sure that the dotnet is installed on the machine.Не удалось найти {0}. Убедитесь, что dotnet установлен на компьютере.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Процесс testhost завершился с ошибкой: {0}. Дополнительные сведения см. в журналах диагностики.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.Включена отладка datacollector. Для продолжения подключите отладчик к процессу datacollector.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.В {0} нет доступных тестов. Убедитесь, что средства обнаружения и выполнения тестов зарегистрированы, а также проверьте правильность параметров платформы и версии платформы, после чего повторите попытку.
-
-
+ Logging TestHost Diagnostics in file: {0}Ведение журналов диагностики TestHost в файле: {0}
-
-
+ Failed to launch testhost with error: {0}Не удалось запустить хост для тестов с ошибкой: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.Параметр ExecutionThreadApartmentState не поддерживается для платформы: {0}.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Вы используете более старую версию Microsoft.NET.Test.Sdk. Перейдите на версию 15.3.0 или более позднюю.
-
-
+ Could not find extensions: {0}Не удалось найти расширения: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Изменяется поиск адаптеров. Дополнительные сведения: https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap.
-
-
+ No test matches the given testcase filter `{0}` in {1}Нет тестов, соответствующих указанному фильтру тестовых случаев "{0}" в {1}
-
-
+ Discovery of tests cancelled.Обнаружение тестов отменено.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Не удается подключить отладчик к узлу тестирования по умолчанию с идентификатором процесса {0}.
-
-
+ {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.{0} Отказано в доступе при попытке создания папки "TestResults" в указанном расположении. Это исключение возникло, так как вы запускаете файл vstest.console.exe из папки, для которой требуется доступ на запись. Чтобы устранить эту проблему, запустите vstest.console.exe из папки, для которой у вас есть разрешения на запись.
-
-
+ Could not find an available proxy to deque.Не удалось найти доступный прокси-сервер для двусторонней очереди.
-
-
+ Proxy with id {0} is not managed by the current session manager.Прокси-сервер с идентификатором {0} не управляется текущим диспетчером сеансов.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.Прокси-сервер с идентификатором {0} уже доступен и не может быть повторно поставлен в очередь.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ Bulucu örneği oluşturulurken özel durum oluştu: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ Belirtilen '{0}' yinelenen kaynağı yoksayılıyor.An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ '{0}' test bulucusu testleri yüklerken bir özel durum oluştu. Özel durum: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ '{0}' yürütücüsü çağrılırken bir özel durum oluştu: {1}Could not find file {0}.
-
-
+ {0} dosyası bulunamadı.
@@ -44,20 +39,17 @@
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.
-
-
+ Bulucu DefaultExecutorUri özniteliğine sahip olmadığından {0} test bulucusuna karşılık gelen test yürütücüsü yoksayılıyor. Test bağdaştırıcısı eklentisini yeniden yüklemeniz gerekebilir.Failed to initialize client proxy: could not connect to test process.
-
-
+ İstemci ara sunucusu başlatılamadı: Test işlemine bağlanılamadı.This operation is not allowed in the context of a non-debug run.
-
-
+ Bu işlem hata ayıklama dışındaki bir çalıştırmanın bağlamında yapılamaz.
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ Belirtilen '{0}' kaynaklarının hiçbiri geçerli değil. Yukarıdaki hataları/uyarıları düzeltin ve yeniden deneyin.,
-
-
+ , No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ Geçerli olmayan bir veya daha fazla özellik içerdiğinden filtre ile eşleşen test yok ({0}). Geçerli değerleri ({1}) içeren bir filtre ifadesi belirtin.Could not find {0}. Make sure that the dotnet is installed on the machine.{0} bulunamadı. Makinede dotnet’in yüklü olduğundan emin olun.
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Testhost işleminden şu hatayla çıkıldı: {0}. Daha fazla bilgi için lütfen tanılama günlüklerine bakın.
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.DataCollector hata ayıklaması etkin. Devam etmek için lütfen hata ayıklayıcısını datacollector işlemine ekleyin.
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.{0} içinde hiç test yok. Test bulucuları ile yürütücülerinin kayıtlı olduğundan ve platform ile çerçeve sürümü ayarlarının uygun olduğundan emin olun ve yeniden deneyin.
-
-
+ Logging TestHost Diagnostics in file: {0}TestHost Tanılamaları şu dosyadaki günlüğe kaydediliyor: {0}
-
-
+ Failed to launch testhost with error: {0}Testhost başlatılamadı. Şu hata alındı: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.ExecutionThreadApartmentState seçeneği {0} çerçevesi için desteklenmiyor.
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.Eski bir Microsoft.NET.Test.Sdk sürümü kullanıyorsunuz. Lütfen 15.3.0 veya daha yeni bir sürüme geçin.
-
-
+ Could not find extensions: {0}Dosya uzantıları bulunamadı: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.Bağdaştırıcı arama değiştiriliyor. Ayrıntılar için lütfen https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap sayfasını takip edin.
-
-
+ No test matches the given testcase filter `{0}` in {1}{1} içinde sunulan test çalışması filtresi `{0}` ile eşleşen test yok
-
-
+ Discovery of tests cancelled.Test bulma iptal edildi.
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.Hata ayıklayıcı, {0} işlem kimliğine sahip varsayılan test ana bilgisayarına eklenemiyor.
-
-
+ {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.{0} Belirtilen konumda "TestResults" klasörü oluşturulmaya çalışılırken erişim engellendi. Yazma erişimi gerektiren bir klasörden vstest.console.exe çalıştırdığınız için bu özel durumu aldınız. Sorunu çözmek için lütfen yazma ayrıcalıklarına sahip olduğunuz bir klasörden vstest.console.exe dosyasını çalıştırın.
-
-
+ Could not find an available proxy to deque.İki uçtan erişimli kuyruğa yönelik kullanılabilir ara sunucu bulunamadı.
-
-
+ Proxy with id {0} is not managed by the current session manager.{0} kimliğine sahip ara sunucu, geçerli oturum yöneticisi tarafından yönetilmiyor.
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.{0} kimliğine sahip ara sunucu zaten var ve yeniden kuyruğa alınamaz.
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ 实例化发现器时发生异常: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ 忽略指定的重复源“{0}”。An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ 测试发现器“{0}”加载测试时发生异常。异常: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ 调用的执行器“{0}”时发生异常: {1}Could not find file {0}.
-
-
+ 找不到文件 {0}。
@@ -44,20 +39,17 @@
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.
-
-
+ 忽略与测试发现器 {0} 对应的测试执行器,因为该发现器不具有 DefaultExecutorUri 特性。可能需要重新安装测试适配器外接程序。Failed to initialize client proxy: could not connect to test process.
-
-
+ 未能初始化客户端代理: 无法连接到测试过程。This operation is not allowed in the context of a non-debug run.
-
-
+ 非调试运行的上下文中不允许此操作。
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ 无有效的指定源“{0}”。请修复以上错误/警告,然后重试。,
-
-
+ ,No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ 没有与筛选器匹配的测试,因为该筛选器包含一个或多个无效属性 ({0})。请指定包含有效属性 ({1}) 的筛选器表达式。Could not find {0}. Make sure that the dotnet is installed on the machine.找不到 {0}。请确保计算机上安装了 dotnet。
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Testhost 进程已退出,但出现错误: {0}。请查看诊断日志了解详细信息。
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.启用 DataCollector 调试。请将调试器附加到 datacollector 进程以继续。
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.{0} 中没有可用测试。请确保已注册测试发现器和执行器且平台和框架版本设置合理,然后重试。
-
-
+ Logging TestHost Diagnostics in file: {0}在文件 {0} 中记录 TestHost 诊断
-
-
+ Failed to launch testhost with error: {0}未能启动测试主机,错误为 {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.框架 {0} 不支持 ExecutionThreadApartmentState 选项。
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.你使用的是旧版 Microsoft.NET.Test.Sdk。请迁移到 15.3.0 及更高版本。
-
-
+ Could not find extensions: {0}找不到扩展名: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.适配器查找发生了变化,请转到 https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap,了解详细信息。
-
-
+ No test matches the given testcase filter `{0}` in {1}没有测试匹配 {1} 中的给定用例测试筛选器“{0}”
-
-
+ Discovery of tests cancelled.已取消测试发现。
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.无法将调试程序附加到进程 ID 为“{0}”的默认测试主机。
-
-
+ {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.{0} 尝试在所述位置创建 "TestResults" 文件夹时,访问被拒。你收到此异常是因为你正在从需要具有写入权限的文件夹运行 vstest.console.exe。若要解决此问题,请从你具有写入权限的文件夹运行 vstest.console.exe。
-
-
+ Could not find an available proxy to deque.找不到用于取消排队的可用代理。
-
-
+ Proxy with id {0} is not managed by the current session manager.ID 为 {0} 的代理不受当前会话管理器管理。
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.ID 为 {0} 的代理已可用,无法重新排队。
-
-
+ Exception occurred while instantiating discoverer : {0}
-
-
+ 將探索程式具現化時發生例外狀況: {0}
@@ -15,26 +14,22 @@
Ignoring the specified duplicate source '{0}'.
-
-
+ 忽略指定的重複來源 '{0}'。An exception occurred while test discoverer '{0}' was loading tests. Exception: {1}
-
-
+ 測試探索程式 '{0}' 載入測試時發生例外狀況。例外狀況: {1}An exception occurred while invoking executor '{0}': {1}
-
-
+ 叫用執行程式 '{0}' 時發生例外狀況: {1}Could not find file {0}.
-
-
+ 找不到檔案 {0}。
@@ -44,20 +39,17 @@
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.
-
-
+ 忽略對應到測試探索程式 {0} 的測試執行程式,因為探索程式沒有 DefaultExecutorUri 屬性。您可能必須重新安裝測試配接器增益集。Failed to initialize client proxy: could not connect to test process.
-
-
+ 無法將用戶端 Proxy 初始化: 無法連接到測試處理序This operation is not allowed in the context of a non-debug run.
-
-
+ 這項作業不能用於非偵錯回合的內容中。
@@ -67,123 +59,103 @@
None of the specified source(s) '{0}' is valid. Fix the above errors/warnings and then try again.
-
-
+ 指定的來源 '{0}' 皆無效。請修正上述錯誤/警告,並再試一次。,
-
-
+ ,No tests matched the filter because it contains one or more properties that are not valid ({0}). Specify filter expression containing valid properties ({1}).
-
-
+ 因為篩選包含一或多個無效的屬性 ({0}),所以沒有符合篩選的測試。請指定包含有效屬性 ({1}) 的篩選運算式。Could not find {0}. Make sure that the dotnet is installed on the machine.找不到 {0}。請確定電腦上安裝了 .NET。
-
-
+ Testhost process exited with error: {0}. Please check the diagnostic logs for more information.Testhost 處理序已結束。錯誤: {0}。如需詳細資訊,請查看診斷記錄。
-
-
+ DataCollector debugging is enabled. Please attach debugger to datacollector process to continue.DataCollector 已啟用。若要繼續,請將偵錯工具連結到 datacollector 處理序。
-
-
+ No test is available in {0}. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.{0} 中未提供任何測試。請確定已登錄了測試探索程式與執行程式,且平台與 Framework 版本設定皆正確,然後再試一次。
-
-
+ Logging TestHost Diagnostics in file: {0}在檔案 {0} 中記錄 TestHost 診斷
-
-
+ Failed to launch testhost with error: {0}無法啟動測試主機。錯誤: {0}
-
-
+ ExecutionThreadApartmentState option not supported for framework: {0}.架構 {0} 不支援 ExecutionThreadApartmentState 選項。
-
-
+ You are using an older version of Microsoft.NET.Test.Sdk. Kindly move to a version equal or greater than 15.3.0.您正使用較舊版的 Microsoft.NET.Test.Sdk。請移到等於或大於 15.3.0 的版本。
-
-
+ Could not find extensions: {0}找不到延伸模組: {0}
-
-
+ Adapter lookup is being changed, please follow https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap for more details.目前正在變更配接器查閱,請遵循 https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0022-User-Specified-TestAdapter-Lookup.md#roadmap,以取得詳細資料。
-
-
+ No test matches the given testcase filter `{0}` in {1}沒有任何測試符合 {1} 中的指定 testcase 篩選 `{0}`
-
-
+ Discovery of tests cancelled.已取消測試的探索。
-
-
+ Cannot attach the debugger to the default test host with process ID: {0}.無法將偵錯工具連結到處理序識別碼為 {0} 的預設測試主機。
-
-
+ {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.{0} 當嘗試在提及的位置上建立 "TestResults" 資料夾時存取被拒。因為您正從需要寫入存取權的資料夾執行 vstest.console.exe,所以收到此例外狀況。若要解決此問題: 請從您有權寫入的資料夾執行 vstest.console.exe。
-
-
+ Could not find an available proxy to deque.找不到任何要排除於佇列外的 Proxy。
-
-
+ Proxy with id {0} is not managed by the current session manager.識別碼為 {0} 的 Proxy 並非由目前的工作階段管理員所管理。
-
-
+ Proxy with id {0} is already available and cannot be re-enqueued.識別碼為 {0} 的 Proxy 已可供使用,但無法重新加入佇列。
-
-
+ Run settings XML does not contain "RunSettings" node.
-
-
+ Kód XML parametrů spouštění neobsahuje uzel RunSettings.Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Neplatné nastavení {0}. Pro {2} se zadala neplatná hodnota {1}.Could not find 'RunSettings' node.
-
-
+ Nepovedlo se najít uzel RunSettings.Could not find 'RunSettings' node.
-
-
+ Nepovedlo se najít uzel RunSettings.An error occurred while loading the settings. Error: {0}.
-
-
+ Při načítání nastavení se stala chyba. Chyba: {0}Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Nastavení cílové platformy {0} není kompatibilní s architekturou systému {1}.Unexpected settings file specified.
-
-
+ Zadal se neočekávaný soubor nastavení.Run settings XML does not contain "RunSettings" node.
-
-
+ Das Laufzeiteinstellungen-XML enthält nicht den Knoten "RunSettings".Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Ungültige Einstellung "{0}". Für "{2}" wurde ein ungültiger Wert "{1}" angegeben.Could not find 'RunSettings' node.
-
-
+ Der Knoten "RunSettings" wurde nicht gefunden.Could not find 'RunSettings' node.
-
-
+ Der Knoten "RunSettings" wurde nicht gefunden.An error occurred while loading the settings. Error: {0}.
-
-
+ Fehler beim Laden der Einstellungen. Fehler: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Inkompatible Zielplattformeinstellungen "{0}" mit der Systemarchitektur "{1}".Unexpected settings file specified.
-
-
+ Es wurde eine unerwartete Einstellungsdatei angegeben.Run settings XML does not contain "RunSettings" node.
-
-
+ El archivo XML de parámetros de ejecución no contiene el nodo "RunSettings".Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Parámetro '{0}' no válido. Se ha especificado un valor no válido ({1}) para '{2}'.Could not find 'RunSettings' node.
-
-
+ No se encuentra el nodo 'RunSettings'.Could not find 'RunSettings' node.
-
-
+ No se encuentra el nodo 'RunSettings'.An error occurred while loading the settings. Error: {0}.
-
-
+ Error al cargar la configuración. Error: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ La configuración de plataforma de destino '{0}' es incompatible con la arquitectura del sistema '{1}'.Unexpected settings file specified.
-
-
+ Se ha especificado un archivo de configuración no esperado.Run settings XML does not contain "RunSettings" node.
-
-
+ Le fichier XML des paramètres d'exécution ne contient pas le nœud "RunSettings".Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Paramètre non valide '{0}'. Valeur non valide '{1}' spécifiée pour '{2}'.Could not find 'RunSettings' node.
-
-
+ Nœud 'RunSettings' introuvable.Could not find 'RunSettings' node.
-
-
+ Nœud 'RunSettings' introuvable.An error occurred while loading the settings. Error: {0}.
-
-
+ Une erreur s'est produite durant le chargement des paramètres. Erreur : {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Paramètres de plateforme cible '{0}' incompatibles avec l'architecture système '{1}'.Unexpected settings file specified.
-
-
+ Un fichier de paramètres inattendu a été spécifié.Run settings XML does not contain "RunSettings" node.
-
-
+ L'XML delle impostazioni esecuzione test non contiene il nodo "RunSettings".Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ L'impostazione '{0}' non è valida. Il valore '{1}' specificato per '{2}' non è valido.Could not find 'RunSettings' node.
-
-
+ Il nodo 'RunSettings' non è stato trovato.Could not find 'RunSettings' node.
-
-
+ Il nodo 'RunSettings' non è stato trovato.An error occurred while loading the settings. Error: {0}.
-
-
+ Si è verificato un errore durante il caricamento delle impostazioni. Errore: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Le impostazioni della piattaforma di destinazione '{0}' non sono compatibili con l'architettura di sistema '{1}'.Unexpected settings file specified.
-
-
+ È stato specificato un file di impostazioni imprevisto.Run settings XML does not contain "RunSettings" node.
-
-
+ 実行設定 XML に "RunSettings" ノードがありません。Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ 設定 '{0}' は無効です。無効な値 '{1}' が '{2}' に指定されました。Could not find 'RunSettings' node.
-
-
+ 'RunSettings' ノードが見つかりませんでした。Could not find 'RunSettings' node.
-
-
+ 'RunSettings' ノードが見つかりませんでした。An error occurred while loading the settings. Error: {0}.
-
-
+ 設定の読み込み中にエラーが発生しました。エラー: {0}。Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ ターゲット プラットフォームの設定 '{0}' はシステム アーキテクチャ '{1}' と互換性がありません。Unexpected settings file specified.
-
-
+ 予期しない設定ファイルが指定されました。Run settings XML does not contain "RunSettings" node.
-
-
+ 실행 설정 XML에 "RunSettings" 노드가 포함되어 있지 않습니다.Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ '{0}' 설정이 잘못되었습니다. '{2}'에 대해 잘못된 값 '{1}'을(를) 지정했습니다.Could not find 'RunSettings' node.
-
-
+ 'RunSettings' 노드를 찾을 수 없습니다.Could not find 'RunSettings' node.
-
-
+ 'RunSettings' 노드를 찾을 수 없습니다.An error occurred while loading the settings. Error: {0}.
-
-
+ 설정을 로드하는 동안 오류가 발생했습니다. 오류: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ 대상 플랫폼 설정 '{0}'이(가) 시스템 아키텍처 '{1}'과(와) 호환되지 않습니다.Unexpected settings file specified.
-
-
+ 예기치 않은 설정 파일을 지정했습니다.Run settings XML does not contain "RunSettings" node.
-
-
+ Plik XML parametrów uruchomieniowych nie zawiera węzła „RunSettings”.Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Nieprawidłowe ustawienie „{0}”. Nieprawidłowa wartość „{1}” określona dla elementu „{2}”.Could not find 'RunSettings' node.
-
-
+ Nie można odnaleźć węzła „RunSettings”.Could not find 'RunSettings' node.
-
-
+ Nie można odnaleźć węzła „RunSettings”.An error occurred while loading the settings. Error: {0}.
-
-
+ Wystąpił błąd podczas ładowania ustawień. Błąd: {0}Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Niezgodne ustawienia platformy docelowej „{0}” z architekturą systemu „{1}”.Unexpected settings file specified.
-
-
+ Określono nieoczekiwany plik ustawień.Run settings XML does not contain "RunSettings" node.
-
-
+ O XML de configurações de execução não contém o nó de "RunSettings".Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Configuração inválida '{0}'. Valor inválido '{1}' especificado para '{2}'.Could not find 'RunSettings' node.
-
-
+ Não foi possível localizar o nó 'RunSettings'.Could not find 'RunSettings' node.
-
-
+ Não foi possível localizar o nó 'RunSettings'.An error occurred while loading the settings. Error: {0}.
-
-
+ Ocorreu um erro ao carregar as configurações. Erro: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Configurações da plataforma de destino '{0}' incompatíveis com a arquitetura do sistema '{1}'.Unexpected settings file specified.
-
-
+ Arquivo de configurações inesperado especificado.Run settings XML does not contain "RunSettings" node.
-
-
+ XML-файл параметров запуска не содержит узел RunSettings.Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ Недопустимый параметр "{0}". Недопустимое значение "{1}", указанное для "{2}".Could not find 'RunSettings' node.
-
-
+ Не удалось найти узел RunSettings.Could not find 'RunSettings' node.
-
-
+ Не удалось найти узел RunSettings.An error occurred while loading the settings. Error: {0}.
-
-
+ Произошла ошибка при загрузке параметров. Ошибка: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ Параметры целевой платформы "{0}" несовместимы с архитектурой системы "{1}".Unexpected settings file specified.
-
-
+ Указанный неожиданный файл параметров.Run settings XML does not contain "RunSettings" node.
-
-
+ Çalıştırma ayarları XML dosyası "RunSettings" düğümünü içermiyor.Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ '{0}' ayarı geçersiz. '{2}' için geçersiz '{1}' değeri belirtildi.Could not find 'RunSettings' node.
-
-
+ 'RunSettings' düğümü bulunamadı.Could not find 'RunSettings' node.
-
-
+ 'RunSettings' düğümü bulunamadı.An error occurred while loading the settings. Error: {0}.
-
-
+ Ayarlar yüklenirken bir hata oluştu. Hata: {0}.Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ '{0}' hedef platform ayarları, '{1}' sistem mimarisiyle uyumlu değil.Unexpected settings file specified.
-
-
+ Beklenmeyen ayarlar dosyası belirtildi.Run settings XML does not contain "RunSettings" node.
-
-
+ 运行设置 XML 不包含 "RunSettings" 节点。Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ 设置“{0}”无效。为“{2}”指定的值“{1}”无效。Could not find 'RunSettings' node.
-
-
+ 找不到 "RunSettings" 节点。Could not find 'RunSettings' node.
-
-
+ 找不到 "RunSettings" 节点。An error occurred while loading the settings. Error: {0}.
-
-
+ 加载设置时出错。错误: {0}。Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ 目标平台设置“{0}”与系统体系结构“{1}”不兼容。Unexpected settings file specified.
-
-
+ 指定了意外的设置文件。Run settings XML does not contain "RunSettings" node.
-
-
+ 回合設定 XML 不包含 " RunSettings" 節點。Invalid setting '{0}'. Invalid value '{1}' specified for '{2}'.
-
-
+ 設定 '{0}' 無效。為 '{2}' 指定的值 '{1}' 無效。Could not find 'RunSettings' node.
-
-
+ 找不到 'RunSettings' 節點。Could not find 'RunSettings' node.
-
-
+ 找不到 'RunSettings' 節點。An error occurred while loading the settings. Error: {0}.
-
-
+ 載入設定時發生錯誤。錯誤: {0}。Incompatible Target platform settings '{0}' with system architecture '{1}'.
-
-
+ 目標平台設定 '{0}' 與系統架構 '{1}' 不相容。Unexpected settings file specified.
-
-
+ 指定了非預期的設定檔案。The active Tests Run was aborted.
-
-
+ Aktivní testovací běh se přerušil.The active Tests Discovery was aborted.
-
-
+ Aktivní zjišťování testů se přerušilo.Failed to receive message from vstest.console process
-
-
+ Nepovedlo se přijmout zprávu z procesu vstest.console.vstest.console process exited abnormally
-
-
+ Proces vstest.console se ukončil neobvyklým způsobem.File {0} does not existsSoubor {0} neexistuje.
-
-
+ The active Test Run Attachments Processing was aborted.Aktivní zpracovávání příloh testovacího běhu se přerušilo.
-
-
+ The Start Test Session operation was aborted.Operace zahájení testovací relace se přerušila.
-
-
+ The Stop Test Session operation was aborted.Operace zastavení testovací relace se přerušila.
-
-
+ The active Tests Run was aborted.
-
-
+ Der aktive Testlauf wurde abgebrochen.The active Tests Discovery was aborted.
-
-
+ Die aktive Testermittlung wurde abgebrochen.Failed to receive message from vstest.console process
-
-
+ Fehler beim Empfangen der Nachricht aus dem vstest.console-Prozess.vstest.console process exited abnormally
-
-
+ Der vstest.console-Prozess wurde anormal beendet.File {0} does not existsDie Datei "{0}" ist nicht vorhanden.
-
-
+ The active Test Run Attachments Processing was aborted.Die Verarbeitung aktiver Testlaufanlagen wurde abgebrochen.
-
-
+ The Start Test Session operation was aborted.Der Vorgang zum Starten der Testsitzung wurde abgebrochen.
-
-
+ The Stop Test Session operation was aborted.Der Vorgang zum Beenden der Testsitzung wurde abgebrochen.
-
-
+ The active Tests Run was aborted.
-
-
+ Se ha anulado la serie de pruebas activa.The active Tests Discovery was aborted.
-
-
+ Se ha anulado la detección de pruebas activa.Failed to receive message from vstest.console process
-
-
+ No se pudo recibir el mensaje del proceso vstest.consolevstest.console process exited abnormally
-
-
+ El proceso vstest.console finalizó de forma anómalaFile {0} does not existsEl archivo {0} no existe
-
-
+ The active Test Run Attachments Processing was aborted.Se ha anulado el procesamiento de los datos adjuntos de la serie de pruebas activa.
-
-
+ The Start Test Session operation was aborted.La operación de inicio de la sesión de prueba se ha anulado.
-
-
+ The Stop Test Session operation was aborted.La operación de detención de la sesión de prueba se ha anulado.
-
-
+ The active Tests Run was aborted.
-
-
+ La série de tests active a été abandonnée.The active Tests Discovery was aborted.
-
-
+ La découverte de tests active a été abandonnée.Failed to receive message from vstest.console process
-
-
+ Échec de réception du message du processus vstest.consolevstest.console process exited abnormally
-
-
+ Sortie anormale du processus vstest.consoleFile {0} does not existsLe fichier {0} n'existe pas
-
-
+ The active Test Run Attachments Processing was aborted.Le traitement des pièces jointes de série de tests actif a été abandonné.
-
-
+ The Start Test Session operation was aborted.L'opération de démarrage de la session de test a été abandonnée.
-
-
+ The Stop Test Session operation was aborted.L'opération d'arrêt de la session de test a été abandonnée.
-
-
+ The active Tests Run was aborted.
-
-
+ L'esecuzione dei test attiva è stata interrotta.The active Tests Discovery was aborted.
-
-
+ L'individuazione dei test attiva è stata interrotta.Failed to receive message from vstest.console process
-
-
+ Non è stato possibile ricevere il messaggio dal processo vstest.consolevstest.console process exited abnormally
-
-
+ Il processo vstest.console è stato chiuso in modo anomaloFile {0} does not existsIl file {0} non esiste
-
-
+ The active Test Run Attachments Processing was aborted.L'elaborazione degli allegati dell'esecuzione dei test attiva è stata interrotta.
-
-
+ The Start Test Session operation was aborted.L'operazione di avvio della sessione di test è stata interrotta.
-
-
+ The Stop Test Session operation was aborted.L'operazione di arresto della sessione di test è stata interrotta.
-
-
+ The active Tests Run was aborted.
-
-
+ アクティブなテストの実行が中止されました。The active Tests Discovery was aborted.
-
-
+ アクティブなテスト探索が中止されました。Failed to receive message from vstest.console process
-
-
+ vstest.console プロセスからメッセージを受信できませんでしたvstest.console process exited abnormally
-
-
+ vstest.console プロセスが異常終了しましたFile {0} does not existsファイル {0} が存在しません
-
-
+ The active Test Run Attachments Processing was aborted.アクティブなテストの実行の添付ファイルの処理が中止されました。
-
-
+ The Start Test Session operation was aborted.テスト セッションの開始操作が中止されました。
-
-
+ The Stop Test Session operation was aborted.テスト セッションの停止操作が中止されました。
-
-
+ The active Tests Run was aborted.
-
-
+ 활성 테스트 실행이 중단되었습니다.The active Tests Discovery was aborted.
-
-
+ 활성 테스트 검색이 중단되었습니다.Failed to receive message from vstest.console process
-
-
+ vstest.console 프로세스에서 메시지를 받지 못했습니다.vstest.console process exited abnormally
-
-
+ vstest.console 프로세스가 비정상적으로 종료되었습니다.File {0} does not exists{0} 파일이 없습니다.
-
-
+ The active Test Run Attachments Processing was aborted.활성 테스트 실행 첨부 파일 처리가 중단되었습니다.
-
-
+ The Start Test Session operation was aborted.테스트 세션 시작 작업이 중단되었습니다.
-
-
+ The Stop Test Session operation was aborted.테스트 세션 중지 작업이 중단되었습니다.
-
-
+ The active Tests Run was aborted.
-
-
+ Aktywny przebieg testów został przerwany.The active Tests Discovery was aborted.
-
-
+ Aktywny proces wykrywania testów został przerwany.Failed to receive message from vstest.console process
-
-
+ Nie można odebrać komunikatu z procesu vstest.consolevstest.console process exited abnormally
-
-
+ Proces vstest.console zakończył się nieprawidłowoFile {0} does not existsPlik {0} nie istnieje
-
-
+ The active Test Run Attachments Processing was aborted.Aktywne przetwarzanie załączników przebiegu testu zostało przerwane.
-
-
+ The Start Test Session operation was aborted.Operacja uruchamiania sesji testowania została przerwana.
-
-
+ The Stop Test Session operation was aborted.Operacja zatrzymywania sesji testowania została przerwana.
-
-
+ The active Tests Run was aborted.
-
-
+ A Execução de Testes ativa foi anulada.The active Tests Discovery was aborted.
-
-
+ A Descoberta de Testes ativa foi anulada.Failed to receive message from vstest.console process
-
-
+ Falha ao receber mensagem do processo vstest.consolevstest.console process exited abnormally
-
-
+ processo de vstest.console encerrado de forma anormalFile {0} does not existsO arquivo {0} não existe
-
-
+ The active Test Run Attachments Processing was aborted.O Processamento de Anexos de Execução de Teste ativo foi anulado.
-
-
+ The Start Test Session operation was aborted.A operação Iniciar a Sessão de Teste foi anulada.
-
-
+ The Stop Test Session operation was aborted.A operação Parar a Sessão de Teste foi anulada.
-
-
+ The active Tests Run was aborted.
-
-
+ Активный тестовый запуск прерван.The active Tests Discovery was aborted.
-
-
+ Активное обнаружение тестов прервано.Failed to receive message from vstest.console process
-
-
+ Не удалось получить сообщение из процесса vstest.console.vstest.console process exited abnormally
-
-
+ Аварийное завершение процесса vstest.consoleFile {0} does not existsФайл {0} не существует.
-
-
+ The active Test Run Attachments Processing was aborted.Обработка вложений активного тестового запуска прервана.
-
-
+ The Start Test Session operation was aborted.Операция запуска сеанса тестирования прервана.
-
-
+ The Stop Test Session operation was aborted.Операция остановки сеанса тестирования прервана.
-
-
+ The active Tests Run was aborted.
-
-
+ Etkin Test Çalıştırması iptal edildi.The active Tests Discovery was aborted.
-
-
+ Etkin Test Bulma iptal edildi.Failed to receive message from vstest.console process
-
-
+ vstest.console işleminden ileti alınamadıvstest.console process exited abnormally
-
-
+ vstest.console işlemi anormal şekilde çıkış yaptıFile {0} does not exists{0} dosyası yok
-
-
+ The active Test Run Attachments Processing was aborted.Etkin Test Çalıştırması Ekleri İşlemi durduruldu.
-
-
+ The Start Test Session operation was aborted.Test Oturumunu Başlatma işlemi iptal edildi.
-
-
+ The Stop Test Session operation was aborted.Test Oturumunu Durdurma işlemi iptal edildi.
-
-
+ The active Tests Run was aborted.
-
-
+ 活动的测试运行已中止。The active Tests Discovery was aborted.
-
-
+ 活动的测试发现已中止。Failed to receive message from vstest.console process
-
-
+ 未能从 vstest.console 进程接收消息vstest.console process exited abnormally
-
-
+ vstest.console 进程异常退出File {0} does not exists文件 {0} 不存在
-
-
+ The active Test Run Attachments Processing was aborted.已中止正在进行的测试运行附件处理操作。
-
-
+ The Start Test Session operation was aborted.已中止启动测试会话操作。
-
-
+ The Stop Test Session operation was aborted.已中止停止测试会话操作。
-
-
+ The active Tests Run was aborted.
-
-
+ 已中止使用中的測試回合。The active Tests Discovery was aborted.
-
-
+ 已中止使用中的測試探索。Failed to receive message from vstest.console process
-
-
+ 無法接收來自 vstest.console 處理序的訊息vstest.console process exited abnormally
-
-
+ vstest.console 處理序異常結束File {0} does not exists檔案 {0} 不存在
-
-
+ The active Test Run Attachments Processing was aborted.執行中的測試回合附件處理已中止。
-
-
+ The Start Test Session operation was aborted.開始測試工作階段作業已中止。
-
-
+ The Stop Test Session operation was aborted.停止測試工作階段作業已中止。
-
-
+