From bd2a39761f48bb6d719bf042a00ee7948353edc1 Mon Sep 17 00:00:00 2001 From: Medeni Baykal <433724+Haplois@users.noreply.github.com> Date: Fri, 30 Jul 2021 13:58:08 +0200 Subject: [PATCH 1/2] Updated Visual Studio Externals --- scripts/build.ps1 | 3 ++- scripts/build/TestPlatform.Dependencies.props | 5 +++-- src/package/external/external.csproj | 2 +- test/TestAssets/CILProject/OrphanMethod.il | 1 + 4 files changed, 7 insertions(+), 4 deletions(-) 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.1 4.7.63 - 16.11.31527.49 - 16.11.31523.174 + 16.11.31528.385 + 16.11.31528.385 + 16.11.31527.49 16.10.0-beta.21270.2 16.11.230815 diff --git a/src/package/external/external.csproj b/src/package/external/external.csproj index a25f7cb5a4..e070359f33 100644 --- a/src/package/external/external.csproj +++ b/src/package/external/external.csproj @@ -118,7 +118,7 @@ All - $(TestPlatformExternalsVersion) + $(VsWebSiteInteropVersion) All diff --git a/test/TestAssets/CILProject/OrphanMethod.il b/test/TestAssets/CILProject/OrphanMethod.il index d13d1457d1..e13ddf6858 100644 --- a/test/TestAssets/CILProject/OrphanMethod.il +++ b/test/TestAssets/CILProject/OrphanMethod.il @@ -1,5 +1,6 @@ .assembly OrphanMethod {} .assembly extern mscorlib {} +.assembly extern System.Core {} .method static public int32 Add(int32 x, int32 y) cil managed { From e99aad6a5d1d56ab723e4b8202e8da90cd5588f3 Mon Sep 17 00:00:00 2001 From: Medeni Baykal <433724+Haplois@users.noreply.github.com> Date: Fri, 30 Jul 2021 13:58:31 +0200 Subject: [PATCH 2/2] Localization --- .../Resources/xlf/Resources.cs.xlf | 15 +- .../Resources/xlf/Resources.de.xlf | 15 +- .../Resources/xlf/Resources.es.xlf | 15 +- .../Resources/xlf/Resources.fr.xlf | 15 +- .../Resources/xlf/Resources.it.xlf | 15 +- .../Resources/xlf/Resources.ja.xlf | 15 +- .../Resources/xlf/Resources.ko.xlf | 15 +- .../Resources/xlf/Resources.pl.xlf | 15 +- .../Resources/xlf/Resources.pt-BR.xlf | 15 +- .../Resources/xlf/Resources.ru.xlf | 15 +- .../Resources/xlf/Resources.tr.xlf | 15 +- .../Resources/xlf/Resources.zh-Hans.xlf | 15 +- .../Resources/xlf/Resources.zh-Hant.xlf | 15 +- .../Resources/xlf/Resources.cs.xlf | 15 +- .../Resources/xlf/Resources.de.xlf | 15 +- .../Resources/xlf/Resources.es.xlf | 15 +- .../Resources/xlf/Resources.fr.xlf | 15 +- .../Resources/xlf/Resources.it.xlf | 15 +- .../Resources/xlf/Resources.ja.xlf | 15 +- .../Resources/xlf/Resources.ko.xlf | 15 +- .../Resources/xlf/Resources.pl.xlf | 15 +- .../Resources/xlf/Resources.pt-BR.xlf | 15 +- .../Resources/xlf/Resources.ru.xlf | 15 +- .../Resources/xlf/Resources.tr.xlf | 15 +- .../Resources/xlf/Resources.zh-Hans.xlf | 15 +- .../Resources/xlf/Resources.zh-Hant.xlf | 15 +- .../Resources/xlf/Resources.cs.xlf | 12 +- .../Resources/xlf/Resources.de.xlf | 12 +- .../Resources/xlf/Resources.es.xlf | 12 +- .../Resources/xlf/Resources.fr.xlf | 12 +- .../Resources/xlf/Resources.it.xlf | 12 +- .../Resources/xlf/Resources.ja.xlf | 12 +- .../Resources/xlf/Resources.ko.xlf | 12 +- .../Resources/xlf/Resources.pl.xlf | 12 +- .../Resources/xlf/Resources.pt-BR.xlf | 12 +- .../Resources/xlf/Resources.ru.xlf | 12 +- .../Resources/xlf/Resources.tr.xlf | 12 +- .../Resources/xlf/Resources.zh-Hans.xlf | 12 +- .../Resources/xlf/Resources.zh-Hant.xlf | 12 +- .../Resources/xlf/Resources.cs.xlf | 114 ++-- .../Resources/xlf/Resources.de.xlf | 114 ++-- .../Resources/xlf/Resources.es.xlf | 114 ++-- .../Resources/xlf/Resources.fr.xlf | 114 ++-- .../Resources/xlf/Resources.it.xlf | 114 ++-- .../Resources/xlf/Resources.ja.xlf | 114 ++-- .../Resources/xlf/Resources.ko.xlf | 114 ++-- .../Resources/xlf/Resources.pl.xlf | 114 ++-- .../Resources/xlf/Resources.pt-BR.xlf | 114 ++-- .../Resources/xlf/Resources.ru.xlf | 114 ++-- .../Resources/xlf/Resources.tr.xlf | 114 ++-- .../Resources/xlf/Resources.zh-Hans.xlf | 114 ++-- .../Resources/xlf/Resources.zh-Hant.xlf | 114 ++-- .../Resources/xlf/Resources.cs.xlf | 30 +- .../Resources/xlf/Resources.de.xlf | 30 +- .../Resources/xlf/Resources.es.xlf | 30 +- .../Resources/xlf/Resources.fr.xlf | 30 +- .../Resources/xlf/Resources.it.xlf | 30 +- .../Resources/xlf/Resources.ja.xlf | 30 +- .../Resources/xlf/Resources.ko.xlf | 30 +- .../Resources/xlf/Resources.pl.xlf | 30 +- .../Resources/xlf/Resources.pt-BR.xlf | 30 +- .../Resources/xlf/Resources.ru.xlf | 30 +- .../Resources/xlf/Resources.tr.xlf | 30 +- .../Resources/xlf/Resources.zh-Hans.xlf | 30 +- .../Resources/xlf/Resources.zh-Hant.xlf | 30 +- .../Resources/xlf/Resources.cs.xlf | 48 +- .../Resources/xlf/Resources.de.xlf | 48 +- .../Resources/xlf/Resources.es.xlf | 48 +- .../Resources/xlf/Resources.fr.xlf | 48 +- .../Resources/xlf/Resources.it.xlf | 48 +- .../Resources/xlf/Resources.ja.xlf | 48 +- .../Resources/xlf/Resources.ko.xlf | 48 +- .../Resources/xlf/Resources.pl.xlf | 48 +- .../Resources/xlf/Resources.pt-BR.xlf | 48 +- .../Resources/xlf/Resources.ru.xlf | 48 +- .../Resources/xlf/Resources.tr.xlf | 48 +- .../Resources/xlf/Resources.zh-Hans.xlf | 48 +- .../Resources/xlf/Resources.zh-Hant.xlf | 48 +- .../Resources/xlf/Resources.cs.xlf | 84 +-- .../Resources/xlf/Resources.de.xlf | 84 +-- .../Resources/xlf/Resources.es.xlf | 84 +-- .../Resources/xlf/Resources.fr.xlf | 84 +-- .../Resources/xlf/Resources.it.xlf | 84 +-- .../Resources/xlf/Resources.ja.xlf | 84 +-- .../Resources/xlf/Resources.ko.xlf | 84 +-- .../Resources/xlf/Resources.pl.xlf | 84 +-- .../Resources/xlf/Resources.pt-BR.xlf | 84 +-- .../Resources/xlf/Resources.ru.xlf | 84 +-- .../Resources/xlf/Resources.tr.xlf | 84 +-- .../Resources/xlf/Resources.zh-Hans.xlf | 84 +-- .../Resources/xlf/Resources.zh-Hant.xlf | 84 +-- .../Resources/xlf/Resources.cs.xlf | 30 +- .../Resources/xlf/Resources.de.xlf | 30 +- .../Resources/xlf/Resources.es.xlf | 30 +- .../Resources/xlf/Resources.fr.xlf | 30 +- .../Resources/xlf/Resources.it.xlf | 30 +- .../Resources/xlf/Resources.ja.xlf | 30 +- .../Resources/xlf/Resources.ko.xlf | 30 +- .../Resources/xlf/Resources.pl.xlf | 30 +- .../Resources/xlf/Resources.pt-BR.xlf | 30 +- .../Resources/xlf/Resources.ru.xlf | 30 +- .../Resources/xlf/Resources.tr.xlf | 30 +- .../Resources/xlf/Resources.zh-Hans.xlf | 30 +- .../Resources/xlf/Resources.zh-Hant.xlf | 30 +- .../Resources/xlf/Resources.cs.xlf | 9 +- .../Resources/xlf/Resources.de.xlf | 9 +- .../Resources/xlf/Resources.es.xlf | 9 +- .../Resources/xlf/Resources.fr.xlf | 9 +- .../Resources/xlf/Resources.it.xlf | 9 +- .../Resources/xlf/Resources.ja.xlf | 9 +- .../Resources/xlf/Resources.ko.xlf | 9 +- .../Resources/xlf/Resources.pl.xlf | 9 +- .../Resources/xlf/Resources.pt-BR.xlf | 9 +- .../Resources/xlf/Resources.ru.xlf | 9 +- .../Resources/xlf/Resources.tr.xlf | 9 +- .../Resources/xlf/Resources.zh-Hans.xlf | 9 +- .../Resources/xlf/Resources.zh-Hant.xlf | 9 +- .../Resources/xlf/CommonResources.cs.xlf | 15 +- .../Resources/xlf/CommonResources.de.xlf | 15 +- .../Resources/xlf/CommonResources.es.xlf | 15 +- .../Resources/xlf/CommonResources.fr.xlf | 15 +- .../Resources/xlf/CommonResources.it.xlf | 15 +- .../Resources/xlf/CommonResources.ja.xlf | 15 +- .../Resources/xlf/CommonResources.ko.xlf | 15 +- .../Resources/xlf/CommonResources.pl.xlf | 15 +- .../Resources/xlf/CommonResources.pt-BR.xlf | 15 +- .../Resources/xlf/CommonResources.ru.xlf | 15 +- .../Resources/xlf/CommonResources.tr.xlf | 15 +- .../Resources/xlf/CommonResources.zh-Hans.xlf | 15 +- .../Resources/xlf/CommonResources.zh-Hant.xlf | 15 +- .../Resources/xlf/Resources.cs.xlf | 135 ++--- .../Resources/xlf/Resources.de.xlf | 135 ++--- .../Resources/xlf/Resources.es.xlf | 135 ++--- .../Resources/xlf/Resources.fr.xlf | 135 ++--- .../Resources/xlf/Resources.it.xlf | 135 ++--- .../Resources/xlf/Resources.ja.xlf | 135 ++--- .../Resources/xlf/Resources.ko.xlf | 135 ++--- .../Resources/xlf/Resources.pl.xlf | 135 ++--- .../Resources/xlf/Resources.pt-BR.xlf | 135 ++--- .../Resources/xlf/Resources.ru.xlf | 135 ++--- .../Resources/xlf/Resources.tr.xlf | 135 ++--- .../Resources/xlf/Resources.zh-Hans.xlf | 135 ++--- .../Resources/xlf/Resources.zh-Hant.xlf | 135 ++--- .../Resources/xlf/Resources.cs.xlf | 9 +- .../Resources/xlf/Resources.de.xlf | 9 +- .../Resources/xlf/Resources.es.xlf | 9 +- .../Resources/xlf/Resources.fr.xlf | 9 +- .../Resources/xlf/Resources.it.xlf | 9 +- .../Resources/xlf/Resources.ja.xlf | 9 +- .../Resources/xlf/Resources.ko.xlf | 9 +- .../Resources/xlf/Resources.pl.xlf | 9 +- .../Resources/xlf/Resources.pt-BR.xlf | 9 +- .../Resources/xlf/Resources.ru.xlf | 9 +- .../Resources/xlf/Resources.tr.xlf | 9 +- .../Resources/xlf/Resources.zh-Hans.xlf | 9 +- .../Resources/xlf/Resources.zh-Hant.xlf | 9 +- .../Resources/xlf/Resources.cs.xlf | 21 +- .../Resources/xlf/Resources.de.xlf | 21 +- .../Resources/xlf/Resources.es.xlf | 21 +- .../Resources/xlf/Resources.fr.xlf | 21 +- .../Resources/xlf/Resources.it.xlf | 21 +- .../Resources/xlf/Resources.ja.xlf | 21 +- .../Resources/xlf/Resources.ko.xlf | 21 +- .../Resources/xlf/Resources.pl.xlf | 21 +- .../Resources/xlf/Resources.pt-BR.xlf | 21 +- .../Resources/xlf/Resources.ru.xlf | 21 +- .../Resources/xlf/Resources.tr.xlf | 21 +- .../Resources/xlf/Resources.zh-Hans.xlf | 21 +- .../Resources/xlf/Resources.zh-Hant.xlf | 21 +- .../Resources/xlf/Resources.cs.xlf | 24 +- .../Resources/xlf/Resources.de.xlf | 24 +- .../Resources/xlf/Resources.es.xlf | 24 +- .../Resources/xlf/Resources.fr.xlf | 24 +- .../Resources/xlf/Resources.it.xlf | 24 +- .../Resources/xlf/Resources.ja.xlf | 24 +- .../Resources/xlf/Resources.ko.xlf | 24 +- .../Resources/xlf/Resources.pl.xlf | 24 +- .../Resources/xlf/Resources.pt-BR.xlf | 24 +- .../Resources/xlf/Resources.ru.xlf | 24 +- .../Resources/xlf/Resources.tr.xlf | 24 +- .../Resources/xlf/Resources.zh-Hans.xlf | 24 +- .../Resources/xlf/Resources.zh-Hant.xlf | 24 +- .../Resources/xlf/Resources.cs.xlf | 15 +- .../Resources/xlf/Resources.de.xlf | 15 +- .../Resources/xlf/Resources.es.xlf | 15 +- .../Resources/xlf/Resources.fr.xlf | 15 +- .../Resources/xlf/Resources.it.xlf | 15 +- .../Resources/xlf/Resources.ja.xlf | 15 +- .../Resources/xlf/Resources.ko.xlf | 15 +- .../Resources/xlf/Resources.pl.xlf | 15 +- .../Resources/xlf/Resources.pt-BR.xlf | 15 +- .../Resources/xlf/Resources.ru.xlf | 15 +- .../Resources/xlf/Resources.tr.xlf | 15 +- .../Resources/xlf/Resources.zh-Hans.xlf | 15 +- .../Resources/xlf/Resources.zh-Hant.xlf | 15 +- .../Resources/xlf/Resources.cs.xlf | 510 ++++++------------ .../Resources/xlf/Resources.de.xlf | 510 ++++++------------ .../Resources/xlf/Resources.es.xlf | 510 ++++++------------ .../Resources/xlf/Resources.fr.xlf | 510 ++++++------------ .../Resources/xlf/Resources.it.xlf | 510 ++++++------------ .../Resources/xlf/Resources.ja.xlf | 510 ++++++------------ .../Resources/xlf/Resources.ko.xlf | 510 ++++++------------ .../Resources/xlf/Resources.pl.xlf | 510 ++++++------------ .../Resources/xlf/Resources.pt-BR.xlf | 510 ++++++------------ .../Resources/xlf/Resources.ru.xlf | 510 ++++++------------ .../Resources/xlf/Resources.tr.xlf | 510 ++++++------------ .../Resources/xlf/Resources.zh-Hans.xlf | 510 ++++++------------ .../Resources/xlf/Resources.zh-Hant.xlf | 510 ++++++------------ 208 files changed, 4706 insertions(+), 9412 deletions(-) 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 collected Protokol 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} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.de.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.de.xlf index 9e0c9d69d4..7cc9470fcb 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.de.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.de.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Ausnahme beim Erfassen von abschließenden Einträgen aus dem Ereignisprotokoll "{0}": {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} Der DataCollector des Ereignisprotokolls hat den eventLogContext für DataCollectionContext nicht gefunden: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected Das Ereignisprotokoll "{0}" wurde während der Sammlung möglicherweise gelöscht. Einige Ereignisse wurden eventuell nicht erfasst. - - + Unable to read event log '{0}' from computer '{1}' Das Ereignisprotokoll "{0}" konnte vom Computer "{1}" nicht gelesen werden. - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} Beim Ereignisprotokoll "{0}" ist eine Ausnahme aufgetreten. Einige Ereignisse gehen möglicherweise verloren. Fehler: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.es.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.es.xlf index 1985f13d72..24b4c70ce0 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.es.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.es.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Excepción al recopilar las entradas finales del registro de eventos "{0}": {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} La propiedad DataCollector del registro de eventos no encontró eventLogContext para el contexto de DataCollectionContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected Es posible que el registro de eventos "{0}" se haya borrado durante la recopilación; algunos eventos pueden no haberse recopilado - - + Unable to read event log '{0}' from computer '{1}' No se puede leer el registro de eventos "{0}" desde el equipo "{1}" - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} El registro de eventos "{0}" ha encontrado una excepción; algunos eventos pueden haberse perdido. Error: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.fr.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.fr.xlf index f130cb2a27..20b8c11b59 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.fr.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.fr.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Une exception s'est produite durant la collecte des entrées finales dans le journal des événements '{0}' : {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} Le DataCollector du journal des événements n'a pas trouvé eventLogContext pour DataCollectionContext : {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected Le journal des événements '{0}' a peut-être été effacé durant la collecte. Il est possible que certains événements n'aient pas été collectés - - + Unable to read event log '{0}' from computer '{1}' Impossible de lire le journal des événements '{0}' de l'ordinateur '{1}' - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} Le journal des événements '{0}' a rencontré une exception, certains événements risquent d'être perdus. Erreur : {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.it.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.it.xlf index 1bff6db601..2df0527f2e 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.it.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.it.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Si è verificata un'eccezione durante la raccolta delle voci finali del log eventi '{0}': {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} L'agente di raccolta dati del log eventi non ha trovato l'elemento eventLogContext per DataCollectionContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected È possibile che il log eventi '{0}' sia stato cancellato durante la raccolta. Alcuni eventi non sono stati raccolti - - + Unable to read event log '{0}' from computer '{1}' Non è possibile leggere il log eventi '{0}' dal computer '{1}' - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} Il log eventi '{0}' ha rilevato un'eccezione. È possibile che alcuni eventi siano stati persi. Errore: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ja.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ja.xlf index d6ac9820be..59bc0b3c93 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ja.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ja.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} イベント ログ '{0}' からの最後のエントリの収集中に例外が発生しました: {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} イベント ログ DataCollector では、DataCollectionContext の eventLogContext が見つかりませんでした: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected 収集中に '{0}' イベント ログがクリアされた可能性があるため、一部のイベントが収集されていない可能性があります。 - - + Unable to read event log '{0}' from computer '{1}' イベント ログ '{0}' をコンピューター '{1}' から読み取れません - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} '{0}' イベント ログで例外が発生しました。一部のイベントが失われる可能性があります。エラー: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ko.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ko.xlf index e8f7f9e78b..f7e74176d3 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ko.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ko.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} 이벤트 로그 ‘{0}’에서 최종 항목을 수집하는 동안 예외가 발생했습니다. {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} 이벤트 로그 DataCollector에서 DataCollectionContext에 대한 eventLogContext를 찾지 못했습니다. {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected 수집 중 ‘{0}’ 이벤트 로그가 지워졌을 수 있습니다. 일부 이벤트는 수집되지 않았을 수 있습니다. - - + Unable to read event log '{0}' from computer '{1}' ‘{1}’ 컴퓨터에서 이벤트 로그 ‘{0}’을(를) 읽을 수 없습니다. - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} ‘{0}’ 이벤트 로그에서 예외가 발생했습니다. 일부 이벤트가 손실되었을 수 있습니다. 오류: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pl.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pl.xlf index 84547aeb7b..cb78412304 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pl.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pl.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Wystąpił wyjątek podczas zbierania końcowych wpisów z dziennika zdarzeń „{0}”: {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} Element DataCollector dziennika zdarzeń nie znalazł elementu eventLogContext dla elementu DataCollectionContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected Dziennik zdarzeń „{0}” mógł zostać wyczyszczony podczas zbierania; niektóre zdarzenia mogły nie zostać zebrane - - + Unable to read event log '{0}' from computer '{1}' Nie można odczytać dziennika zdarzeń „{0}” z komputera „{1}” - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} Dziennik zdarzeń „{0}” napotkał wyjątek, niektóre zdarzenia mogły zostać utracone. Błąd: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pt-BR.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pt-BR.xlf index 319a11a411..c944d9ced2 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pt-BR.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.pt-BR.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Ocorreu uma exceção ao coletar entradas finais do log de eventos '{0}': {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} O DataCollector de Log de Eventos não encontrou o eventLogContext para DataCollectionContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected O log de evento '{0}' pode ter sido limpo durante a coleção; alguns eventos podem não ter sido coletados - - + Unable to read event log '{0}' from computer '{1}' Não é possível ler o log de eventos '{0}' do computador '{1}' - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} O log de eventos '{0}' encontrou uma exceção, alguns eventos podem ser perdidos. Erro: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ru.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ru.xlf index 95c012701d..a3c70394a1 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ru.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.ru.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} Произошло исключение при сборе последних записей в журнале событий "{0}": {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} Сборщик данных из журнала событий не нашел eventLogContext по DataCollectionContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected Возможно, журнал событий "{0}" был очищен во время сбора данных. Некоторые события могли быть не собраны. - - + Unable to read event log '{0}' from computer '{1}' Не удалось прочитать журнал событий "{0}" с компьютера "{1}" - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} В журнале событий "{0}" произошло исключение; некоторые события могли быть потеряны. Ошибка: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.tr.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.tr.xlf index e54046ce39..cf2efc3fbf 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.tr.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.tr.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} '{0}' olay günlüğündeki son girdiler toplanırken bir özel durum oluştu: {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} Event Log DataCollector, şu DataCollectionContext için eventLogContext bulamadı: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected '{0}' olay günlüğü toplama sırasında temizlenmiş olabilir. Bazı olaylar toplanmamış olabilir - - + Unable to read event log '{0}' from computer '{1}' '{1}' bilgisayarından olay günlüğü '{0}' okunamıyor - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} '{0}' olay günlüğü bir özel durumla karşılaştı. Bazı olaylar kaybolabilir. Hata : {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hans.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hans.xlf index d88b045014..e858659144 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hans.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} 从事件日志“{0}”中收集最后的条目时出现异常: {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} 事件日志数据收集器找不到数据收集上下文的事件日志上下文: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected “{0}”事件日志可能在收集期间已被清除；某些事件可能还未被收集 - - + Unable to read event log '{0}' from computer '{1}' 无法从计算机“{1}”中读取事件日志“{0}” - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} 事件日志“{0}”出现异常，某些事件可能已丢失。错误: {1} - - + diff --git a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hant.xlf b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hant.xlf index c5fe9a4c93..6fbe5ea1ac 100644 --- a/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/DataCollectors/Microsoft.TestPlatform.Extensions.EventLogCollector/Resources/xlf/Resources.zh-Hant.xlf @@ -5,32 +5,27 @@ An exception occurred while collecting final entries from the event log '{0}': {1} 從事件記錄檔 '{0}' 收集最終項目時發生例外狀況: {1} - - + Event Log DataCollector did not find eventLogContext for DataCollectionContext: {0} 事件記錄檔 DataCollector 找不到 DataCollectionContext 的 eventLogContext: {0} - - + The '{0}' event log may have been cleared during collection; some events may not have been collected '{0}' 事件記錄檔可能已在收集期間清除; 某些事件可能未收集到 - - + Unable to read event log '{0}' from computer '{1}' 無法從電腦 '{1}' 讀取事件記錄檔 '{0} - - + The '{0}' event log has encountered an exception, some events might get lost. Error : {1} '{0}' 事件記錄檔發生例外狀況，某些事件可能會遺失。錯誤: {1} - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.cs.xlf index cabaf23702..ca211fbee3 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.cs.xlf @@ -5,32 +5,27 @@ Build completed. Sestavení bylo dokončeno. - - + Build started, please wait... Začalo sestavování. Počkejte prosím... - - + Test run for {0} ({1}) Testovací běh pro {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Upozornění: Aktualizujte odkaz na balíček Microsoft.NET.Test.Sdk na verzi 15.8.0 nebo novější, aby se získalo pokrytí kódu. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Přeskakuje se spuštění testu pro projekt {0}. Pokud chcete spustit testy pomocí příkazu dotnet test, přidejte do souboru projektu vlastnost <IsTestProject>true</IsTestProject>. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.de.xlf index a3218e58d1..169344be83 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.de.xlf @@ -5,32 +5,27 @@ Build completed. Buildvorgang abgeschlossen. - - + Build started, please wait... Buildvorgang gestartet, bitte warten... - - + Test run for {0} ({1}) Testlauf für "{0}" ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Warnung: Aktualisieren Sie die Microsoft.NET.Test.Sdk-Paketreferenz auf Version 15.8.0 oder höher, um von Code Coverage zu profitieren. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Die Ausführung des Tests für das Projekt "{0}" wird übersprungen. Um Tests mit "dotnet test" auszuführen, fügen Sie der Projektdatei die Eigenschaft <IsTestProject>true</IsTestProject> hinzu. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.es.xlf index 9db62f0926..bfbbb265a6 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.es.xlf @@ -5,32 +5,27 @@ Build completed. Se completó la compilación. - - + Build started, please wait... Compilación iniciada, espere... - - + Test run for {0} ({1}) Serie de pruebas para {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Advertencia: Actualice la referencia del paquete Microsoft.NET.Test.Sdk a la versión 15.8.0 o posterior para recopilar la cobertura de código. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Omitiendo la ejecución de la prueba para el proyecto {0}. Para ejecutar pruebas con dotnet test, agregue la propiedad "<IsTestProject>true</IsTestProject>" al archivo del proyecto. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.fr.xlf index c467a83707..cac849faa0 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.fr.xlf @@ -5,32 +5,27 @@ Build completed. Fin de la build. - - + Build started, please wait... La build a démarré. Patientez… - - + Test run for {0} ({1}) Série de tests pour {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Avertissement : mettez à jour la référence de package Microsoft.NET.Test.Sdk vers la version 15.8.0 ou ultérieure pour collecter la couverture du code. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Le test en cours d'exécution est ignoré pour le projet {0}. Pour exécuter des tests avec dotnet test, ajoutez la propriété "<IsTestProject>true</IsTestProject>" au fichier projet. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.it.xlf index 17768120d6..04056ad6ca 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.it.xlf @@ -5,32 +5,27 @@ Build completed. Compilazione completata. - - + Build started, please wait... Compilazione avviata. Attendere... - - + Test run for {0} ({1}) Esecuzione dei test per {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Avviso: per raccogliere i dati di code coverage, aggiornare il riferimento al pacchetto Microsoft.NET.Test.Sdk alla versione 15.8.0 o successiva. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. L'esecuzione del test per il progetto {0} verrà ignorata. Per eseguire test con dotnet test, aggiungere la proprietà "<IsTestProject>true</IsTestProject>" al file di progetto. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ja.xlf index c309e58b87..cd7c252457 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ja.xlf @@ -5,32 +5,27 @@ Build completed. ビルドが完了しました。 - - + Build started, please wait... ビルドが開始されました。しばらくお待ちください... - - + Test run for {0} ({1}) {0} ({1}) のテスト実行 - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. 警告: コード カバレッジを収集するには、Microsoft.NET.Test.Sdk パッケージ参照をバージョン 15.8.0 以降に更新してください。 - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. プロジェクト {0} へのテストの実行をスキップしています。dotnet テストでテストを実行するには、"<IsTestProject>true</IsTestProject>" プロパティをプロジェクト ファイルに追加します。 - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ko.xlf index 7d0532f09d..3f09767df9 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ko.xlf @@ -5,32 +5,27 @@ Build completed. 빌드가 완료되었습니다. - - + Build started, please wait... 빌드가 시작되었습니다. 잠시 기다려 주세요. - - + Test run for {0} ({1}) {0}({1})에 대한 테스트 실행 - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. 경고: 코드 검사를 수집하려면 Microsoft.NET.Test.Sdk 패키지 참조를 버전 15.8.0 이상으로 업데이트하세요. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. 프로젝트 {0}에 대한 테스트 실행을 건너뜁니다. dotnet 테스트와 함께 테스트를 실행하려면 "<IsTestProject>true</IsTestProject>" 속성을 프로젝트 파일에 추가합니다. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pl.xlf index f5bdcfb955..889879bdd8 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pl.xlf @@ -5,32 +5,27 @@ Build completed. Kompilacja zakończona. - - + Build started, please wait... Kompilacja została rozpoczęta, czekaj... - - + Test run for {0} ({1}) Przebieg testu dla: {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Ostrzeżenie: zaktualizuj odwołanie do pakietu Microsoft.NET.Test.Sdk do wersji 15.8.0 lub nowszej w celu zbierania danych dotyczących pokrycia kodu. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Pomijanie uruchamiania testu dla projektu {0}. Aby uruchomić testy za pomocą polecenia dotnet test, dodaj właściwość „<IsTestProject>true</IsTestProject>” do pliku projektu. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pt-BR.xlf index 3aaba3fadc..1c529a940b 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.pt-BR.xlf @@ -5,32 +5,27 @@ Build completed. Build concluído. - - + Build started, please wait... Build iniciada, aguarde... - - + Test run for {0} ({1}) Execução de teste para {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Aviso: Atualize a referência do pacote Microsoft.NET.Test.Sdk para a versão 15.8.0 ou posterior para coletar a cobertura do código. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Ignorando a execução de teste do projeto {0}. Para executar testes com dotnet test, adicione a propriedade "<IsTestProject>true</IsTestProject>" ao arquivo de projeto. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ru.xlf index a8e886ce9f..e4cda322f1 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.ru.xlf @@ -5,32 +5,27 @@ Build completed. Сборка выполнена. - - + Build started, please wait... Сборка начата, подождите... - - + Test run for {0} ({1}) Тестовый запуск для {0} ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Внимание. Для сбора данных об объеме протестированного кода обновите пакет Microsoft.NET.Test.Sdk по ссылке как минимум до версии 15.8.0. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. Пропуск выполнения теста для проекта {0}. Чтобы выполнить тесты с помощью теста dotnet, добавьте свойство "<IsTestProject>true</IsTestProject>" в файл проекта. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.tr.xlf index 56fa27e4d0..afc5584429 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.tr.xlf @@ -5,32 +5,27 @@ Build completed. Derleme tamamlandı. - - + Build started, please wait... Derleme başlatıldı. Lütfen bekleyin... - - + Test run for {0} ({1}) {0} ({1}) için test çalıştırması - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. Uyarı: Kod kapsamını toplamak için Microsoft.NET.Test.Sdk paketinin başvurusunu 15.8.0 veya üzeri bir sürüme güncelleştirin. - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. {0} projesi için test çalıştırma atlanıyor. Testleri dotnet test ile çalıştırmak için proje dosyasına "<IsTestProject>true</IsTestProject>" özelliğini ekleyin. - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hans.xlf index d06c582e43..505a7221ab 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hans.xlf @@ -5,32 +5,27 @@ Build completed. 完成的生成。 - - + Build started, please wait... 已开始生成，请等待... - - + Test run for {0} ({1}) {0} ({1})的测试运行 - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. 警告: 将 Microsoft.NET.Test.Sdk 包引用更新为版本 15.8.0 或更高版本，以便收集代码覆盖率。 - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. 正在跳过项目 {0} 的运行测试。若要使用 dotnet test 运行 dotnet 测试，请向项目文件添加 "<IsTestProject>true</IsTestProject>" 属性。 - - + diff --git a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hant.xlf index b195bb6a0e..24dc701c99 100644 --- a/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Build/Resources/xlf/Resources.zh-Hant.xlf @@ -5,32 +5,27 @@ Build completed. 建置完成。 - - + Build started, please wait... 已開始建置，請稍候... - - + Test run for {0} ({1}) {0} 的測試回合 ({1}) - - + Warning: Update the Microsoft.NET.Test.Sdk package reference to version 15.8.0 or later to collect code coverage. 警告: 將 Microsoft.NET.Test.Sdk 套件參考更新至版本 15.8.0 或更新版本，才可收集程式碼涵蓋範圍。 - - + Skipping running test for project {0}. To run tests with dotnet test add "<IsTestProject>true</IsTestProject>" property to project file. 跳過專案 {0} 目前正在執行中的測試。若要執行有 dotnet 測試的測試項目，請對專案檔新增 "<IsTestProject>true</IsTestProject>" 屬性。 - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.cs.xlf index a23b841442..130037af9d 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.cs.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.de.xlf index 9fb3c93a7c..696353c967 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.de.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.es.xlf index 299149c38e..fa89843ebc 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.es.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.fr.xlf index 05ad447ee8..4a91eaea6f 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.fr.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.it.xlf index 02afa15de7..bd7749d7f0 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.it.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ja.xlf index 4839b465cc..7ee98aebfa 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ja.xlf @@ -4,27 +4,23 @@ 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. この実行に対して適切なテスト ランタイム プロバイダーが見つかりませんでした。 - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ko.xlf index 1e362a1d5b..016e6ed72d 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ko.xlf @@ -4,27 +4,23 @@ 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. 이 실행에 적합한 테스트 런타임 공급자를 찾지 못했습니다. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pl.xlf index 5a4353fe67..be1dd5c075 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pl.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pt-BR.xlf index ebd972ab54..f851bd4b20 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.pt-BR.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ru.xlf index 37fdb298e2..4f3126a6d5 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.ru.xlf @@ -4,27 +4,23 @@ 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. Не найден подходящий поставщик среды выполнения теста для этого запуска. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.tr.xlf index c54ae6c42d..88325a4bb4 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.tr.xlf @@ -4,27 +4,23 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hans.xlf index 9f608facb3..5f3ce7babc 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hans.xlf @@ -4,27 +4,23 @@ 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. 对于此运行，未找到适合的测试运行时提供程序。 - - + diff --git a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hant.xlf index 235238d939..22e7d1e87b 100644 --- a/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Client/Resources/xlf/Resources.zh-Hant.xlf @@ -4,27 +4,23 @@ 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. 找不到適用於此回合的測試執行階段提供者。 - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.cs.xlf index 4bc0e219ab..6e90ce0ce6 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.cs.xlf @@ -4,231 +4,193 @@ 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.de.xlf index 872fa8d83d..4ad0e12965 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.de.xlf @@ -4,231 +4,193 @@ 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 "&" fehlt The 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.es.xlf index 5749a41500..672a9bfa70 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.es.xlf @@ -4,231 +4,193 @@ 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álida Test 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 operando Missing 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.fr.xlf index acc66d709d..8c3a5097e2 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.fr.xlf @@ -4,231 +4,193 @@ 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 : ')' manquante Error: Missing '(' - - + Erreur : '(' manquante Error: Missing operand - - + Erreur : opérande manquant Missing 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 : - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.it.xlf index 47f1c2f0dc..6ca503bad2 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.it.xlf @@ -4,231 +4,193 @@ 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'operando Missing 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ja.xlf index bafe36b56f..74c34de4c4 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ja.xlf @@ -4,231 +4,193 @@ 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: スタック トレース: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ko.xlf index 076391285b..7e6a2db159 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ko.xlf @@ -4,231 +4,193 @@ 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: 스택 추적: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pl.xlf index 7deef5dcf2..c1ba20ccc6 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pl.xlf @@ -4,231 +4,193 @@ 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 operacji Missing 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pt-BR.xlf index c27fd12dd5..48c5126257 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.pt-BR.xlf @@ -4,231 +4,193 @@ 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: ')' ausente Error: Missing '(' - - + Erro: '(' ausente Error: Missing operand - - + Erro: operando ausente Missing 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ru.xlf index 3055677cd2..c8732c97b2 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.ru.xlf @@ -4,231 +4,193 @@ 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: Трассировка стека: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.tr.xlf index 285f95eca8..a030305684 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.tr.xlf @@ -4,231 +4,193 @@ 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: ')' eksik Error: Missing '(' - - + Hata: '(' eksik Error: Missing operand - - + Hata: İşlenen eksik Missing Operator '|' or '&' - - + '|' veya '&' işleci eksik The 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: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hans.xlf index 964beb6e60..646975d4dc 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hans.xlf @@ -4,231 +4,193 @@ 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: 堆栈跟踪: - - + diff --git a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hant.xlf index 3dc55e1a06..dc6339b00c 100644 --- a/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Common/Resources/xlf/Resources.zh-Hant.xlf @@ -4,231 +4,193 @@ 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: 堆疊追蹤: - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.cs.xlf index 9b5843c21d..95ef147464 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.cs.xlf @@ -4,63 +4,53 @@ 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 crashed Proces 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ů. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.de.xlf index 52b03f498f..b101f56dea 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.de.xlf @@ -4,63 +4,53 @@ 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 crashed Der Testhostprozess ist abgestürzt. - - + Cannot attach the debugger to the default test host. Der Debugger kann nicht an den Standardtesthost angefügt werden. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.es.xlf index 034e96cfbd..56268124be 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.es.xlf @@ -4,63 +4,53 @@ 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 crashed Proceso 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. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.fr.xlf index be3dfd485a..fd10885589 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.fr.xlf @@ -4,63 +4,53 @@ 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 crashed Plantage 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. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.it.xlf index 6eb97b4764..c859fd81f8 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.it.xlf @@ -4,63 +4,53 @@ 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 crashed Arresto 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. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ja.xlf index e65e888c39..cd1e2f66ab 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ja.xlf @@ -4,63 +4,53 @@ 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. デバッガーを既定のテスト ホストにアタッチできません。 - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ko.xlf index c91803c134..0c880cec04 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ko.xlf @@ -4,63 +4,53 @@ 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. 기본 테스트 호스트에 디버거를 연결할 수 없습니다. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pl.xlf index cdda303565..777913c9a6 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pl.xlf @@ -4,63 +4,53 @@ 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 crashed Wystą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. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pt-BR.xlf index c9076e811c..e7b6bd3768 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.pt-BR.xlf @@ -4,63 +4,53 @@ 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 crashed Falha 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. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ru.xlf index c33868730e..beb0b4325b 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.ru.xlf @@ -4,63 +4,53 @@ 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. Не удается подключить отладчик к узлу тестирования по умолчанию. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.tr.xlf index 1170a92504..ef2baae23d 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.tr.xlf @@ -4,63 +4,53 @@ 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 crashed Test ana işlemi kilitlendi - - + Cannot attach the debugger to the default test host. Hata ayıklayıcı, varsayılan test ana bilgisayarına eklenemiyor. - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hans.xlf index c73dfb1e3e..9003ea3047 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hans.xlf @@ -4,63 +4,53 @@ 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. 无法将调试程序附加到默认测试主机。 - - + diff --git a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hant.xlf index 9a2cf1ecda..dbd7dec68b 100644 --- a/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.CommunicationUtilities/Resources/xlf/Resources.zh-Hant.xlf @@ -4,63 +4,53 @@ 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. 無法將偵錯工具連結到預設測試主機。 - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.cs.xlf index be029dc21a..c5e146ea0a 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.cs.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.de.xlf index f18ad2f727..a19990733b 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.de.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.es.xlf index a63facbd59..bffb274152 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.es.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.fr.xlf index d5b073243e..232fca3424 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.fr.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.it.xlf index b2255bad73..dcf6d4cda6 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.it.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ja.xlf index 547b0712e5..f67cbfed6e 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ja.xlf @@ -4,99 +4,83 @@ 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 環境変数で使用できることを確認してください。 - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ko.xlf index 7330eb2a26..e4aad90fa0 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ko.xlf @@ -4,99 +4,83 @@ 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 환경 변수에서 사용할 수 있는지 확인하세요. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pl.xlf index a68aaba786..a33bd39544 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pl.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pt-BR.xlf index 1f0feff325..ff67902e41 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.pt-BR.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ru.xlf index f946559eeb..10ba99d23f 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.ru.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.tr.xlf index c8753a76af..bf7772fa77 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.tr.xlf @@ -4,99 +4,83 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hans.xlf index af3e49e988..d592e83ec8 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hans.xlf @@ -4,99 +4,83 @@ 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 环境变量中。 - - + diff --git a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hant.xlf index 6a5aa518b3..e75104c67f 100644 --- a/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.CoreUtilities/Resources/xlf/Resources.zh-Hant.xlf @@ -4,99 +4,83 @@ 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 環境變數中使用。 - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.cs.xlf index 2f7bbad104..284e022651 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.cs.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.de.xlf index 6c904cebc0..313da6e3c9 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.de.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.es.xlf index 66df550df1..e6e11682df 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.es.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.fr.xlf index 9bbef613e5..3d5cdc0837 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.fr.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.it.xlf index bec91e032a..c23e7f494e 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.it.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ja.xlf index 4743cd71b3..30473f39f4 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ja.xlf @@ -4,8 +4,7 @@ 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} のプロキシは、既に使用可能になっているため、再度エンキューすることはできません。 - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ko.xlf index 356da2e63f..dbc0fdcce0 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ko.xlf @@ -4,8 +4,7 @@ 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}인 프록시를 이미 사용할 수 있으며 큐에 다시 넣을 수 없습니다. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pl.xlf index 5b7c35b236..e582ae5e1a 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pl.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pt-BR.xlf index fcd193d672..90cb2bc6cb 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.pt-BR.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ru.xlf index 02875ab766..ae20ce86f1 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.ru.xlf @@ -4,8 +4,7 @@ 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} уже доступен и не может быть повторно поставлен в очередь. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.tr.xlf index 9ebfed314d..8f413efa45 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.tr.xlf @@ -4,8 +4,7 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hans.xlf index f8dfd6147e..cdd86cec6a 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hans.xlf @@ -4,8 +4,7 @@ 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} 的代理已可用，无法重新排队。 - - + diff --git a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hant.xlf index 5943c6391d..6b66d3baef 100644 --- a/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.CrossPlatEngine/Resources/xlf/Resources.zh-Hant.xlf @@ -4,8 +4,7 @@ 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 已可供使用，但無法重新加入佇列。 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.cs.xlf index f25420a381..3781d6a61c 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.cs.xlf @@ -16,38 +16,32 @@ Tento test může a nemusí být příčinou chybového ukončení. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. Vyžadovaná proměnná prostředí PROCDUMP_PATH má hodnotu Null nebo je prázdná. Nastavte pro ni cestu ke složce obsahující příslušný spustitelný soubor ProcDump. - - + Collect dump was enabled but no dump file was generated. Bylo povoleno shromáždění výpisu, ale nebyl vygenerován žádný soubor výpisu. - - + The blame parameter key specified {0} is not valid. Ignoring this key. Zadaný klíč parametru blame {0} není platný. Tento klíč se bude ignorovat. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. Klíč parametru blame {0} dokáže podporovat jen hodnoty {1}/{2}. Tento klíč se bude ignorovat. - - + Could not start process dump: {0} Nešlo spustit výpis procesu: {0} - - + CollectDump was enabled but dump file was not generated. Byla povolena funkce CollectDump, ale soubor výpisu nebyl vygenerován. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Tento test může a nemusí být příčinou chybového ukončení. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Jako časový limit se přidala neočekávaná hodnota {0}. Zadejte prosím hodnotu v tomto formátu: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Tento test může a nemusí být příčinou chybového ukončení. Dumping this process tree (from bottom) Vytváří se výpis tohoto stromu procesu (zespod) - - + minutes minuty - - + seconds sekundy - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.de.xlf index a6cf8dceda..8751849d00 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.de.xlf @@ -16,38 +16,32 @@ Dieser Test kann, muss aber nicht unbedingt die Absturzursache sein. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. Die erforderliche Umgebungsvariable PROCDUMP_PATH war NULL oder leer. Legen Sie PROCDUMP_PATH auf den Pfad des Ordners fest, der die geeignete ausführbare procdump-Datei enthält. - - + Collect dump was enabled but no dump file was generated. Die Abbilderfassung war aktiviert, aber es wurde keine Abbilddatei generiert. - - + The blame parameter key specified {0} is not valid. Ignoring this key. Der angegebene blame-Parameterschlüssel "{0}" ist ungültig. Dieser Schlüssel wird ignoriert. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. Der blame-Parameterschlüssel "{0}" kann nur die Werte "{1}"/"{2}" unterstützen. Dieser Schlüssel wird ignoriert. - - + Could not start process dump: {0} Prozesssicherung konnte nicht gestartet werden: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump war aktiviert, aber es wurde keine Abbilddatei generiert. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Dieser Test kann, muss aber nicht unbedingt die Absturzursache sein. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Unerwarteter Wert "{0}" als Timeout angegeben. Geben Sie einen Wert in folgendem Format an: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Dieser Test kann, muss aber nicht unbedingt die Absturzursache sein. Dumping this process tree (from bottom) Diese Prozessstruktur wird gesichert (von unten). - - + minutes Minuten - - + seconds Sekunden - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.es.xlf index b39b63d67c..8890c61094 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.es.xlf @@ -16,38 +16,32 @@ Esta prueba puede ser el origen del bloqueo o no serlo. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. La variable de entorno PROCDUMP_PATH requerida era NULL o estaba vacía. Establezca PROCDUMP_PATH en la ruta de acceso de la carpeta que contiene el ejecutable procdump correcto. - - + Collect dump was enabled but no dump file was generated. La opción para recopilar un volcado de memoria estaba habilitada, pero no se generó ningún archivo de volcado de memoria. - - + The blame parameter key specified {0} is not valid. Ignoring this key. La clave de parámetro blame especificada {0} no es válida. Se omitirá esta clave. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. La clave de parámetro blame {0} solo puede admitir valores {1}/{2}. Se omitirá esta clave. - - + Could not start process dump: {0} No se ha podido iniciar el volcado de proceso: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump estaba habilitado pero no se ha generado el archivo de volcado. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Esta prueba puede ser el origen del bloqueo o no serlo. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Valor inesperado "{0}" proporcionado como tiempo de espera. Indique un valor en este formato: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Esta prueba puede ser el origen del bloqueo o no serlo. Dumping this process tree (from bottom) Volcando este árbol de procesos (desde abajo) - - + minutes minutos - - + seconds segundos - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.fr.xlf index 33a07b1f03..1bab835425 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.fr.xlf @@ -16,38 +16,32 @@ Ce test est éventuellement à l'origine du plantage. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. La variable d'environnement exigée PROCDUMP_PATH était null ou vide. Affectez à PROCDUMP_PATH le chemin du dossier contenant l'exécutable procdump approprié. - - + Collect dump was enabled but no dump file was generated. La collecte de fichiers dump a été activée, mais aucun fichier dump n'a été généré. - - + The blame parameter key specified {0} is not valid. Ignoring this key. La clé de paramètre blame spécifiée {0} n'est pas valide. Cette clé est ignorée. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. La clé de paramètre blame {0} peut prendre en charge uniquement les valeurs {1}/{2}. Cette clé est ignorée. - - + Could not start process dump: {0} Impossible de démarrer le fichier dump du processus : {0} - - + CollectDump was enabled but dump file was not generated. CollectDump a été activé, mais le fichier dump n'a pas été généré. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Ce test est éventuellement à l'origine du plantage. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Valeur inattendue '{0}' fournie en tant que délai d'expiration. Indiquez une valeur au format suivant : 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Ce test est éventuellement à l'origine du plantage. Dumping this process tree (from bottom) Création d'une image mémoire de cette arborescence de processus (à partir du bas) - - + minutes minutes - - + seconds secondes - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.it.xlf index 9e2ac1a324..d666f1b951 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.it.xlf @@ -16,38 +16,32 @@ Il test potrebbe essere l'origine dell'arresto anomalo. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. La variabile di ambiente PROCDUMP_PATH richiesta è Null o vuota. Impostare PROCDUMP_PATH sul percorso della cartella che contiene il file eseguibile appropriato di procdump. - - + Collect dump was enabled but no dump file was generated. La raccolta del dump è stata abilitata ma non è stato generato alcun file di dump. - - + The blame parameter key specified {0} is not valid. Ignoring this key. La chiave specificata {0} del parametro di Blame non è valida e verrà ignorata. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. La chiave {0} del parametro di Blame può supportare solo valori {1}/{2}. Questa chiave verrà ignorata. - - + Could not start process dump: {0} Non è stato possibile avviare il dump del processo: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump è stato abilitato ma non è stato generato alcun file di dump. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Il test potrebbe essere l'origine dell'arresto anomalo. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Il valore '{0}', specificato come timeout, è imprevisto. Specificare un valore in questo formato: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Il test potrebbe essere l'origine dell'arresto anomalo. Dumping this process tree (from bottom) Dump di questo albero processi (dal basso) - - + minutes minuti - - + seconds secondi - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ja.xlf index dd2a537bcf..689a680dc8 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ja.xlf @@ -16,38 +16,32 @@ This test may, or may not be the source of the crash. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. 必須の環境変数 PROCDUMP_PATH は Null または空でした。PROCDUMP_PATH を、適切な procdump 実行可能ファイルを含むフォルダーのパスに設定してください。 - - + Collect dump was enabled but no dump file was generated. ダンプの収集は有効化されましたが、ダンプ ファイルは生成されませんでした。 - - + The blame parameter key specified {0} is not valid. Ignoring this key. 指定された blame パラメーター キー {0} は無効です。このキーは無視されます。 - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. blame パラメーター キー {0} は値 {1}/{2} のみをサポートします。このキーは無視されます。 - - + Could not start process dump: {0} プロセス ダンプを開始できませんでした: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump は有効になりましたが、ダンプ ファイルは生成されませんでした。 - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ This test may, or may not be the source of the crash. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 予期しない値 '{0}' がタイムアウトとして指定されました。次の形式で値を指定してください: 1.5h、90m、5400s、5400000ms、5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ This test may, or may not be the source of the crash. Dumping this process tree (from bottom) このプロセス ツリーをダンプしています (下から) - - + minutes 分 - - + seconds 秒 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ko.xlf index 4d6cadbcf8..87b9f0865f 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ko.xlf @@ -16,38 +16,32 @@ This test may, or may not be the source of the crash. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. 필요한 환경 변수 PROCDUMP_PATH가 null이거나 비어 있습니다. 적절한 procdump 실행 파일이 포함된 폴더의 경로에 PROCDUMP_PATH를 설정하세요. - - + Collect dump was enabled but no dump file was generated. 덤프 수집이 사용하도록 설정되었지만 덤프 파일이 생성되지 않았습니다. - - + The blame parameter key specified {0} is not valid. Ignoring this key. 지정된 blame 매개 변수 키 {0}이(가) 잘못되었습니다. 이 키를 무시합니다. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. blame 매개 변수 키 {0}은(는) {1}/{2} 값만 지원할 수 있습니다. 이 키를 무시합니다. - - + Could not start process dump: {0} 프로세스 덤프를 시작할 수 없음: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump가 사용하도록 설정되었지만 덤프 파일이 생성되지 않았습니다. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ This test may, or may not be the source of the crash. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 예기치 않은 값 '{0}'이(가) 시간 제한으로 제공되었습니다. 1.5h/90m/5400s/5400000ms/5400000 형식으로 값을 제공하세요. - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ This test may, or may not be the source of the crash. Dumping this process tree (from bottom) 이 프로세스 트리 덤핑(아래쪽에서) - - + minutes 분 - - + seconds 초 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pl.xlf index 982d3c7ed9..b8e229978d 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pl.xlf @@ -16,38 +16,32 @@ Ten test może, ale nie musi być źródłem awarii. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. Wymagana zmienna środowiskowa PROCDUMP_PATH miała wartość null lub była pusta. Ustaw zmienną PROCDUMP_PATH na ścieżkę lub folder zawierające odpowiedni plik wykonywalny procdump. - - + Collect dump was enabled but no dump file was generated. Zbieranie zrzutów zostało włączone, ale nie wygenerowano żadnego pliku zrzutu. - - + The blame parameter key specified {0} is not valid. Ignoring this key. Podany klucz parametru blame {0} nie jest prawidłowy. Ten klucz jest ignorowany. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. Klucz parametru blame {0} może obsługiwać tylko wartości {1}/{2}. Ten klucz jest ignorowany. - - + Could not start process dump: {0} Nie można rozpocząć zrzutu procesu: {0} - - + CollectDump was enabled but dump file was not generated. Opcja CollectDump została włączona, ale nie wygenerowano pliku zrzutu. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Ten test może, ale nie musi być źródłem awarii. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Podano nieoczekiwaną wartość „{0}” jako limit czasu. Podaj wartość w następującym formacie: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Ten test może, ale nie musi być źródłem awarii. Dumping this process tree (from bottom) Tworzenie zrzutu tego drzewa procesów (od dołu) - - + minutes min - - + seconds s - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pt-BR.xlf index 823225aa9f..183db0826f 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.pt-BR.xlf @@ -16,38 +16,32 @@ Esse teste pode ser a origem da falha ou não. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. A variável de ambiente obrigatória PROCDUMP_PATH era nula ou estava vazia. Defina PROCDUMP_PATH para o caminho da pasta que contém o executável procdump apropriado. - - + Collect dump was enabled but no dump file was generated. A coleta de despejo estava habilitada, mas não foi gerado nenhum arquivo de despejo. - - + The blame parameter key specified {0} is not valid. Ignoring this key. A chave de parâmetro de blame especificada {0} é inválida. Ignorando esta chave. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. A chave de parâmetro de blame {0} oferece suporte apenas aos valores {1}/{2}. Ignorando esta chave. - - + Could not start process dump: {0} Não foi possível iniciar o processo de despejo: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump foi habilitado, mas o arquivo de despejo não foi gerado. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Esse teste pode ser a origem da falha ou não. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Valor inesperado '{0}' fornecido como tempo limite. Forneça um valor neste formato: 1.5h/90m/5400s/5400000ms/5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Esse teste pode ser a origem da falha ou não. Dumping this process tree (from bottom) Despejando esta árvore de processos (da parte inferior) - - + minutes minutos - - + seconds segundos - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ru.xlf index a94788a81c..174393655e 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.ru.xlf @@ -16,38 +16,32 @@ This test may, or may not be the source of the crash. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. Требуемая переменная среды PROCDUMP_PATH была пустой или имела значение NULL. Задайте для PROCDUMP_PATH путь к папке, содержащей нужный исполняемый файл procdump. - - + Collect dump was enabled but no dump file was generated. Сбор дампа включен, но файл дампа не создан. - - + The blame parameter key specified {0} is not valid. Ignoring this key. Указанный ключ {0} параметра Blame недопустим. Он будет пропущен. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. Ключ {0} параметра Blame поддерживает только значения {1}/{2}. Он будет пропущен. - - + Could not start process dump: {0} Не удалось запустить дамп процесса: {0} - - + CollectDump was enabled but dump file was not generated. Параметр CollectDump включен, но файл дампа не был создан. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ This test may, or may not be the source of the crash. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 В качестве времени ожидания указано непредвиденное значение "{0}". Укажите значение в следующем формате: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ This test may, or may not be the source of the crash. Dumping this process tree (from bottom) Создание дампа для этого дерева процессов (из нижней части) - - + minutes мин - - + seconds с - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.tr.xlf index e8dfcbabb3..96e906da89 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.tr.xlf @@ -16,38 +16,32 @@ Bu test, kilitlenmenin kaynağı olmayabilir veya olmayabilir. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. Gerekli ortam değişkeni PROCDUMP_PATH null veya boştu. PROCDUMP_PATH değişkenini uygun yürütülebilir procdump içeren klasörün yoluna ayarlayın. - - + Collect dump was enabled but no dump file was generated. Döküm toplama etkindi, ancak hiçbir döküm dosyası oluşturulmamıştı. - - + The blame parameter key specified {0} is not valid. Ignoring this key. Belirtilen blame parametresi anahtarı {0} geçerli değil. Bu anahtar yoksayılıyor. - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. Belirtilen blame parametresi anahtarı {0} yalnızca {1}/{2} değerlerini destekleyebilir. Bu anahtar yoksayılıyor. - - + Could not start process dump: {0} İşlem dökümü başlatılamadı: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump etkindi, ancak döküm dosyası oluşturulmamıştı. - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ Bu test, kilitlenmenin kaynağı olmayabilir veya olmayabilir. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 Zaman aşımı olarak beklenmeyen '{0}' değeri sağlandı. Lütfen şu biçimde bir değer girin: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ Bu test, kilitlenmenin kaynağı olmayabilir veya olmayabilir. Dumping this process tree (from bottom) Bu işlem ağacının dökümü alınıyor (alttan) - - + minutes dakika - - + seconds saniye - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hans.xlf index 87fe3008da..c3ea2af6ad 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hans.xlf @@ -16,38 +16,32 @@ This test may, or may not be the source of the crash. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. 所需环境变量 PROCDUMP_PATH 为空。请将 PROCDUMP_PATH 设为包含适当的可执行进程转储的文件夹路径。 - - + Collect dump was enabled but no dump file was generated. 收集转储已启用，但是未生成转储文件。 - - + The blame parameter key specified {0} is not valid. Ignoring this key. 指定的追责参数键 {0} 无效。忽略此键。 - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. 追责参数键 {0} 只支持值 {1}/{2}。忽略此键。 - - + Could not start process dump: {0} 无法启动进程转储: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump 已启用，但是未生成转储文件。 - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ This test may, or may not be the source of the crash. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 提供了意外的值“{0}”作为超时。请按以下格式提供值: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ This test may, or may not be the source of the crash. Dumping this process tree (from bottom) 正在转储此进程树(从底部) - - + minutes 分钟 - - + seconds 秒 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hant.xlf index e09835d757..491532f393 100644 --- a/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Extensions.BlameDataCollector/Resources/xlf/Resources.zh-Hant.xlf @@ -16,38 +16,32 @@ This test may, or may not be the source of the crash. Required environment variable PROCDUMP_PATH was null or empty. Set PROCDUMP_PATH to path of folder containing appropriate procdump executable. 必要的環境變數 PROCDUMP_PATH 為 null 或是空的。請將 PROCDUMP_PATH 設定為包含適當之 procdump 可執行檔之資料夾的路徑。 - - + Collect dump was enabled but no dump file was generated. 已啟用了收集傾印，但未產生任何傾印檔。 - - + The blame parameter key specified {0} is not valid. Ignoring this key. 指定的 blame 參數索引鍵 {0} 無效。即將忽略此索引鍵。 - - + The blame parameter key {0} can only support values {1}/{2}. Ignoring this key. blame 參數索引鍵 {0} 僅支援值 {1}/{2}。即將忽略此索引鍵。 - - + Could not start process dump: {0} 無法啟動處理序傾印: {0} - - + CollectDump was enabled but dump file was not generated. CollectDump 已啟用，但未產生傾印檔案。 - - + The specified inactivity time of {0} {1} has elapsed. Collecting hang dumps from testhost and its child processes @@ -57,8 +51,7 @@ This test may, or may not be the source of the crash. Unexpected value '{0}' provided as timeout. Please provide a value in this format: 1.5h / 90m / 5400s / 5400000ms / 5400000 提供了非預期的值 '{0}' 作為逾時。請提供以下格式的值: 1.5h / 90m / 5400s / 5400000ms / 5400000 - - + All tests finished running, Sequence file will not be generated @@ -73,20 +66,17 @@ This test may, or may not be the source of the crash. Dumping this process tree (from bottom) 正在傾印此處理序樹狀結構 (從底部) - - + minutes 分鐘 - - + seconds 秒 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.cs.xlf index a6653a4d4a..797ee003e0 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.cs.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Soubor HTML s výsledky testů: {0} - - + Html Logger Error : {0} Chyba protokolovače HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Parametry LogFileName a LogFilePrefix nelze uvést společně. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.de.xlf index 4dd9909802..0036fb22b0 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.de.xlf @@ -5,20 +5,17 @@ Html test results file : {0} HTML-Testergebnisdatei: {0} - - + Html Logger Error : {0} HTML-Protokollierungsfehler: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Die Parameter "LogFileName" und "LogFilePrefix" können nicht zusammen angegeben werden. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.es.xlf index 5f99510172..8db3c86978 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.es.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Archivo de resultados de pruebas HTML: {0} - - + Html Logger Error : {0} Error del registrador HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Los parámetros LogFileName y LogFilePrefix no se pueden proporcionar juntos. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.fr.xlf index a0ae84c39c..5139854891 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.fr.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Fichier de résultats des tests HTML : {0} - - + Html Logger Error : {0} Erreur de l'enregistreur d'événements HTML : {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Les paramètres LogFileName et LogFilePrefix ne peuvent pas être donnés ensemble. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.it.xlf index 59cac2106c..56e5a0fd34 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.it.xlf @@ -5,20 +5,17 @@ Html test results file : {0} File di risultati del test HTML: {0} - - + Html Logger Error : {0} Errore del logger HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Non è possibile specificare insieme i parametri LogFileName e LogFilePrefix. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ja.xlf index 7735fa745f..91d9b72ac7 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ja.xlf @@ -5,20 +5,17 @@ Html test results file : {0} HTML テスト結果ファイル: {0} - - + Html Logger Error : {0} HTML ロガー エラー: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. パラメーター LogFileName と LogFilePrefix を同時に指定することはできません。 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ko.xlf index 6d7191d791..fd2d309453 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ko.xlf @@ -5,20 +5,17 @@ Html test results file : {0} HTML 테스트 결과 파일: {0} - - + Html Logger Error : {0} HTML 로거 오류: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. LogFileName 및 LogFilePrefix 매개 변수는 함께 제공할 수 없습니다. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pl.xlf index 37d44aebe1..73d37a49e0 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pl.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Plik wyników testu HTML: {0} - - + Html Logger Error : {0} Błąd rejestratora HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Parametry LogFileName i LogFilePrefix nie mogą być podawane razem. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pt-BR.xlf index da5b0064f7..aea6458fbc 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.pt-BR.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Arquivo de resultados de teste HTML: {0} - - + Html Logger Error : {0} Erro do Agente de HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Os parâmetros LogFileName e LogFilePrefix não podem ser usados juntos. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ru.xlf index 862fe76aa9..a436d171f3 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.ru.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Файл результатов теста HTML: {0} - - + Html Logger Error : {0} Ошибка в средстве ведения журнала HTML: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. Параметры LogFileName и LogFilePrefix не могут использоваться вместе. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.tr.xlf index 1d81ea328c..864e4a78cd 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.tr.xlf @@ -5,20 +5,17 @@ Html test results file : {0} HTML test sonuçları dosyası: {0} - - + Html Logger Error : {0} HTML Günlükçü Hatası: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. LogFileName ve LogFilePrefix parametreleri birlikte kullanılamaz. - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hans.xlf index aead595cba..d1de0ea107 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hans.xlf @@ -5,20 +5,17 @@ Html test results file : {0} HTML 测试结果文件: {0} - - + Html Logger Error : {0} HTML 记录器错误: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. 参数 LogFileName 和 LogFilePrefix 不能一起使用。 - - + diff --git a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hant.xlf index 3f5b12511a..e3c03e3c9b 100644 --- a/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Extensions.HtmlLogger/Resources/xlf/Resources.zh-Hant.xlf @@ -5,20 +5,17 @@ Html test results file : {0} Html 測試結果檔案: {0} - - + Html Logger Error : {0} Html 記錄器錯誤: {0} - - + The parameters LogFileName and LogFilePrefix cannot be given together. 不能同時指定參數 LogFileName 和 LogFilePrefix。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.cs.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.cs.xlf index 8dc584c74f..5e6f6bda56 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.cs.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.cs.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Parametr nemůže být null nebo prázdný. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + Otestujte zjištěné knihovny DLL, které se vytvořily pro různé verze architektury a platformy. Následující knihovny DLL neodpovídají aktuálnímu nastavení, tedy architektuře {0} a platformě {1}.{2}Další podrobnosti o správě těchto nastavení najdete v {3}. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Žádný s poskytnutých kontejnerů testů neodpovídá nastavení architektury platformy a rozhraní .NET Framework pro testovací běh. Platforma: {0} .NET Framework: {1}. Další podrobnosti o správě těchto nastavení najdete na adrese http://go.microsoft.com/fwlink/?LinkID=330428. Settings file provided does not conform to required format. Zadaný soubor nastavení neodpovídá požadovanému formátu. - - + {0} is built for Framework {1} and Platform {2}. Produkt {0} je sestaven pro rozhraní {1} a platformu {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.de.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.de.xlf index c7c6499a48..0904b4e6a4 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.de.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.de.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Der Parameter darf nicht NULL oder leer sein. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + Beim Testlauf wurden DLLs erkannt, die für verschiedene Framework- und Plattformversionen erstellt wurden. Die folgenden DLLs entsprechen nicht den aktuellen Einstellungen: Framework {0} und Plattform {1}.{2}Wechseln Sie zu {3}, um weitere Informationen zum Verwalten dieser Einstellungen zu erhalten. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Keiner der angegebenen Testcontainer stimmt mit der Plattformarchitektur und den .NET Framework-Einstellungen für den Testlauf überein. Plattform: {0}, .NET Framework: {1}. Navigieren Sie zu http://go.microsoft.com/fwlink/?LinkID=330428, um weitere Informationen zum Verwalten dieser Einstellungen zu erhalten. Settings file provided does not conform to required format. Die angegebene Einstellungsdatei entspricht nicht dem erforderlichen Format. - - + {0} is built for Framework {1} and Platform {2}. "{0}" wurde für das Framework {1} und die Plattform {2} erstellt. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.es.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.es.xlf index e3ec47906c..ea9dd037da 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.es.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.es.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + El parámetro no puede ser nulo ni estar vacío. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + La serie de pruebas detectó archivos DLL que se compilaron para diferentes versiones de marco de trabajo y plataforma. Los siguientes archivos DLL no coinciden con la configuración actual, que es el marco de trabajo {0} y la plataforma {1}. {2}Vaya a {3} para obtener más información sobre cómo administrar esta configuración. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Ninguno de los contenedores de prueba proporcionados coincide con la configuración de arquitectura de plataforma y .Net Framework de la serie de pruebas. Plataforma: {0}, .Net Framework: {1}. Vaya a http://go.microsoft.com/fwlink/?LinkID=330428 para obtener más información sobre cómo administrar esta configuración. Settings file provided does not conform to required format. El archivo de configuración proporcionado no tiene el formato requerido. - - + {0} is built for Framework {1} and Platform {2}. {0} se ha compilado para el marco {1} y la plataforma {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.fr.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.fr.xlf index 79b01267b0..0c9b75f180 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.fr.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.fr.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Le paramètre ne peut pas avoir une valeur null ou être vide. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + La série de tests a détecté une ou plusieurs DLL qui ont été générées pour d'autres versions de framework et de plateforme. La ou les DLL suivantes ne correspondent pas aux paramètres actuels : framework {0} et plateforme {1}.{2}Accédez à {3} pour plus d'informations sur la gestion de ces paramètres. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Aucun des conteneurs de tests fournis ne correspond aux paramètres d'architecture de la plateforme et du .Net Framework pour la série de tests. Plateforme : {0} .Net Framework : {1}. Accédez à http://go.microsoft.com/fwlink/?LinkID=330428 pour plus de détails sur la gestion de ces paramètres. Settings file provided does not conform to required format. Le fichier de paramètres fourni n'est pas conforme au format requis. - - + {0} is built for Framework {1} and Platform {2}. {0} est généré pour le framework {1} et la plateforme {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.it.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.it.xlf index 162dca2a4d..cde112bdb8 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.it.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.it.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Il parametro non può essere vuoto o Null. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + L'esecuzione dei test ha rilevato DLL compilate per versioni diverse del framework e della piattaforma. Le DLL seguenti non corrispondono alle impostazioni correnti, ovvero al framework {0} e alla piattaforma {1}.{2}Per altri dettagli sulla gestione di queste impostazioni, vedere {3}. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Nessuno dei contenitori di test specificati corrisponde alle impostazioni di architettura della piattaforma e .NET Framework per l'esecuzione dei test. Piattaforma: {0} .NET Framework: {1}. Per altre informazioni sulla gestione di tali impostazioni, visitare http://go.microsoft.com/fwlink/?LinkID=330428 Settings file provided does not conform to required format. Il file di impostazioni specificato non è conforme al formato richiesto. - - + {0} is built for Framework {1} and Platform {2}. {0} viene compilato per il framework {1} e la piattaforma {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ja.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ja.xlf index e4e3140e15..5e8f037b7a 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ja.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ja.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + パラメーターを null または空にすることはできません。 Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + テストの実行で、別のフレームワークとプラットフォームのバージョン用にビルドされた DLL が検出されました。以下の DLL は、現在の設定と一致しません。現在のフレームワーク: {0}、プラットフォーム: {1}。{2}これらの設定を管理することについて詳しくは、{3} にアクセスしてください。 None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + 提供されたどのテスト コンテナーも、テスト実行のプラットフォーム アーキテクチャおよび .NET Framework 設定に一致しません。プラットフォーム: {0}、.NET Framework: {1}。これらの設定の管理方法の詳細については、http://go.microsoft.com/fwlink/?LinkID=330428 にアクセスしてください。 Settings file provided does not conform to required format. 指定された設定ファイルは、必要な形式に準拠していません。 - - + {0} is built for Framework {1} and Platform {2}. {0} はフレームワーク {1} およびプラットフォーム {2} 向けにビルドされます。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ko.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ko.xlf index 897ba1f693..ee4b96f092 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ko.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ko.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + 매개 변수는 null이거나 비워 둘 수 없습니다. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + 테스트 실행에서 다른 프레임워크 및 플랫폼 버전용으로 빌드된 DLL을 감지했습니다. 다음 DLL은 현재 설정({0} 프레임워크 및 {1} 플랫폼)과 일치하지 않습니다.{2}이 설정을 관리하는 방법에 대한 자세한 내용을 보려면 {3}(으)로 이동하세요. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + 제공된 테스트 컨테이너 중에 테스트 실행을 위한 플랫폼 아키텍처 및 .NET Framework 설정과 일치하는 것이 없습니다. 플랫폼: {0}, .NET Framework: {1}. 이러한 설정의 관리에 대한 자세한 내용은 http://go.microsoft.com/fwlink/?LinkID=330428을 참조하세요. Settings file provided does not conform to required format. 제공된 설정 파일이 필요한 형식에 맞지 않습니다. - - + {0} is built for Framework {1} and Platform {2}. {0}은(는) 프레임워크 {1} 및 플랫폼 {2}을(를) 대상으로 빌드됩니다. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pl.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pl.xlf index b14586561e..e4e0d81fb4 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pl.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pl.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Parametr nie może mieć wartości null ani być pusty. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + Przebieg testowy wykrył biblioteki DLL utworzone dla innych wersji struktury i platformy. Następujące biblioteki DLL są niezgodne z bieżącymi ustawieniami (określającymi strukturę {0} i platformę {1}).{2}Aby uzyskać więcej informacji o zarządzaniu tymi ustawieniami, przejdź do: {3}. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Żaden z dostarczonych kontenerów testów nie odpowiada architekturze platformy i ustawieniom programu .NET Framework dotyczącym przebiegu testu. Platforma: {0}. Program .NET Framework: {1}. Aby uzyskać więcej informacji na temat zarządzania tymi ustawieniami, przejdź do strony http://go.microsoft.com/fwlink/?LinkID=330428. Settings file provided does not conform to required format. Podany plik ustawień nie jest zgodny z wymaganym formatem. - - + {0} is built for Framework {1} and Platform {2}. Element {0} został skompilowany dla struktury {1} i platformy {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pt-BR.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pt-BR.xlf index ca4510c6ae..d36d02f785 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.pt-BR.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + O parâmetro não pode ser nulo ou estar vazio. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + A execução de teste detectou DLLs que foram criadas para diferentes versões de estrutura e de plataforma. As DLLs a seguir não correspondem às configurações atuais, que são a estrutura {0} e a plataforma {1}.{2}Acesse {3} para obter mais detalhes sobre o gerenciamento dessas configurações. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Nenhum dos contêineres de teste fornecidos corresponde às configurações da Arquitetura da Plataforma e do .Net Framework para a execução de teste. Plataforma: {0} .Net Framework: {1}. Acesse http://go.microsoft.com/fwlink/?LinkID=330428 para obter mais detalhes sobre como gerenciar essas configurações. Settings file provided does not conform to required format. O arquivo de configurações fornecido não está em conformidade com o formato exigido. - - + {0} is built for Framework {1} and Platform {2}. {0} é compilado para Framework {1} e Platform {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ru.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ru.xlf index 4058fb4d73..10fda594fd 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ru.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.ru.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Параметр не может быть пустым или иметь значение null. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + Тестовый запуск обнаружил библиотеки DLL, которые были созданы для различных версий инфраструктуры и платформы. Следующие библиотеки DLL не соответствуют текущим параметрам (инфраструктура {0} и платформа {1}).{2}Перейдите по ссылке {3} для получения дополнительных сведений об управлении этими параметрами. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Ни один из предоставленных контейнеров тестов не соответствует архитектуре платформы и параметрам .NET Framework для тестового запуска. Платформа: {0} .NET Framework: {1}. Дополнительные сведения об управлении этими параметрами см. по адресу http://go.microsoft.com/fwlink/?LinkID=330428. Settings file provided does not conform to required format. Указанный файл параметров не соответствует требуемому формату. - - + {0} is built for Framework {1} and Platform {2}. {0} создается для программной платформы {1} и аппаратной платформы {2}. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.tr.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.tr.xlf index 9e59a96e84..d8243a5dff 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.tr.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.tr.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + Parametre null veya boş olamaz. Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + Test çalıştırması, farklı çerçeve ve platform sürümleri için oluşturulmuş DLL'ler buldu. Aşağıdaki DLL'ler, {0} çerçevesi ve {1} platformu olan geçerli ayarlarla eşleşmiyor. {2}Bu ayarları yönetme hakkında daha fazla ayrıntı için {3} bölümüne gidin. None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + Belirtilen test kapsayıcılarının hiçbiri test çalıştırmasına ait Platform Mimarisi ve .NET Framework ayarlarıyla eşleşmiyor. Platform: {0} .NET Framework: {1}. Bu ayarları yönetmeye ilişkin ayrıntılar için bkz. http://go.microsoft.com/fwlink/?LinkID=330428. Settings file provided does not conform to required format. Belirtilen ayarlar dosyası, gerekli biçime uymuyor. - - + {0} is built for Framework {1} and Platform {2}. {0}, {1} Çerçevesi ve {2} Platformu için derlenmiştir. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hans.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hans.xlf index 37276113b7..91aa3fa748 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hans.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + 参数不能为 NULL 或为空。 Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + 测试运行检测到为不同框架和平台版本构建的 DLL。后面的 DLL 与当前设置(即 {0} 框架和 {1} 平台)不匹配。{2}如需了解如何管理这些设置，请转到 {3}。 None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + 提供的所有测试容器均与用于测试运行的平台体系结构和 .Net Framework 设置不匹配。平台: {0}。.Net Framework: {1}。有关管理这些设置的详细信息，请转到http://go.microsoft.com/fwlink/?LinkID=330428。 Settings file provided does not conform to required format. 提供的设置文件不符合格式要求。 - - + {0} is built for Framework {1} and Platform {2}. {0} 适用于 {1} 框架和 {2} 平台。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hant.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hant.xlf index 7fe5c8ebec..faa0382b32 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/CommonResources.zh-Hant.xlf @@ -4,33 +4,28 @@ The parameter cannot be null or empty. - - + 參數不可為 null 或空白。 Test run detected DLL(s) which were built for different framework and platform versions. Following DLL(s) do not match current settings, which are {0} framework and {1} platform.{2}Go to {3} for more details on managing these settings. - - + 測試回合偵測到為不同架構和平台版本所建置的 DLL。下列 DLL 與目前的設定不相符，亦即 {0} 架構及 {1} 平台。{2}如需管理這些設定的詳細資料，請前往 {3}。 None of the provided test containers match the Platform Architecture and .Net Framework settings for the test run. Platform: {0} .Net Framework: {1}. Go to http://go.microsoft.com/fwlink/?LinkID=330428 for more details on managing these settings. - - + 提供的測試容器全都不符合測試回合的平台架構與 .Net Framework 設定。平台: {0} .Net Framework: {1}。如需如何管理這些設定的詳細資料，請前往 http://go.microsoft.com/fwlink/?LinkID=330428。 Settings file provided does not conform to required format. 提供的設定檔案不符合所需的格式。 - - + {0} is built for Framework {1} and Platform {2}. {0} 專為架構 {1} 及平台 {2} 建置。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.cs.xlf index 2d048a5528..1976fdb514 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.cs.xlf @@ -9,8 +9,7 @@ None - - + Žádné @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Zprávy testů: {0} Message: {0} - - + Zpráva: {0} StackTrace: {0} - - + Trasování zásobníku: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Vlastnost {0} nejde zaregistrovat jako typ hodnoty {1}, protože už je zaregistrovaná jako {2}. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + Nejde najít TypeConverter pro typ {0}. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Neplatné nastavení {0}. Neočekávaný XmlAttribute: {1} Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Neplatné nastavení {0}. Neočekávaný XmlElement: {1} Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Neplatné nastavení kolekce dat. Očekávaný atribut '{0}' nebyl nalezen. Typické nastavení kolekce dat by mělo vypadat přibližně následovně <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Neplatné nastavení {0}. Pro {2} se zadala neplatná hodnota {1}. The root node of the run settings must be named 'RunSettings'. - - + Kořenový uzel parametrů spouštění se musí jmenovat RunSettings. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + TestCaseFilter se nedá zadat pro konkrétní běh testů. Parametr FilterCriteria je určený jenom pro běhy se zdroji. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Typ vlastnosti testu {0} vlastnosti {1} se nepodporuje. Použijte jeden z podporovaných typů vlastností (primitivní typy, identifikátor URI, řetězec, string[]) a zkuste to znovu. @@ -222,8 +205,7 @@ FullyQualifiedName - - + PlněKvalifikovanýNázev @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + Adresář řešení {0} neexistuje. Ujistěte se prosím, že adresář řešení zadaný v nastavení Runsettings existuje a že máte oprávnění ho číst. The parameter cannot be null or empty. - - + Parametr nemůže být null nebo prázdný. File {0} does not exist. - - + Soubor {0} neexistuje. Object must be of type {0}. - - + Objekt musí být typu {0}. Aborted - - + Přerušené Completed - - + Dokončené Disconnected - - + Odpojené Error - - + Chyba Failed - - + Neúspěšné Inconclusive - - + Neprůkazné In Progress - - + Probíhá Not Executed - - + Neprovedené Not Runnable - - + Nejde spustit Passed - - + Úspěšné Passed (run aborted) - - + Úspěšné (běh se přerušil) Pending - - + Čekající Timeout - - + Časový limit Warning - - + Upozornění Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Z poskytnutého streamu nejde číst. Pokud stream nepodporuje čtení, jeho data nejde poslat. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Zadaný název souboru {0} obsahuje tyto neplatné znaky: {1} The provided file name '{0}' is reserved. - - + Zadaný název souboru {0} je rezervovaný. Failed to Create msdia Session COM HResult '{0}'. Nepovedlo se vytvořit model COM pro relaci msdia. HResult: {0} - - + Failed to load msdia Nepovedlo se načíst knihovnu msdia - - + Invalid URI in data collector settings '{0}'. Neplatný identifikátor URI v nastavení {0} kolekce dat - - + Invalid URI '{0}' in settings '{1}'. Neplatný identifikátor URI {0} v nastavení {1} - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Neplatné nastavení {0}. Očekával se alespoň jeden XmlAttribute: popisný název (friendlyName), identifikátor URI (uri) nebo kvalifikovaný název sestavení (assemblyQualifiedName). - - + Filter string '{0}' includes unrecognized escape sequence. Řetězec filtru {0} zahrnuje nerozpoznanou řídicí sekvenci. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.de.xlf index 587f14980d..8308ca4528 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.de.xlf @@ -9,8 +9,7 @@ None - - + Keine @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Testmeldungen: {0} Message: {0} - - + Meldung: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (NULL) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Die Eigenschaft "{0}" kann nicht als Werttyp "{1}" registriert werden, weil sie bereits als "{2}" registriert wurde. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + TypeConverter für den Typ "{0}" wurde nicht gefunden. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Ungültige Einstellungen "{0}". Unerwartetes XmlAttribute: "{1}". Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Ungültige Einstellungen "{0}". Unerwartetes XmlElement: "{1}". Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Ungültige Datensammlereinstellungen. Das erwartete Attribut '{0}' fehlt. Eine typische Datensammlereinstellung hat das folgende Format: <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Ungültige Einstellung "{0}". Es wurde ein ungültiger Wert "{1}" für "{2}" angegeben. The root node of the run settings must be named 'RunSettings'. - - + Der Stammknoten der Laufzeiteinstellungen muss "RunSettings" heißen. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + TestCaseFilter kann nicht für einen bestimmten Testlauf angegeben werden. FilterCriteria gilt nur für Ausführungen mit Quellen. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Der Testeigenschaftentyp "{0}" der Eigenschaft "{1}" wird nicht unterstützt. Verwenden Sie einen der unterstützten Eigenschaftentypen (primitive Typen, uri, string, string[]), und versuchen Sie es erneut. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + Das Projektmappenverzeichnis "{0}" ist nicht vorhanden. Stellen Sie sicher, dass das in "runsettings" angegebene Projektmappenverzeichnis vorhanden ist und über Leseberechtigungen für das Verzeichnis verfügt. The parameter cannot be null or empty. - - + Der Parameter darf nicht NULL oder leer sein. File {0} does not exist. - - + Die Datei "{0}" ist nicht vorhanden. Object must be of type {0}. - - + Das Objekt muss vom Typ {0} sein. Aborted - - + Abgebrochen Completed - - + Abgeschlossen Disconnected - - + Getrennt Error - - + Fehler Failed - - + Fehler Inconclusive - - + Nicht eindeutig In Progress - - + In Bearbeitung Not Executed - - + Nicht ausgeführt Not Runnable - - + Nicht ausführbar Passed - - + Bestanden Passed (run aborted) - - + Bestanden (Ausführung abgebrochen) Pending - - + Ausstehend Timeout - - + Timeout Warning - - + Warnung Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Aus dem bereitgestellten Datenstrom kann nicht gelesen werden. Daten aus einem Datenstrom können nur gesendet werden, wenn der Datenstrom Lesevorgänge unterstützt. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Der angegebene Dateiname "{0}" enthält die folgenden ungültigen Zeichen: "{1}". The provided file name '{0}' is reserved. - - + Der angegebene Dateiname "{0}" ist reserviert. Failed to Create msdia Session COM HResult '{0}'. Fehler beim Erstellen von MSDIA-Sitzung. COM-HRESULT "{0}". - - + Failed to load msdia Fehler beim Laden von MSDIA. - - + Invalid URI in data collector settings '{0}'. Ungültiger URI in Datensammlereinstellungen "{0}". - - + Invalid URI '{0}' in settings '{1}'. Ungültiger URI "{0}" in den Einstellungen "{1}". - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Ungültige Einstellungen "{0}". Erwartet wird mindestens ein XmlAttribute: "friendlyName", "uri" oder "assemblyQualifiedName". - - + Filter string '{0}' includes unrecognized escape sequence. Die Filterzeichenfolge "{0}" umfasst eine nicht erkannte Escapesequenz. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.es.xlf index 33c19d4e42..22bc2f8f0d 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.es.xlf @@ -9,8 +9,7 @@ None - - + Ninguna @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Mensajes de prueba: {0} Message: {0} - - + Mensaje: {0} StackTrace: {0} - - + Seguimiento de la pila: {0} (null) - - + (nulo) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + No se puede registrar la propiedad '{0}' como tipo de valor '{1}' porque ya se registró como '{2}'. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + No se encuentra TypeConverter para el tipo {0}. @@ -154,26 +145,22 @@ Id - - + Id. Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Configuración no válida: '{0}'. Atributo XML no esperado: '{1}'. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Configuración no válida: '{0}'. Elemento XML no esperado: '{1}'. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + La configuración del recolector de datos no es válida. Falta el atributo esperado '{0}'. Una configuración de colector de datos típica debería ser similar a <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Configuración no válida: '{0}'. Se ha especificado un valor no válido ('{1}') para '{2}'. The root node of the run settings must be named 'RunSettings'. - - + El nodo raíz de los parámetros de ejecución debe denominarse 'RunSettings'. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + No se puede especificar TestCaseFilter para series de pruebas específicas. FilterCriteria se usa solo para ejecuciones con orígenes. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + No se admite el tipo '{0}' de la propiedad de prueba '{1}'. Use un tipo de propiedad admitido (tipos primitivos, URI, string, string[]) y vuelva a intentarlo. @@ -222,8 +205,7 @@ FullyQualifiedName - - + Nombre completo @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + El directorio de solución '{0}' no existe. Asegúrese de que el directorio de solución especificado en Runsettings existe y de que tiene permisos de lectura para el directorio. The parameter cannot be null or empty. - - + El parámetro no puede ser nulo ni estar vacío. File {0} does not exist. - - + El archivo {0} no existe. Object must be of type {0}. - - + El objeto debe ser de tipo {0}. Aborted - - + Anuladas Completed - - + Finalizadas Disconnected - - + Desconectadas Error - - + Error Failed - - + Con error Inconclusive - - + No concluyentes In Progress - - + En curso Not Executed - - + No ejecutadas Not Runnable - - + No ejecutables Passed - - + Correctas Passed (run aborted) - - + Correctas (ejecución anulada) Pending - - + Pendientes Timeout - - + Tiempo de espera agotado Warning - - + Advertencia Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + No se puede leer el flujo proporcionado. Los datos de un flujo no se pueden enviar si el flujo no admite lectura. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + El nombre de archivo proporcionado ({0}) contiene los siguientes caracteres no válidos: '{1}'. The provided file name '{0}' is reserved. - - + El nombre de archivo proporcionado ({0}) es un nombre reservado. Failed to Create msdia Session COM HResult '{0}'. No se pudo crear msdia Session COM HResult "{0}". - - + Failed to load msdia No se pudo cargar msdia - - + Invalid URI in data collector settings '{0}'. URI no válido en la configuración del recopilador de datos "{0}". - - + Invalid URI '{0}' in settings '{1}'. URI "{0}" no válido en la configuración "{1}". - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Configuración "{0}" no válida. Se esperaba al menos uno de los siguientes valores de XmlAttribute: friendlyName, uri y assemblyQualifiedName. - - + Filter string '{0}' includes unrecognized escape sequence. La cadena de filtro "{0}" incluye una secuencia de escape no reconocida. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.fr.xlf index 8101e99b64..b25476ad1d 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.fr.xlf @@ -9,8 +9,7 @@ None - - + Aucun @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0} : {1} Test Messages: {0} - - + Messages de test : {0} Message: {0} - - + Message : {0} StackTrace: {0} - - + StackTrace : {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Impossible d'inscrire la propriété '{0}' en tant que type valeur '{1}', car elle est déjà inscrite en tant que '{2}'. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + TypeConverter introuvable pour le type {0}. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Paramètres non valides '{0}'. XmlAttribute inattendu : '{1}'. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Paramètres non valides '{0}'. XmlElement inattendu : '{1}'. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Paramètres de collecteur de données non valides. Attribut attendu '{0}' manquant. Un paramétrage de collecteur de données classique se présente comme suit : <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Paramètres non valides '{0}'. Valeur non valide '{1}' spécifiée pour '{2}'. The root node of the run settings must be named 'RunSettings'. - - + Le nœud racine des paramètres d'exécution doit être nommé 'RunSettings'. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Impossible de spécifier TestCaseFilter pour l'exécution de tests spécifiques. FilterCriteria est destiné uniquement à l'exécution avec des sources. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Le type de propriété de test '{0}' de la propriété '{1}' n'est pas pris en charge. Utilisez l'un des types de propriété pris en charge (types primitifs, uri, string, string[]), puis réessayez. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + Le répertoire de solution '{0}' n'existe pas. Vérifiez que le répertoire de solution spécifié dans runsettings existe, et que vous disposez d'autorisations d'accès en lecture pour celui-ci. The parameter cannot be null or empty. - - + Le paramètre ne peut pas avoir une valeur null ou être vide. File {0} does not exist. - - + Le fichier {0} n'existe pas. Object must be of type {0}. - - + L'objet doit être de type {0}. Aborted - - + Abandonné Completed - - + Effectué Disconnected - - + Déconnecté Error - - + Erreur Failed - - + Échec Inconclusive - - + Non concluant In Progress - - + En cours Not Executed - - + Non exécuté Not Runnable - - + Non exécutable Passed - - + Réussite Passed (run aborted) - - + Réussi (exécution abandonnée) Pending - - + En attente Timeout - - + Délai d'expiration Warning - - + Avertissement Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Impossible de lire le flux fourni. Impossible d'envoyer les données d'un flux s'il ne prend pas en charge la lecture. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Le nom de fichier '{0}' fourni contient les caractères non valides suivants : '{1}'. The provided file name '{0}' is reserved. - - + Le nom de fichier '{0}' fourni est réservé. Failed to Create msdia Session COM HResult '{0}'. Échec de la création du HResult COM de la session msdia : '{0}'. - - + Failed to load msdia Échec du chargement de msdia - - + Invalid URI in data collector settings '{0}'. URI non valide dans les paramètres de collecteur de données '{0}'. - - + Invalid URI '{0}' in settings '{1}'. URI '{0}' non valide dans les paramètres '{1}'. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Paramètres '{0}' non valides. Au moins un des attributs XmlAttribute (friendlyName, uri ou assemblyQualifiedName) était attendu. - - + Filter string '{0}' includes unrecognized escape sequence. La chaîne de filtre '{0}' inclut une séquence d'échappement non reconnue. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.it.xlf index 663abeb056..376f7da07a 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.it.xlf @@ -9,8 +9,7 @@ None - - + Nessuno @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Messaggi di test: {0} Message: {0} - - + Messaggio: {0} StackTrace: {0} - - + Analisi dello stack: {0} (null) - - + (Null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Non è possibile registrare la proprietà '{0}' come tipo valore '{1}' perché è stata già registrata come '{2}'. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + Non è stato trovato alcun convertitore di tipo per il tipo {0}. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Le impostazioni '{0}' non sono valide. Elemento XmlAttribute imprevisto: '{1}'. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Le impostazioni '{0}' non sono valide. Elemento XmlElement imprevisto: '{1}'. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Impostazioni agente di raccolta dati non valide. Attributo previsto '{0}' mancante. Un'impostazione tipica dell'agente di raccolta dati è analoga alla seguente: <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Le impostazioni '{0}' non sono valide. È stato specificato un valore '{1}' non valido per '{2}'. The root node of the run settings must be named 'RunSettings'. - - + Al nodo radice delle impostazioni esecuzione test è necessario assegnare il nome 'RunSettings'. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Non è possibile specificare TestCaseFilter per la specifica esecuzione dei test. FilterCriteria è valido solo per l'esecuzione con origini. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Il tipo '{0}' della proprietà di test '{1}' non è supportato. Usare un tipo di proprietà supportato (tipi primitivi, uri, string, string[]) e riprovare. @@ -222,8 +205,7 @@ FullyQualifiedName - - + Nome completo @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + La directory '{0}' della soluzione non esiste. Assicurarsi che la directory della soluzione specificata in runsettings esista e che siano disponibili le autorizzazioni di lettura. The parameter cannot be null or empty. - - + Il parametro non può essere vuoto o Null. File {0} does not exist. - - + Il file {0} non esiste. Object must be of type {0}. - - + L'oggetto deve essere di tipo {0}. Aborted - - + Interrotto Completed - - + Completato Disconnected - - + Disconnesso Error - - + Errore Failed - - + Non superato Inconclusive - - + Senza risultati In Progress - - + In corso Not Executed - - + Non eseguito Not Runnable - - + Non eseguibile Passed - - + Superato Passed (run aborted) - - + Superato (esecuzione interrotta) Pending - - + In sospeso Timeout - - + Timeout Warning - - + Avviso Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Non è possibile leggere dal flusso specificato. I dati di un flusso non possono essere inviati se il flusso non supporta l'operazione di lettura. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Il nome file '{0}' specificato contiene i seguenti caratteri non validi: '{1}'. The provided file name '{0}' is reserved. - - + Il nome file '{0}' specificato è riservato. Failed to Create msdia Session COM HResult '{0}'. Non è stato possibile creare la sessione msdia. HResult COM: '{0}'. - - + Failed to load msdia Non è stato possibile caricare msdia - - + Invalid URI in data collector settings '{0}'. URI non valido nelle impostazioni '{0}' dell'agente di raccolta dati. - - + Invalid URI '{0}' in settings '{1}'. URI '{0}' non valido nelle impostazioni '{1}'. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Impostazioni '{0}' non valide. È previsto almeno un elemento XmlAttribute, tra friendlyName, uri e assemblyQualifiedName. - - + Filter string '{0}' includes unrecognized escape sequence. La stringa di filtro '{0}' include una sequenza di escape non riconosciuta. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ja.xlf index 1b4099aa74..bd660a2009 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ja.xlf @@ -9,8 +9,7 @@ None - - + なし @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + テスト メッセージ: {0} Message: {0} - - + メッセージ: {0} StackTrace: {0} - - + スタック トレース: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + プロパティ '{0}' は既に値の型 '{2}' として登録されていたため、'{1}' として登録できません。 @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + 型 {0} の TypeConverter が見つかりません。 @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + 設定 '{0}' は無効です。予期しない XmlAttribute: '{1}'。 Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + 設定 '{0}' は無効です。予期しない XmlElement: '{1}'。 Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + データ コレクターの設定が無効です。予期された属性 '{0}' が見つかりません。通常のデータ コレクターの設定は <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector"> のようになります。 @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + 無効な設定です: '{0}'。'{2}' に対して無効な値 '{1}' が指定されました。 The root node of the run settings must be named 'RunSettings'. - - + 実行設定のルート ノードには 'RunSettings' という名前を付ける必要があります。 Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + 特定のテストの実行には TestCaseFilter を指定できません。FilterCriteria は、ソースでの実行だけで使用できます。 The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + プロパティ '{1}' のテスト プロパティの型 '{0}' はサポートされていません。サポートされているプロパティの型 (プリミティブ型、URI、string、string[]) のいずれかを使用して、もう一度お試しください。 @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + ソリューション ディレクトリ '{0}' は存在しません。実行設定で指定したソリューション ディレクトリが存在することと、ディレクトリの読み取りアクセス許可があることをご確認ください。 The parameter cannot be null or empty. - - + パラメーターを null または空にすることはできません。 File {0} does not exist. - - + ファイル {0} は存在しません。 Object must be of type {0}. - - + オブジェクトは {0} 型でなければなりません。 Aborted - - + 中止 Completed - - + 完了 Disconnected - - + 切断 Error - - + エラー Failed - - + 失敗 Inconclusive - - + 結果不確定 In Progress - - + 処理中 Not Executed - - + 実行されませんでした Not Runnable - - + 実行できませんでした Passed - - + 成功 Passed (run aborted) - - + 成功 (中止された実行) Pending - - + 保留中 Timeout - - + タイムアウト Warning - - + 警告 Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + 指定されたストリームからデータを読み取ることができません。ストリームで読み取りがサポートされていない場合は、ストリームのデータを送信できません。 The provided file name '{0}' contains the following invalid characters: '{1}'. - - + 指定されたファイル名 '{0}' に次の無効な文字が含まれています: '{1}'。 The provided file name '{0}' is reserved. - - + 指定されたファイル名 '{0}' は、予約済みです。 Failed to Create msdia Session COM HResult '{0}'. msdia Session COM HResult '{0}' を作成できませんでした。 - - + Failed to load msdia msdia を読み込めませんでした - - + Invalid URI in data collector settings '{0}'. データ コレクター設定 '{0}' の URI は無効です。 - - + Invalid URI '{0}' in settings '{1}'. 設定 '{1}' の URI '{0}' は無効です。 - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. 設定 '{0}' は無効です。friendlyName、uri、assemblyQualifiedName のうち少なくとも一つの XmlAttribute が必要です。 - - + Filter string '{0}' includes unrecognized escape sequence. フィルター文字列 '{0}' には、認識されないエスケープ シーケンスが含まれています。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ko.xlf index 410c3934b8..bbd2c3ec0c 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ko.xlf @@ -9,8 +9,7 @@ None - - + 없음 @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + 테스트 메시지: {0} Message: {0} - - + 메시지: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + '{0}' 속성은 이미 '{2}'(으)로 등록되었으므로 '{1}' 값 형식으로 등록할 수 없습니다. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + {0} 형식에 대해 TypeConverter를 찾을 수 없습니다. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + '{0}' 설정이 잘못되었습니다. 예기치 않은 XmlAttribute '{1}'이(가) 있습니다. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + '{0}' 설정이 잘못되었습니다. 예기치 않은 XmlElement '{1}'이(가) 있습니다. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + 데이터 수집기 설정이 잘못되었습니다. 필요한 '{0}' 특성이 없습니다. 일반적인 데이터 수집기 설정은 <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">와 같습니다. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + '{0}' 설정이 잘못되었습니다. '{2}'에 대해 잘못된 값 '{1}'을(를) 지정했습니다. The root node of the run settings must be named 'RunSettings'. - - + 실행 설정의 루트 노드 이름은 'RunSettings'여야 합니다. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + 특정 테스트 실행에 대해 TestCaseFilter를 지정할 수 없습니다. FilterCriteria는 소스와 실행하기 위한 용도로만 사용됩니다. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + 속성 '{1}'의 테스트 속성 형식 '{0}'이(가) 지원되지 않습니다. 지원되는 속성 형식(기본 형식, URI, 문자열, string[]) 중 하나를 사용하고 다시 시도하세요. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + 솔루션 디렉터리 '{0}'이(가) 없습니다. runsettings에 지정된 솔루션 디렉터리가 존재하는지와 디렉터리에 대한 읽기 권한이 있는지 확인하세요. The parameter cannot be null or empty. - - + 매개 변수는 null이거나 비워 둘 수 없습니다. File {0} does not exist. - - + {0} 파일이 없습니다. Object must be of type {0}. - - + 개체는 {0} 형식이어야 합니다. Aborted - - + 중단됨 Completed - - + 완료됨 Disconnected - - + 연결 끊김 Error - - + 오류 Failed - - + 실패 Inconclusive - - + 결과 불충분 In Progress - - + 진행 중 Not Executed - - + 실행되지 않음 Not Runnable - - + 실행할 수 없음 Passed - - + 통과 Passed (run aborted) - - + 통과(실행이 중단됨) Pending - - + 보류 중 Timeout - - + 시간 초과 Warning - - + 경고 Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + 제공된 스트림에서 읽을 수 없습니다. 스트림에서 읽기를 지원하지 않으면 스트림의 데이터를 보낼 수 없습니다. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + 제공된 파일 이름 '{0}'에 다음과 같은 잘못된 문자가 들어 있습니다. '{1}'. The provided file name '{0}' is reserved. - - + 제공된 파일 이름 '{0}'이(가) 예약되어 있습니다. Failed to Create msdia Session COM HResult '{0}'. msdia 세션 COM HResult '{0}'을(를) 만들지 못했습니다. - - + Failed to load msdia msdia 로드 실패 - - + Invalid URI in data collector settings '{0}'. 데이터 수집기 설정 '{0}'의 URI가 잘못되었습니다. - - + Invalid URI '{0}' in settings '{1}'. '{1}' 설정의 '{0}' URI가 잘못되었습니다. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. '{0}' 설정이 잘못되었습니다. friendlyName, URI 및 assemblyQualifiedName 중 하나 이상의 XmlAttribute가 필요합니다. - - + Filter string '{0}' includes unrecognized escape sequence. 필터 문자열 '{0}'에 인식할 수 없는 이스케이프 시퀀스가 포함되어 있습니다. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pl.xlf index f47136662c..7502541035 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pl.xlf @@ -9,8 +9,7 @@ None - - + Brak @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Komunikaty testowe: {0} Message: {0} - - + Komunikat: {0} StackTrace: {0} - - + Ślad stosu: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Nie można zarejestrować właściwości „{0}” jako typu wartości „{1}”, ponieważ została już ona zarejestrowana jako „{2}”. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + Nie można odnaleźć elementu TypeConverter dla typu {0}. @@ -154,26 +145,22 @@ Id - - + Identyfikator Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Nieprawidłowe ustawienia „{0}”. Nieoczekiwany atrybut XmlAttribute: „{1}”. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Nieprawidłowe ustawienia „{0}”. Nieoczekiwany atrybut XmlElement: „{1}”. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Nieprawidłowe ustawienia modułów zbierających dane. Brak oczekiwanego atrybutu „{0}”. Typowe ustawienia modułu zbierającego dane typowe mają postać <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Nieprawidłowe ustawienia „{0}”. Nieprawidłowa wartość „{1}” określona dla elementu „{2}”. The root node of the run settings must be named 'RunSettings'. - - + Węzeł główny ustawień uruchamiania musi mieć nazwę „RunSettings”. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Nie można określić elementu TestCaseFilter dla określonego przebiegu testów. Element FilterCriteria jest przeznaczony tylko dla przebiegu ze źródłami. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Typ „{0}” właściwości testu „{1}” nie jest obsługiwany. Użyj jednego z obsługiwanych typów właściwości (typy pierwotne, identyfikator URI, ciąg, ciąg[]) i spróbuj ponownie. @@ -222,8 +205,7 @@ FullyQualifiedName - - + W pełni kwalifikowana nazwa @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + Katalog „{0}” rozwiązania nie istnieje. Upewnij się, że katalog rozwiązania podany w pliku runsettings istnieje, a Ty masz uprawnienia odczytu wobec katalogu. The parameter cannot be null or empty. - - + Parametr nie może mieć wartości null ani być pusty. File {0} does not exist. - - + Plik {0} nie istnieje. Object must be of type {0}. - - + Obiekt musi być typu {0}. Aborted - - + Przerwano Completed - - + Zakończono Disconnected - - + Rozłączono Error - - + Błąd Failed - - + Niepowodzenie Inconclusive - - + Niejednoznaczny In Progress - - + W toku Not Executed - - + Niewykonany Not Runnable - - + Niemożliwy do uruchomienia Passed - - + Powodzenie Passed (run aborted) - - + Powodzenie (uruchomienie zostało przerwane) Pending - - + Oczekiwanie Timeout - - + Limit czasu Warning - - + Ostrzeżenie Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Nie można przeprowadzić odczytu z podanego strumienia. Nie można wysłać danych ze strumienia, jeśli strumień nie obsługuje odczytu. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Podana nazwa pliku „{0}” zawiera następujące nieprawidłowe znaki: „{1}”. The provided file name '{0}' is reserved. - - + Podana nazwa pliku „{0}” została zarezerwowana. Failed to Create msdia Session COM HResult '{0}'. Nie można utworzyć modelu COM sesji msdia, wartość HResult: „{0}”. - - + Failed to load msdia Nie można załadować elementu msdia - - + Invalid URI in data collector settings '{0}'. Nieprawidłowy identyfikator URI w ustawieniach modułu zbierającego dane „{0}”. - - + Invalid URI '{0}' in settings '{1}'. Nieprawidłowy identyfikator URI „{0}” w ustawieniach „{1}”. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Nieprawidłowe ustawienia „{0}”. Oczekiwany jest co najmniej jeden atrybut XmlAttribute wraz z przyjazną nazwą, identyfikatorem URI oraz kwalifikowaną nazwą zestawu. - - + Filter string '{0}' includes unrecognized escape sequence. Ciąg filtra „{0}” obejmuje nierozpoznaną sekwencję ucieczki. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pt-BR.xlf index 42c8e268f3..08797c50a5 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.pt-BR.xlf @@ -9,8 +9,7 @@ None - - + Nenhum @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Mensagens de teste: {0} Message: {0} - - + Mensagem: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (nulo) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Não é possível registrar a propriedade '{0}' com o tipo de valor '{1}' porque ela já foi registrada como '{2}'. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + Não é possível localizar o TypeConverter para o tipo {0}. @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Configurações inválidas '{0}'. XmlAttribute inesperado: '{1}'. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Configurações inválidas '{0}'. XmlElement inesperado: '{1}'. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Configurações de coletores de dados inválidas. Atributo esperado '{0}' está ausente. O coletor de dados típico de configuração se pareceria com <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyqualifiedname="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Configurações inválidas '{0}'. Valor inválido '{1}' especificado para '{2}'. The root node of the run settings must be named 'RunSettings'. - - + O nó raiz das configurações de execução deve ser nomeado como 'RunSettings'. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Não é possível especificar o TestCaseFilter para a execução de testes específicos. FilterCriteria é somente para execução com fontes. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Não há suporte para o tipo de propriedade de teste '{0}' da propriedade '{1}'. Use um dos tipos de propriedade com suporte (tipos primitivos, URI, cadeia de caracteres, string[]) e tente novamente. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + O diretório da solução '{0}' não existe. Verifique se o diretório da solução especificado em runsettings existe e se tem permissões de leitura para o diretório. The parameter cannot be null or empty. - - + O parâmetro não pode ser nulo ou estar vazio. File {0} does not exist. - - + O arquivo {0} não existe. Object must be of type {0}. - - + O objeto deve ser do tipo {0}. Aborted - - + Anulado Completed - - + Concluído Disconnected - - + Desconectado Error - - + Erro Failed - - + Com falha Inconclusive - - + Inconclusivo In Progress - - + Em andamento Not Executed - - + Não executado Not Runnable - - + Não executável Passed - - + Aprovado Passed (run aborted) - - + Aprovado (execução anulada) Pending - - + Pendente Timeout - - + Tempo limite Warning - - + Aviso Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Não é possível ler o fluxo fornecido. Não é possível enviar dados de um fluxo, a menos que o fluxo ofereça suporte para leitura. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + O nome de arquivo fornecido '{0}' contém os seguintes caracteres inválidos: '{1}'. The provided file name '{0}' is reserved. - - + O nome de arquivo fornecido '{0}' é reservado. Failed to Create msdia Session COM HResult '{0}'. Falha ao Criar o HResult COM de Sessão msdia '{0}'. - - + Failed to load msdia Falha ao carregar msdia - - + Invalid URI in data collector settings '{0}'. URI inválido nas configurações do coletor de dados '{0}'. - - + Invalid URI '{0}' in settings '{1}'. URI inválido '{0}' nas configurações '{1}'. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Configurações inválidas '{0}'. Era esperado pelo menos um do XmlAttribute entre friendlyName, uri e assemblyQualifiedName. - - + Filter string '{0}' includes unrecognized escape sequence. A cadeia de caracteres de filtro '{0}' inclui sequência de escape não reconhecida - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ru.xlf index 1a4cdc7801..a4d319626c 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.ru.xlf @@ -9,8 +9,7 @@ None - - + Нет @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Тестовые сообщения: {0} Message: {0} - - + Сообщение: {0} StackTrace: {0} - - + Трассировка стека: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + Невозможно зарегистрировать свойство "{0}" как тип значения "{1}", так как оно уже зарегистрировано как "{2}". @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + Не удается найти преобразователь TypeConverter для типа {0}. @@ -154,26 +145,22 @@ Id - - + Идентификатор Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + Недопустимые параметры "{0}". Неожиданный атрибут XmlAttribute: "{1}". Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + Недопустимые параметры "{0}". Неожиданный элемент XmlElement: "{1}". Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Недопустимые параметры сборщика данных. Отсутствует ожидаемый атрибут "{0}". Типичный параметр сборщика данных обычно выглядит следующим образом: <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + Недопустимые параметры "{0}". Недопустимое значение "{1}", указанное для "{2}". The root node of the run settings must be named 'RunSettings'. - - + Корневой узел параметров запуска должен иметь имя RunSettings. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Нельзя указывать фильтр TestCaseFilter для конкретного тестового запуска. Условия фильтра FilterCriteria предназначены только для выполнения с использованием источников. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + Тип свойства теста "{0}" для свойства "{1}" не поддерживается. Используйте один из поддерживаемых типов свойств (типы-примитивы, URI, string, string[]) и повторите попытку. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + Каталог решения "{0}" не существует. Убедитесь, что указанный в файле параметров запуска RUNSETTINGS каталог решения существует и для него имеются разрешения на чтение. The parameter cannot be null or empty. - - + Параметр не может быть пустым или иметь значение null. File {0} does not exist. - - + Файл {0} не существует. Object must be of type {0}. - - + Объект должен принадлежать типу {0}. Aborted - - + Прерван Completed - - + Завершен Disconnected - - + Отключен Error - - + Ошибка Failed - - + Не пройден Inconclusive - - + С неопределенным результатом In Progress - - + Выполняется Not Executed - - + Не выполнен Not Runnable - - + Не готов к запуску Passed - - + Пройден Passed (run aborted) - - + Пройден (выполнение прервано) Pending - - + Ожидание Timeout - - + Время ожидания Warning - - + Предупреждение Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Не удается прочитать данные из указанного потока. Данные из потока не могут быть отправлены, если поток поддерживает чтение. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Указанное имя файла "{0}" содержит следующие недопустимые символы: "{1}". The provided file name '{0}' is reserved. - - + Указанное имя файла "{0}" зарезервировано. Failed to Create msdia Session COM HResult '{0}'. Не удалось создать HResult COM сеанса msdia "{0}". - - + Failed to load msdia Не удалось загрузить msdia - - + Invalid URI in data collector settings '{0}'. Недопустимый URI в параметрах сборщика данных "{0}". - - + Invalid URI '{0}' in settings '{1}'. Недопустимый URI "{0}" в параметрах "{1}". - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Недопустимые параметры "{0}". Ожидается как минимум один атрибут XmlAttribute: friendlyName, uri или assemblyQualifiedName. - - + Filter string '{0}' includes unrecognized escape sequence. Строка фильтра "{0}" содержит нераспознанную escape-последовательность. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.tr.xlf index 280697fe13..0ebbc06b6b 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.tr.xlf @@ -9,8 +9,7 @@ None - - + Yok @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + Test İletileri: {0} Message: {0} - - + İleti: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + '{0}' özelliği daha önce '{2}' olarak kaydedildiğinden '{1}' değer türü olarak kaydedilemiyor. @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + {0} türü için TypeConverter bulunamıyor. @@ -154,26 +145,22 @@ Id - - + Kimlik Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + '{0}' ayarları geçersiz. Beklenmeyen XmlAttribute: '{1}'. Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + '{0}' ayarları geçersiz. Beklenmeyen XmlElement: '{1}'. Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + Geçersiz veri toplayıcı ayarları. Beklenen '{0}' özniteliği eksik. Normal bir veri toplayıcı ayarı şöyle görünmelidir: <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + '{0}' ayarları geçersiz. '{2}' için geçersiz '{1}' değeri belirtildi. The root node of the run settings must be named 'RunSettings'. - - + Çalıştırma ayarlarının kök düğümü 'RunSettings' olarak adlandırılmalıdır. Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + Belirli bir test çalıştırması için TestCaseFilter belirtilemiyor. FilterCriteria yalnızca kaynakları olan bir çalıştırma içindir. The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + '{1}' özelliğinin '{0}' test özelliği türü desteklenmiyor. Desteklenen özellik türlerinden birini (temel türler, uri, string, string[]) seçin ve yeniden deneyin. @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + '{0}' çözüm dizini yok. Lütfen runsettings içinde belirtilen çözüm dizininin mevcut olduğundan ve dizin için okuma izinlerine sahip olduğundan emin olun. The parameter cannot be null or empty. - - + Parametre null veya boş olamaz. File {0} does not exist. - - + {0} dosyası yok. Object must be of type {0}. - - + Nesne {0} türünde olmalıdır. Aborted - - + İptal edildi Completed - - + Tamamlandı Disconnected - - + Bağlantı kesildi Error - - + Hata Failed - - + Başarısız Inconclusive - - + Sonuçsuz In Progress - - + Sürüyor Not Executed - - + Yürütülmedi Not Runnable - - + Çalıştırılamıyor Passed - - + Başarılı Passed (run aborted) - - + Başarılı (çalıştırma iptal edildi) Pending - - + Bekliyor Timeout - - + Zaman aşımı Warning - - + Uyarı Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + Belirtilen akıştan okunamadı. Bir akış okumayı desteklemiyorsa, akıştaki veriler gönderilemez. The provided file name '{0}' contains the following invalid characters: '{1}'. - - + Belirtilen '{0}' dosya adı şu geçersiz karakterleri içeriyor: '{1}'. The provided file name '{0}' is reserved. - - + Belirtilen '{0}' dosya adı ayrılmış. Failed to Create msdia Session COM HResult '{0}'. Msdia Oturumu COM HResult '{0}' oluşturulamadı. - - + Failed to load msdia Msdia yüklenemedi - - + Invalid URI in data collector settings '{0}'. '{0}' veri toplayıcı ayarlarında geçersiz URI. - - + Invalid URI '{0}' in settings '{1}'. '{1}' ayarlarında geçersiz URI '{0}'. - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. Geçersiz ayarlar '{0}'. FriendlyName, URI veya AssemblyQualifiedName değişkenlerinden en az biri bekleniyordu. - - + Filter string '{0}' includes unrecognized escape sequence. '{0}' filtre dizesi tanınmayan atlatma sırası içeriyor. - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hans.xlf index 7db6169c19..f34e584153 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hans.xlf @@ -9,8 +9,7 @@ None - - + 无 @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + 测试消息: {0} Message: {0} - - + 消息: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + 无法将属性“{0}”注册为值类型“{1}”，因为已将它注册为“{2}”。 @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + 找不到类型 {0} 的 TypeConverter。 @@ -154,26 +145,22 @@ Id - - + ID Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + 设置“{0}”无效。意外的 XmlAttribute:“{1}”。 Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + 设置“{0}”无效。意外的 XmlElement:“{1}”。 Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + 数据收集器设置无效。缺少所需的特性“{0}”。典型数据收集器设置将类似于 <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">。 @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + 设置“{0}”无效。为“{2}”指定的值“{1}”无效。 The root node of the run settings must be named 'RunSettings'. - - + 必须将运行设置的根节点命名为 "RunSettings"。 Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + 不能为特定测试运行指定 TestCaseFilter。FilterCriteria 仅用于与源一起运行。 The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + 不支持属性“{1}”的测试属性类型“{0}”。使用一种支持的属性类型(基元类型、URI、字符串和 string[])，然后重试。 @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + 解决方案目录“{0}”不存在。请确保在 runsettings 中指定的解决方案目录存在并且具有对该目录的读取权限。 The parameter cannot be null or empty. - - + 参数不能为 NULL 或为空。 File {0} does not exist. - - + 文件 {0} 不存在。 Object must be of type {0}. - - + 对象必须为类型 {0}。 Aborted - - + 已中止 Completed - - + 完成 Disconnected - - + 已断开连接 Error - - + 错误 Failed - - + 失败 Inconclusive - - + 无结论 In Progress - - + 正在进行 Not Executed - - + 未执行 Not Runnable - - + 不可运行 Passed - - + 已通过 Passed (run aborted) - - + 已通过(运行已中止) Pending - - + 待定 Timeout - - + 超时 Warning - - + 警告 Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + 无法从所提供的流读取。无法发送流中的数据，除非该流支持读取。 The provided file name '{0}' contains the following invalid characters: '{1}'. - - + 提供的文件名“{0}”包含以下无效字符:“{1}”。 The provided file name '{0}' is reserved. - - + 所提供的文件名“{0}”是保留文件名。 Failed to Create msdia Session COM HResult '{0}'. 未能创建 msdia 会话 COM HResult“{0}”。 - - + Failed to load msdia 未能加载 msdia - - + Invalid URI in data collector settings '{0}'. 数据收集器设置“{0}”中的 URI 无效。 - - + Invalid URI '{0}' in settings '{1}'. 设置 "{1}" 中的 URI "{0}" 无效。 - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. 无效设置 "{0}"。按照预期，在 friendlyName、URI 和 assemblyQualifiedName 中至少存在一个 XmlAttribute。 - - + Filter string '{0}' includes unrecognized escape sequence. 筛选器字符串“{0}”包含无法识别的转义序列。 - - + diff --git a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hant.xlf index cef00d7fb6..566ec5baec 100644 --- a/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.ObjectModel/Resources/xlf/Resources.zh-Hant.xlf @@ -9,8 +9,7 @@ None - - + 無 @@ -20,50 +19,43 @@ {0,-10} {1} - - + {0,-10} {1} {0}: {1} - - + {0}: {1} Test Messages: {0} - - + 測試訊息: {0} Message: {0} - - + 訊息: {0} StackTrace: {0} - - + StackTrace: {0} (null) - - + (null) Cannot register property '{0}' as value type '{1}' because it was already registered as '{2}'. - - + 無法將屬性 '{0}' 登錄為值類型 '{1}'，因為它已登錄為 '{2}'。 @@ -138,8 +130,7 @@ Cannot find TypeConverter for type {0}. - - + 找不到類型 {0} 的 TypeConverter。 @@ -154,26 +145,22 @@ Id - - + 識別碼 Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'. - - + 設定 '{0}' 無效。未預期的 XmlAttribute: '{1}'。 Invalid settings '{0}'. Unexpected XmlElement: '{1}'. - - + 設定 '{0}' 無效。未預期的 XmlElement: '{1}'。 Invalid data collector settings. Expected attribute '{0}' is missing. A typical data collector setting would look like <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">. - - + 無效的資料收集器設定。預期的屬性 '{0}' 遺失。一般的資料收集器設定看起來像 <DataCollector uri="dataCollector://Samples/SampleCollector/1.0" assemblyQualifiedName="Samples.SampleCollector.SampleDataCollector, SampleCollectors, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1111111111111111" friendlyName="sampleCollector">。 @@ -193,26 +180,22 @@ Invalid settings '{0}'. Invalid value '{1}' specified for '{2}'. - - + 設定 '{0}' 無效。為 '{2}' 指定的值 '{1}' 無效。 The root node of the run settings must be named 'RunSettings'. - - + 回合設定的根節點必須命名為 'RunSettings'。 Cannot specify TestCaseFilter for specific tests run. FilterCriteria is only for run with sources. - - + 無法為特定測試回合指定 TestCaseFilter。FilterCriteria 只適用於以來源執行的狀況。 The test property type '{0}' of property '{1}' is not supported. Use one of the supported property type (primitive types, uri, string, string[]) and try again. - - + 不支援屬性 '{1}' 的測試屬性類型 '{0}'。請使用其中一個支援的屬性類型 (基本類型、uri、string、string[])，並再試一次。 @@ -222,8 +205,7 @@ FullyQualifiedName - - + FullyQualifiedName @@ -233,165 +215,138 @@ Solution directory '{0}' does not exists. Please make sure solution directory specified in runsettings exists and have read permissions for directory. - - + 解決方案目錄 '{0}' 不存在。請確認 runsettings 中指定的解決方案目錄存在，並且具有目錄的讀取權限。 The parameter cannot be null or empty. - - + 參數不可為 null 或空白。 File {0} does not exist. - - + 檔案 {0} 不存在。 Object must be of type {0}. - - + 物件必須為 {0} 類型。 Aborted - - + 已中止 Completed - - + 已完成 Disconnected - - + 已中斷連線 Error - - + 錯誤 Failed - - + 失敗 Inconclusive - - + 結果不明 In Progress - - + 進行中 Not Executed - - + 未執行 Not Runnable - - + 無法執行 Passed - - + 成功 Passed (run aborted) - - + 成功 (執行已中止) Pending - - + 暫止 Timeout - - + 逾時 Warning - - + 警告 Unable to read from the provided stream. Data from a stream cannot be sent unless the stream supports reading. - - + 無法讀取提供的資料流。除非資料流支援讀取，否則無法傳送來自資料流的資料。 The provided file name '{0}' contains the following invalid characters: '{1}'. - - + 提供的檔案名稱 '{0}' 含有下列無效的字元: '{1}'。 The provided file name '{0}' is reserved. - - + 已保留提供的檔案名稱 '{0}'。 Failed to Create msdia Session COM HResult '{0}'. 無法建立 msdia 工作階段 COM HResult '{0}'。 - - + Failed to load msdia 無法載入 msdia - - + Invalid URI in data collector settings '{0}'. 資料收集器設定 '{0}' 中的 URI 無效。 - - + Invalid URI '{0}' in settings '{1}'. 設定 '{1}' 中的 URI '{0}' 無效。 - - + Invalid settings '{0}'. Expected atleast one of the XmlAttribute among friendlyName, uri and assemblyQualifiedName. 設定 '{0}' 無效。在 friendlyName、URI assemblyQualifiedName 之間，至少要有一個 XmlAttribute。 - - + Filter string '{0}' includes unrecognized escape sequence. 篩選字串 '{0}' 包含無法辨識的逸出序列。 - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.cs.xlf index 86de428615..52a857de0e 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.cs.xlf @@ -7,20 +7,17 @@ {0} Našlo se více verzí stejného rozšíření. Vybere se nejvyšší verze. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". Nejde najít {0}. Ujistěte se, že testovací projekt má odkaz na balíček nuget Microsoft.NET.Test.Sdk. - - + Unable to find {0}. Please publish your test project and retry. Nejde najít {0}. Publikujte prosím svůj testovací projekt a zkuste to znovu. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.de.xlf index f7182e443b..100490cade 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.de.xlf @@ -7,20 +7,17 @@ {0} Es wurden mehrere Versionen derselben Erweiterung gefunden. Die höchste Version wird ausgewählt. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". "{0}" wurde nicht gefunden. Stellen Sie sicher, dass das Testprojekt einen NuGet-Verweis des Pakets "Microsoft.NET.Test.Sdk" aufweist. - - + Unable to find {0}. Please publish your test project and retry. "{0}" wurde nicht gefunden. Veröffentlichen Sie Ihr Testprojekt, und versuchen Sie es noch mal. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.es.xlf index 9f043f6963..1cfe87db50 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.es.xlf @@ -7,20 +7,17 @@ {0} Se encontraron varias versiones de la misma extensión. Seleccionando la versión más alta. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". No se encuentra {0}. Asegúrese de que el proyecto de prueba tenga una referencia NuGet del paquete "Microsoft.NET.Test.Sdk". - - + Unable to find {0}. Please publish your test project and retry. No se encuentra {0}. Publique el proyecto de prueba y vuelva a intentarlo. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.fr.xlf index ad1f942e77..c041cd085f 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.fr.xlf @@ -7,20 +7,17 @@ {0} Plusieurs versions de la même extension ont été trouvées. Sélection de la version la plus élevée. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". {0} est introuvable. Vérifiez que le projet de test a une référence nuget du package "Microsoft.NET.Test.Sdk". - - + Unable to find {0}. Please publish your test project and retry. {0} est introuvable. Publiez votre projet de test et réessayez. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.it.xlf index 1689e6eab4..42d74885e5 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.it.xlf @@ -7,20 +7,17 @@ {0} Sono state trovate più versioni della stessa estensione. Verrà selezionata quella più recente. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". Non è possibile trovare {0}. Assicurarsi che il progetto di test includa un riferimento NuGet del pacchetto "Microsoft.NET.Test.Sdk". - - + Unable to find {0}. Please publish your test project and retry. Non è possibile trovare {0}. Pubblicare il progetto di test e riprovare. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ja.xlf index a909a94705..62108eca0b 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ja.xlf @@ -7,20 +7,17 @@ {0} 同じ拡張子で複数のバージョンが見つかりました。最新のバージョンを選択しています。 {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". {0} を見つけることができません。テスト プロジェクトにパッケージ "Microsoft.NET.Test.Sdk" の NuGet 参照があることを確認してください。 - - + Unable to find {0}. Please publish your test project and retry. {0} を見つけることができません。テスト プロジェクトを公開してもう一度お試しください。 - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ko.xlf index 23a71202e4..d8e7d172d6 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ko.xlf @@ -7,20 +7,17 @@ {0} 동일한 확장의 여러 버전을 찾았습니다. 가장 높은 버전을 선택합니다. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". {0}을(를) 찾을 수 없습니다. 테스트 프로젝트에 "Microsoft.NET.Test.Sdk" 패키지의 nuget 참조가 포함되어 있는지 확인하세요. - - + Unable to find {0}. Please publish your test project and retry. {0}을(를) 찾을 수 없습니다. 테스트 프로젝트를 게시하고 다시 시도하세요. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pl.xlf index 800576f361..39b704e462 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pl.xlf @@ -7,20 +7,17 @@ {0} Znaleziono wiele wersji tego samego rozszerzenia. Wybierana jest najwyższa wersja. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". Nie można znaleźć elementu {0}. Upewnij się, że projekt testowy ma odwołanie nuget do pakietu „Microsoft.NET.Test.Sdk”. - - + Unable to find {0}. Please publish your test project and retry. Nie można znaleźć elementu {0}. Opublikuj swój projekt testowy i spróbuj ponownie. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pt-BR.xlf index 332c43ba8a..1944fd7115 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.pt-BR.xlf @@ -7,20 +7,17 @@ {0} Várias versões da mesma extensão foram encontradas. Selecionando a versão mais alta. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". Não foi possível localizar {0}. Certifique-se de que o projeto de teste tem uma referência nuget do pacote "Microsoft.NET.Test.Sdk". - - + Unable to find {0}. Please publish your test project and retry. Não foi possível localizar {0}. Publique o projeto de teste e tente novamente. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ru.xlf index ff0e3ff7e2..4d098564ee 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.ru.xlf @@ -7,20 +7,17 @@ {0} Обнаружено несколько версий одного расширения. Выбрана самая поздняя версия. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". Не удается найти {0}. Убедитесь, что в тестовом проекте есть ссылка NuGet на пакет "Microsoft.NET.Test.Sdk". - - + Unable to find {0}. Please publish your test project and retry. Не удалось найти {0}. Опубликуйте тестовый проект и повторите попытку. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.tr.xlf index 6a3b50014e..afbaa599f0 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.tr.xlf @@ -7,20 +7,17 @@ {0} Aynı uzantının birden çok sürümü bulundu. En yüksek sürüm seçiliyor. {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". {0} bulunamıyor. Test projesinin "Microsoft.NET.Test.Sdk" paketinde nuget başvurusu olduğundan emin olun. - - + Unable to find {0}. Please publish your test project and retry. {0} bulunamıyor. Lütfen test projenizi yayımlayın ve yeniden deneyin. - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hans.xlf index c7d57e44cd..0b0a602375 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hans.xlf @@ -7,20 +7,17 @@ {0} 找到多个具有相同扩展的版本。请选择最高版本。 {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". 无法找到 {0}。确保测试项目具有包 "Microsoft.NET.Test.Sdk" 的 nuget 引用。 - - + Unable to find {0}. Please publish your test project and retry. 无法找到 {0}。请发布测试项目并重试。 - - + diff --git a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hant.xlf index aaa112eadf..02e48d5a16 100644 --- a/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.TestHostProvider/Resources/xlf/Resources.zh-Hant.xlf @@ -7,20 +7,17 @@ {0} 找到相同延伸模組的多個版本。系統會選取最高版本。 {0} - - + Unable to find {0}. Make sure test project has a nuget reference of package "Microsoft.NET.Test.Sdk". 找不到 {0}。請確認測試專案有 "Microsoft.NET.Test.Sdk "套件的 nuget 參考。 - - + Unable to find {0}. Please publish your test project and retry. 找不到 {0}。請發佈您的測試專案並重試。 - - + diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.cs.xlf index e2439f8fa0..8c267db1e4 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.cs.xlf @@ -4,44 +4,37 @@ 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í. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.de.xlf index b34e7faf3f..38ee0127b6 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.de.xlf @@ -4,44 +4,37 @@ 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. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.es.xlf index 65a4e9e692..692b6957eb 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.es.xlf @@ -4,44 +4,37 @@ 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. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.fr.xlf index 3c25bc86cb..748f424522 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.fr.xlf @@ -4,44 +4,37 @@ 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é. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.it.xlf index 2e7ee07965..f5104eff95 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.it.xlf @@ -4,44 +4,37 @@ 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. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ja.xlf index ab2d3ee3bf..6aa4ff3684 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ja.xlf @@ -4,44 +4,37 @@ 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. - - + 予期しない設定ファイルが指定されました。 diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ko.xlf index f57dab4132..f59fb250b3 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ko.xlf @@ -4,44 +4,37 @@ 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. - - + 예기치 않은 설정 파일을 지정했습니다. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pl.xlf index 1a7bbffe59..b9c2a6974b 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pl.xlf @@ -4,44 +4,37 @@ 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ń. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pt-BR.xlf index 7fd2daa3d1..a8cb17021f 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.pt-BR.xlf @@ -4,44 +4,37 @@ 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. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ru.xlf index b5f50f97ad..321ddfc8a5 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.ru.xlf @@ -4,44 +4,37 @@ 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. - - + Указанный неожиданный файл параметров. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.tr.xlf index b3a0bc77ce..96cb6bfb86 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.tr.xlf @@ -4,44 +4,37 @@ 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. diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hans.xlf index e0549ff09f..435639785f 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hans.xlf @@ -4,44 +4,37 @@ 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. - - + 指定了意外的设置文件。 diff --git a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hant.xlf index 4d6c86ca39..8895f16c8f 100644 --- a/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.Utilities/Resources/xlf/Resources.zh-Hant.xlf @@ -4,44 +4,37 @@ 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. - - + 指定了非預期的設定檔案。 diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.cs.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.cs.xlf index 850ae4ae58..bfb979a970 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.cs.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.cs.xlf @@ -4,51 +4,43 @@ 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 exists Soubor {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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.de.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.de.xlf index de405d2f42..f5dbd9ebfd 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.de.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.de.xlf @@ -4,51 +4,43 @@ 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 exists Die 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.es.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.es.xlf index 6902730d54..846a8c672e 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.es.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.es.xlf @@ -4,51 +4,43 @@ 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.console vstest.console process exited abnormally - - + El proceso vstest.console finalizó de forma anómala File {0} does not exists El 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.fr.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.fr.xlf index ab15d99a72..520701f49e 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.fr.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.fr.xlf @@ -4,51 +4,43 @@ 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.console vstest.console process exited abnormally - - + Sortie anormale du processus vstest.console File {0} does not exists Le 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.it.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.it.xlf index 12d7eb043d..9c961daa74 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.it.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.it.xlf @@ -4,51 +4,43 @@ 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.console vstest.console process exited abnormally - - + Il processo vstest.console è stato chiuso in modo anomalo File {0} does not exists Il 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ja.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ja.xlf index cdc09cbdb2..f8a2a7df30 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ja.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ja.xlf @@ -4,51 +4,43 @@ 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. テスト セッションの停止操作が中止されました。 - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ko.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ko.xlf index acdb57c4fe..7b5468fb0e 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ko.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ko.xlf @@ -4,51 +4,43 @@ 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. 테스트 세션 중지 작업이 중단되었습니다. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pl.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pl.xlf index 5b6460f77e..1210941c11 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pl.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pl.xlf @@ -4,51 +4,43 @@ 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.console vstest.console process exited abnormally - - + Proces vstest.console zakończył się nieprawidłowo File {0} does not exists Plik {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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pt-BR.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pt-BR.xlf index 301653d4d1..b0403adaac 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pt-BR.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.pt-BR.xlf @@ -4,51 +4,43 @@ 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.console vstest.console process exited abnormally - - + processo de vstest.console encerrado de forma anormal File {0} does not exists O 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ru.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ru.xlf index 0ff66e8787..c35d49a2a9 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ru.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.ru.xlf @@ -4,51 +4,43 @@ 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. Операция остановки сеанса тестирования прервана. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.tr.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.tr.xlf index 9e321ce9c6..bc43e1e1f6 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.tr.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.tr.xlf @@ -4,51 +4,43 @@ 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. - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hans.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hans.xlf index 1da323e0f8..261a682df9 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hans.xlf @@ -4,51 +4,43 @@ 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. 已中止停止测试会话操作。 - - + diff --git a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hant.xlf b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hant.xlf index 86de7d3fc2..0baa3681f5 100644 --- a/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/Microsoft.TestPlatform.VsTestConsole.TranslationLayer/Resources/xlf/Resources.zh-Hant.xlf @@ -4,51 +4,43 @@ 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. 停止測試工作階段作業已中止。 - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.cs.xlf b/src/SettingsMigrator/Resources/xlf/Resources.cs.xlf index f034348258..20546a6c23 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.cs.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.cs.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Všechny uzly LegacySettings, které už jsou v souboru Runsettings, se odstraní. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings neobsahuje žádné vložené testSettings, nemigruje se. - - + The migrated RunSettings file has been created at: {0} Migrovaný soubor RunSettings se vytvořil v: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Atributy agentNotRespondingTimeout, deploymentTimeout a scriptTimeout uzlu Timeouts nejsou podporované, takže se nebudou migrovat. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.de.xlf b/src/SettingsMigrator/Resources/xlf/Resources.de.xlf index 9ec4cf7592..58f1501e26 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.de.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.de.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Bereits in RunSettings vorhandene LegacySettings-Knoten werden entfernt. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings enthält keine eingebetteten testSettings. Die Migration wird nicht durchgeführt. - - + The migrated RunSettings file has been created at: {0} Die migrierte RunSettings-Datei wurde in folgendem Verzeichnis erstellt: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Die Attribute "agentNotRespondingTimeout", "deploymentTimeout" und "scriptTimeout" des Knotens "Timeouts" werden nicht unterstützt und daher nicht migriert. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.es.xlf b/src/SettingsMigrator/Resources/xlf/Resources.es.xlf index a2c38c2974..5c53ace202 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.es.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.es.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Se quitará cualquier nodo de LegacySettings que ya exista en el archivo RunSettings. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings no contiene ningún valor de testSettings incrustado, por lo que no se migrará. - - + The migrated RunSettings file has been created at: {0} El archivo RunSettings migrado se ha creado a las {0}. - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Los atributos agentNotRespondingTimeout, deploymentTimeout, scriptTimeout del nodo Timeouts no se admiten, por lo que no se migrarán. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.fr.xlf b/src/SettingsMigrator/Resources/xlf/Resources.fr.xlf index 88aa9c39fe..47500388c1 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.fr.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.fr.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Tout nœud LegacySettings déjà présent dans les paramètres d’exécution sera supprimé. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings ne contient pas de testSettings incorporé. Échec de la migration. - - + The migrated RunSettings file has been created at: {0} Le fichier RunSettings migré a été créé à : {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Les attributs agentNotRespondingTimeout, deploymentTimeout et scriptTimeout du nœud Timeouts ne sont pas pris en charge. Ils ne seront donc pas migrés. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.it.xlf b/src/SettingsMigrator/Resources/xlf/Resources.it.xlf index 8e24921737..7c0c22c825 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.it.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.it.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. L'eventuale nodo LegacySettings già presente nel file RunSettings verrà rimosso. - - + RunSettings does not contain an embedded testSettings, not migrating. Il file RunSettings non contiene un elemento testSettings incorporato. La migrazione non verrà eseguita. - - + The migrated RunSettings file has been created at: {0} Il file RunSettings di cui è stata eseguita la migrazione è stato creato in: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Gli attributi agentNotRespondingTimeout, deploymentTimeout, scriptTimeout del nodo Timeouts non sono supportati, di conseguenza non ne verrà eseguita la migrazione. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.ja.xlf b/src/SettingsMigrator/Resources/xlf/Resources.ja.xlf index bc241ddc50..d9f7f28410 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.ja.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.ja.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. RunSettings 内に既に存在するすべての LegacySettings ノードは削除されます。 - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings には埋め込み testSettings が含まれていないため、移行されません。 - - + The migrated RunSettings file has been created at: {0} 移行された RunSettings ファイルは次の場所に作成されました: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Timeouts ノードの agentNotRespondingTimeout、deploymentTimeout、scriptTimeout 属性はサポートされていないため、これらは移行されません。 - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.ko.xlf b/src/SettingsMigrator/Resources/xlf/Resources.ko.xlf index 71189c8049..a0eabdc951 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.ko.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.ko.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. runsettings에 이미 존재하는 LegacySettings 노드가 제거됩니다. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings에 포함된 testSettings이 없으며 마이그레이션되지 않습니다. - - + The migrated RunSettings file has been created at: {0} 마이그레이션된 RunSettings 파일은 {0}에 생성되었습니다. - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. 시간 제한 노드의 agentNotRespondingTimeout, deploymentTimeout, scriptTimeout 특성은 지원되지 않으므로 마이그레이션되지 않습니다. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.pl.xlf b/src/SettingsMigrator/Resources/xlf/Resources.pl.xlf index 91f9cbb4a2..2e71fcf941 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.pl.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.pl.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Wszelkie węzły LegacySettings już istniejące w pliku runsettings zostaną usunięte. - - + RunSettings does not contain an embedded testSettings, not migrating. Plik RunSettings nie zawiera osadzonego elementu testSettings, migracja nie jest wykonywana. - - + The migrated RunSettings file has been created at: {0} Zmigrowany plik RunSettings został utworzony w: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Atrybuty agentNotRespondingTimeout, deploymentTimeout i scriptTimeout węzła Timeouts nie są obsługiwane, więc nie zostaną zmigrowane. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MójTest\UstawieniaMojegoTestu.testsettings SettingsMigrator.exe E:\MójTest\UstawieniaMojegoStaregoPrzebiegu.runsettings SettingsMigrator.exe E:\MójTest\UstawieniaMojegoTestu.testsettings E:\MójTest\UstawieniaMojegoNowegoPrzebiegu.runsettings SettingsMigrator.exe E:\MójTest\UstawieniaMojegoStaregoPrzebiegu.runsettings E:\MójTest\UstawieniaMojegoNowegoPrzebiegu.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.pt-BR.xlf b/src/SettingsMigrator/Resources/xlf/Resources.pt-BR.xlf index 1cfb4ddb09..d49ed59e0a 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.pt-BR.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.pt-BR.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Qualquer nó LegacySettings já presente em runsettings será removido. - - + RunSettings does not contain an embedded testSettings, not migrating. O RunSettings que não contém um testSettings incorporado não migrará. - - + The migrated RunSettings file has been created at: {0} O arquivo RunSettings migrado foi criado em: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Os atributos agentNotRespondingTimeout, deploymentTimeout, scriptTimeout do nó Timeouts não têm suporte, portanto, não serão migrados. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.ru.xlf b/src/SettingsMigrator/Resources/xlf/Resources.ru.xlf index 089e3acd87..7441b23f98 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.ru.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.ru.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Любые узлы LegacySettings в runsettings будут удалены. - - + RunSettings does not contain an embedded testSettings, not migrating. Файл RunSettings не содержит внутри себя testSettings. Перенос выполняться не будет. - - + The migrated RunSettings file has been created at: {0} Перенесенный файл RunSettings создан в {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Атрибуты agentNotRespondingTimeout, deploymentTimeout, scriptTimeout узла Timeouts не поддерживаются и перенесены не будут. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.tr.xlf b/src/SettingsMigrator/Resources/xlf/Resources.tr.xlf index c91eb14622..2640caa2e8 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.tr.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.tr.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. Runsettings içinde zaten mevcut olan tüm Any LegacySettings düğümleri kaldırılacak. - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings, ekli bir testSettings içermiyor ve geçirilmiyor. - - + The migrated RunSettings file has been created at: {0} Geçirilen RunSettings dosyası şu konumda oluşturuldu: {0} - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Zaman aşımları düğümünün agentNotRespondingTimeout, deploymentTimeout, scriptTimeout öznitelikleri desteklenmediğinden bunlar geçirilmeyecek. - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.zh-Hans.xlf b/src/SettingsMigrator/Resources/xlf/Resources.zh-Hans.xlf index 3e3437b957..47cfb40472 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.zh-Hans.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. 已经存在于 runsettings 中的任何 LegacySettings 节点都将被删除。 - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings 不包含嵌入的 testSettings，不会迁移。 - - + The migrated RunSettings file has been created at: {0} 已迁移的 RunSettings 文件已在 {0} 中创建 - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. Timeouts 节点的属性 agentNotRespondingTimeout、deploymentTimeout、scriptTimeout 不受支持，因此不会迁移它们。 - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/SettingsMigrator/Resources/xlf/Resources.zh-Hant.xlf b/src/SettingsMigrator/Resources/xlf/Resources.zh-Hant.xlf index 87899b5381..1a25da44e4 100644 --- a/src/SettingsMigrator/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/SettingsMigrator/Resources/xlf/Resources.zh-Hant.xlf @@ -5,26 +5,22 @@ Any LegacySettings node already present in the runsettings will be removed. 所有出現在 runsettings 中的 LegacySettings 節點，都將移除。 - - + RunSettings does not contain an embedded testSettings, not migrating. RunSettings 並不包含內嵌的 testSettings，所以未移轉。 - - + The migrated RunSettings file has been created at: {0} 移轉的 RunSettings 檔案已於 {0} 建立 - - + The attributes agentNotRespondingTimeout, deploymentTimeout, scriptTimeout of Timeouts node are not supported, so these will not be migrated. 不支援 Timeouts 節點的屬性 agentNotRespondingTimeout、deploymentTimeout、scriptTimeout，所以這些將不會移轉。 - - + Valid usage: @@ -43,8 +39,7 @@ SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyTestSettings.testsettings E:\MyTest\MyNewRunSettings.runsettings SettingsMigrator.exe E:\MyTest\MyOldRunSettings.runsettings E:\MyTest\MyNewRunSettings.runsettings - - + diff --git a/src/vstest.console/Resources/xlf/Resources.cs.xlf b/src/vstest.console/Resources/xlf/Resources.cs.xlf index cc7859270c..0a950cc6e4 100644 --- a/src/vstest.console/Resources/xlf/Resources.cs.xlf +++ b/src/vstest.console/Resources/xlf/Resources.cs.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + {0} se nenašel. The following Test Discovery Add-Ins are available: - - + Jsou k dispozici tyto doplňky zjišťování testů: The following Test Execution Add-Ins are available: - - + Jsou k dispozici tyto doplňky pro provádění testů: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Jsou k dispozici tyto doplňky protokolovače testu: @@ -44,8 +39,7 @@ Error: {0} - - + Chyba: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Parametr {0} by se měl poskytnout jenom jednou. Exception occurred when instantiating extension '{0}': {1} - - + Při vytváření instance rozšíření {0} došlo k výjimce: {1} The following Tests are available: - - + Jsou k dispozici následující testy: Unrecognized parameter "{0}". - - + Nerozpoznaný parametr {0} The test source file "{0}" provided was not found. - - + Poskytnutý zdrojový soubor testu {0} se nenašel. 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. Information: {0} - - + Informace: {0} Warning: {0} - - + Upozornění: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Zobrazí tuto zprávu o používání. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Všechna práva vyhrazena. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Test Execution Command Line Tool verze {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<identifikátor URI nebo popisný název protokolovacího nástroje> Určuje protokolovací nástroj pro výsledky testu. Pokud chcete protokolovat výsledky třeba do souboru výsledků testu sady Visual Studio (TRX), použijte /logger:trx[;LogFileName=<výchozí hodnota je jedinečný název souboru>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Popis: Spustí testy ze zadaných souborů. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Použití: vstest.console.exe [argumenty] [možnosti] [[--] <argumenty RunSettings>...]] No test source files were specified. - - + Nezadaly se žádné zdrojové soubory testů. No arguments were specified. - - + Nezadaly se žádné argumenty. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Spusťte testy ze zadaných souborů nebo ze vzoru se zástupnými znaky. Oddělte více názvů nebo vzorů testovacích souborů pomocí mezer. Nastavte úroveň podrobností protokolovacího nástroje konzoly na podrobnou, aby se zobrazily odpovídající testovací soubory. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Jsou k dispozici tyto doplňky poskytovatelů nastavení: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<soubor nastavení> Nastavení, která se použijí při testování. The /Settings parameter requires a settings file to be provided. - - + Parametr /Settings vyžaduje, aby se poskytl soubor nastavení. The Settings file '{0}' could not be found. - - + Soubor nastavení {0} se nenašel. Test Run Failed. - - + Testovací běh nebyl úspěšný. Test Run Successful. - - + Testovací běh byl úspěšný. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + V příkazu InIsolation se argument {0} neočekává. Zadejte příkaz bez tohoto argumentu (třeba vstest.console.exe myTests.dll /InIsolation) a zkuste to znovu. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Parametr /UseVsixExtensions vyžaduje hodnotu. Pokud hodnota bude true, v testovacím běhu se použijí nainstalovaná rozšíření VSIX (pokud nějaká jsou). Pokud je hodnota false, budou se rozšíření ignorovat. Příklad: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + V příkazu UseVsixExtensions se argument {0} neočekává. Zadejte příkaz, který určí, jestli se mají rozšíření vsix používat, nebo přeskočit (třeba vstest.console.exe myTests.dll /UseVsixExtensions:true) a zkuste to znovu. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Spustí testy v izolovaném procesu. Díky tomu je méně pravděpodobné, že se proces vstest.console.exe zastaví, pokud se v testech stane chyba, @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Tato možnost určí, jestli má proces vstest.console.exe v testovacím běhu používat, nebo přeskočit nainstalovaná rozšíření VSIX (pokud nějaká jsou). @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + Argument /BatchSize vyžaduje velikost dávky. Příklad: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Neplatná velikost dávky {0}. Velikost dávky by měla být větší než nula. Příklad: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Pro spuštění testů: >vstest.console.exe tests.dll Pro spuštění testů s dalšími nastaveními, třeba kolekcemi dat: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Vypíše nainstalované nástroje zjišťování testů. /ListExecutors Lists installed test executors. - - + /ListExecutors Vypíše nainstalované prováděcí moduly testů. /ListLoggers Lists installed test loggers. - - + /ListLoggers Vypíše nainstalované protokolovače testů. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Vypíše nainstalované poskytovatele nastavení testů. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<název souboru> Vypíše všechny zjištěné testy z daného kontejneru testů. Time elapsed : - - + Uplynulý čas: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + Argument /Tests vyžaduje aspoň jeden konkrétní název testu nebo jeho podřetězec. Příklady: /Tests:TestovaciMetoda1, /Tests:TestovaciMetoda1,metoda2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Zjistilo se několik testů (celkem {0}), ale žádný z testů neodpovídá zadaným kritériím výběru ({1}). Použijte správné hodnoty a zkuste to znovu. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Ke spouštění testů se používá režim izolace, protože v nastavení Runsettings se povolily adaptéry diagnostických dat. Pokud chcete toto upozornění potlačit, použijte parametr /InIsolation. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Ke spouštění testů jednotek pro aplikace pro Windows Store se používá režim izolace. Pokud chcete toto upozornění potlačit, použijte parametr /InIsolation. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Pokud se spouští testy jednotek pro aplikace pro Windows Store, nepodporují se adaptéry diagnostických dat. Odeberte nastavení adaptérů diagnostických dat z nastavení. FriendlyName: {0} - - + PopisnýNázev: {0} Uri: {0} - - + Identifikátor URI: {0} SettingName: {0} - - + NázevNastavení: {0} Supported File Types: - - + Podporované typy souborů: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + Identifikátor URI výchozího prováděcího modulu: {0} Uri: {0} - - + Identifikátor URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Neplatný typ platformy: {0}. Platné typy platformy jsou x86, x64 a Arm. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + Argument /Platform vyžaduje, aby se pro testovací běh poskytl typ platformy. Příklad: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<typ platformy> Cílová architektura platformy, která se použije ke spuštění testu. Platné hodnoty jsou x86, x64 a ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Pro provádění testů se používá režim izolace tak, jak to vyžaduje nastavení platformy {0} a rozhraní .NET Framework {1} pro testovací běh. Pokud chcete toto upozornění potlačit, použijte parametr /InIsolation. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<verze rozhraní> Cílová verze rozhraní .NET Framework, která se použije ke spuštění testu. Platné hodnoty jsou .NETFramework,Version=v4.5.1, .NETCoreApp,Version=v1.0 apod. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + Argument /Framework vyžaduje cílovou verzi rozhraní .NET Framework pro testovací běh. Příklad: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Neplatná verze rozhraní .NET Framework: {0}. Zadejte prosím úplný název cílového rozhraní (příklad: .NETCoreApp,Version=v2.0). Další podporované verze jsou Framework40, Framework45, FrameworkCore10 a FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Nepovedlo se spustit testovací běh pro testy jednotek aplikace pro Windows Store: {0} @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<výraz> Spustí testy, které odpovídají danému výrazu. <výraz> musí být formátu <vlastnost>operátor<hodnota>[|&<výraz>], @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + Argument příkazu /TestCaseFilter vyžaduje hodnotu filtru. Hodnota filtru by měla být typu<vlastnost>=<hodnota>. Příklady: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Argument /TestCaseFilter nejde zadat spolu s argumentem /Tests. Když se zadají testy, filtrování testovacích případů nejde použít. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + Projekt {0} je sestavený pro {1}/{2}. Testovací sestavení zadané v běhu by měly mít společné cílové rozhraní .NET Framework a platformu. Only one app package (.appx file) can be specified for running tests. - - + Pro spouštění testů se dá zadat jenom jeden balíček aplikace (soubor .appx). Starting test discovery, please wait... - - + Začínají se zjišťovat testy, počkejte prosím... Starting test execution, please wait... - - + Začínají se provádět testy, počkejte prosím... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + Při čtení nastavení adaptéru diagnostických dat se vyvolala výjimka {0}. Všechny adaptéry diagnostických dat se v tomto běhu přeskočí. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Povolí kolekci dat CodeCoverage pro testovací běh. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + V příkazu EnableCodeCoverage se argument {0} neočekává. Zadejte příkaz bez tohoto argumentu (třeba vstest.console.exe myTests.dll /EnableCodeCoverage) a zkuste to znovu. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + Balíček aplikace {0} nemá vstupní bod prováděcího modulu testování. Pokud chcete spouštět testy jednotek pro aplikace pro Windows Store, vytvořte balíček aplikace pomocí projektu Knihovna testu jednotek pro aplikaci pro Windows Store. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Pro aplikace pro Windows Store není pokrytí kódu k dispozici. Pro tento testovací běh se analýza pokrytí kódu přeskočí. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Zjistilo se několik testů (celkem {0}), ale některé z testů neodpovídají zadaným kritériím výběru ({1}). Použijte správné hodnoty a zkuste to znovu. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Proces vstest.console.exe použije v testovacím běhu vlastní adaptéry testu ze zadané cesty (pokud existují). @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Parametr /TestAdapterPath vyžaduje hodnotu, která je součástí umístění obsahujícího vlastní adaptéry testů. Příklad: /TestAdapterPath:c:\MojeVlastniAdaptery The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Cesta {0} zadaná v TestAdapterPath není platná. Chyba: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Zadaná cesta pro vyhledávání vlastních adaptérů testů se nenašla. Zadejte platnou cestu a zkuste to znovu. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Cesta {0} zadaná v TestAdapterPath neobsahuje žádné adaptéry testů. Zadejte platnou cestu a zkuste to znovu. Could not start test run for the tests for Windows Phone app: {0}. - - + Nepovedlo se spustit testovací běh pro testy aplikace pro Windows Phone: {0} Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Ke spouštění testů jednotek pro aplikace pro Windows Phone se používá režim izolace. Pokud chcete toto upozornění potlačit, použijte parametr /InIsolation. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Pro aplikace pro Windows Phone není pokrytí kódu k dispozici. Pro tento testovací běh se analýza pokrytí kódu přeskočí. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Pokud se spouští testy jednotek pro aplikace pro Windows Phone, nepodporují se adaptéry diagnostických dat. Odeberte nastavení adaptérů diagnostických dat z nastavení. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + Balíček aplikace {0} nemá vstupní bod prováděcího modulu testování. Pokud chcete spouštět testy jednotek pro aplikace pro Windows Phone, vytvořte balíček aplikace pomocí projektu Knihovna testu jednotek pro aplikaci pro Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Ke spouštění testů se používá rozhraní {0}. Pokud chcete toto upozornění potlačit, zadejte /Framework:{1}. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + V kontejnerech testů se nenašly žádné testy. Navíc Adaptér testování částí aplikací pro Microsoft Windows Store nepodporuje soubory .appxbundle. Při vytváření balíčku aplikace vytvořte soubor appx (nastavte možnost Generovat svazek aplikací na Nikdy) a zkuste to znovu. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Určí, že se testy mají provádět paralelně. Ve výchozím nastavení se můžou použít všechna dostupná jádra počítače. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + V příkazu Parallel se argument {0} neočekává. Zadejte příkaz bez tohoto argumentu (třeba vstest.console.exe myTests.dll /Parallel) a zkuste to znovu. Cannot be null or empty - - + Nemůže být null nebo prázdné. --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<port> Port pro připojení soketu a přijímání zpráv událostí The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + Argument --Port|/Port vyžaduje celočíselné číslo portu. Zadejte port pro připojení soketu a přijímání zpráv událostí. Unable to find the assembly under test. Please make sure that the project is built. - - + Nepovedlo se najít testované sestavení. Ujistěte se prosím, že je projekt sestavený. The Path {0} does not exist. - - + Cesta {0} neexistuje. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> Adresář, který obsahuje dočasné výstupy -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<konfigurace> Konfigurace, pro kterou se projekt sestaví, tj. Debug/Release The given configuration is invalid. - - + Zadaná konfigurace není platná. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<výstup> Adresář, který obsahuje binární soubory, které se mají spustit The BuildBasePath was not found, provide a valid path and try again. - - + Cesta k základu sestavení se nenašla, zadejte platnou cestu a zkuste to znovu. The Output path was not found, provide a valid path and try again. - - + Cesta k výstupu se nenašla, zadejte platnou cestu a zkuste to znovu. Additional Information Messages: - - + Další informační zprávy: Days - - + Dny Error Message: - - + Chybová zpráva: Total time: {0:0.0000} {1} - - + Celkový čas: {0:0.0000} {1} Hours - - + Hodiny Could not find a test logger with URI or FriendlyName '{0}'. - - + Nepovedlo se najít protokolovač testu s identifikátorem URI nebo popisným názvem {0}. Minutes - - + Minuty Seconds - - + Sekundy Stack Trace: - - + Trasování zásobníku: Standard Error Messages: - - + Zprávy standardních chyb: Standard Output Messages: - - + Zprávy standardního výstupu: Attachments: - - + Přílohy: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + V {0} nejsou dostupné žádné testy. Přesvědčte se, že nainstalované nástroje zjišťování testů, moduly provádění, nastavení verzí platformy a rozhraní jsou vhodné a zkuste to znova. @@ -867,34 +750,29 @@ Skipped - - + Přeskočeno Discovery failed for given sources. Exception : {0} - - + Zjišťování pro dané zdroje selhalo. Výjimka: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> ID nadřazeného procesu, který je odpovědný za spuštění aktuálního procesu The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + Argument --ParentProcessId|/ParentProcessId vyžaduje ID procesu, které je celočíselné. Zadejte ID nadřazeného procesu, který spustil tento proces. Arguments: - - + Argumenty: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<cesta k protokolu souboru> Povolit protokoly pro testovací platformu Protokoly se zapisují do zadaného souboru. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Zadaný soubor {0} je jen pro čtení. Timeout to connect or process request for DesignModeClient on port: {0} Časový limit k propojení nebo zpracování žádosti pro DesignModeClient na portu: {0} - - + Not Run Nespuštěno - - + RunSettings arguments: @@ -942,14 +816,12 @@ Argumenty k předání konfigurací runsettings prostřednictvím příkazového řádku. Argumenty je možné zadat jako dvojici název-hodnota ve formě [název]=[hodnota] po -- . Po -- následuje mezera. K oddělení více dvojic [název]=[hodnota] použijte mezeru. Další informace o podpoře argumentů RunSettings: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Nejméně jedno z nastavení Runsettings obsahuje neplatný token - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory Na zadané cestě se vytvoří adresář pro výsledky testů, pokud ještě neexistuje. Příklad: /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Parametr /ResultsDirectory vyžaduje hodnotu určující, kam se výsledky testů uloží. Příklad: /ResultsDirectory:c:\MůjAdresářVýsledkůTestů - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Cesta {0} zadaná v ResultsDirectory není platná. Chyba: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process Příznak /InIsolation je zastaralý. Testy se vždy spouští v samostatném procesu. - - + Logging Vstest Diagnostics in file: {0} Protokolování diagnostiky Vstest v souboru: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> Povolit kolekci dat pro testovací běh. Další informace: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Popisný název kolekce dat {0} není platný. Kolekce dat se bude ignorovat. - - + Debug Traces Messages: Zprávy trasování ladění: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Příklad: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Testovací běh se přerušil. - - + Test Run Canceled. Testovací běh se zrušil. - - + Error opening response file '{0}' Chyba při otevírání souboru odpovědí {0} - - + @<file> Read response file for more options. @<file> Načte další možnosti ze souboru odpovědí. - - + Total tests: Unknown Celkový počet testů: neznámý - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Kromě toho se cesta k adaptérům testů dá zadat pomocí příkazu /TestAdapterPath. Příklad: /TestAdapterPath:<cesta_k_vlastním_adaptérům>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. Příkaz /UseVsixExtensions je zastaralý. Použijte místo něj prosím příkaz /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Příklad: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" není podporován, pokud je testovací běh nakonfigurován pomocí nastavení testů. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Kolekce dat jiné než Pokrytí kódu a Microsoft Fakes konfigurované prostřednictvím nastavení běhu nejsou podporované s vloženým nastavením testů. Další informace viz https://aka.ms/vstest-configure-datacollector. Nastavení běhu: {0} - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Změní předponu úrovně diagnostiky pro protokolovací nástroj konzoly tak, jak je uvedeno níže. Příklad: /logger:console;prefix=<výchozí hodnota je false> Další informace o protokolovacím nástroji konzoly: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Shromažďování výpisů stavu systému pomocí možnosti CollectDump pro Blame se pro tuto platformu nepodporuje. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Zadaný parametr blame {0} není platný. Tento parametr se bude ignorovat. - - + Diag file path '{0}' is not valid. Cesta k souboru diag {0} není platná. - - + Blame argument '{0}' is not valid. Argument blame {0} není platný. - - + Diag argument '{0}' is not valid. Argument diag {0} není platný. - - + Logger argument '{0}' is not valid. Argument logger {0} není platný. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Rozhraní Framework35 není podporováno. Pro projekty, které cílí na rozhraní .Net Framework 3.5, bude test spuštěn v „režimu kompatibility“ CLR 4.0. - - + Test run in progress Probíhá testovací běh - - + Total tests: {0} Celkový počet testů: {0} - - + Failed: {0} Neúspěšné: {0} - - + Passed: {0} Úspěšné: {0} - - + Skipped: {0} Přeskočené: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. Argument {0} není platný. Pokud si chcete zobrazit seznam platných argumentů, použijte prosím možnost /help. - - + A total of {0} test files matched the specified pattern. Celkový počet testovacích souborů, které odpovídají zadanému vzoru: {0} - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") Argument parametru testovacího běhu {0} není platný. Použijte prosím formát uvedený níže. Formát: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Shromažďování výpisů stavu systému při zablokování pomocí možnosti CollectDump s TestTimeout pro Blame se pro tuto platformu nepodporuje. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - Neúspěšné: {1}, Úspěšné: {2}, Přeskočeno: {3}, Celkem: {4}, Doba trvání: {5} - - + None Žádné - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Příklad: -e:PROMENNA1=HODNOTA1 -e:JINA_PROMENNA="HODNOTA S MEZERAMI" -e:JINA_PROMENNA="HODNOTA;oddělená;středníky" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. Proměnná prostředí {0} se už definovala, ale přepsal ji argument -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.de.xlf b/src/vstest.console/Resources/xlf/Resources.de.xlf index fdd4077ae8..9f0d8d9f23 100644 --- a/src/vstest.console/Resources/xlf/Resources.de.xlf +++ b/src/vstest.console/Resources/xlf/Resources.de.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + "{0}" wurde nicht gefunden. The following Test Discovery Add-Ins are available: - - + Die folgenden Testermittlungs-Add-Ins sind verfügbar: The following Test Execution Add-Ins are available: - - + Die folgenden Testausführungs-Add-Ins sind verfügbar: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Die folgenden Testprotokollierungs-Add-Ins sind verfügbar: @@ -44,8 +39,7 @@ Error: {0} - - + Fehler: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Der Parameter "{0}" sollte nur ein Mal angegeben werden. Exception occurred when instantiating extension '{0}': {1} - - + Ausnahme beim Instanziieren der Erweiterung "{0}": {1} The following Tests are available: - - + Die folgenden Tests sind verfügbar: Unrecognized parameter "{0}". - - + Unbekannter Parameter "{0}". The test source file "{0}" provided was not found. - - + Die angegebene Testquelldatei "{0}" wurde nicht gefunden. 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. Information: {0} - - + Informationen: {0} Warning: {0} - - + Warnung: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Zeigt diese Syntaxmeldung an. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Testausführungs-Befehlszeilentool Version {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<URI/Anzeigename für Protokollierung> Geben Sie eine Protokollierung für Testergebnisse an. Um Ergebnisse beispielsweise in einer Visual Studio-Testergebnisdatei (TRX) zu protokollieren, verwenden Sie /logger:trx[;LogFileName=<Standardmäßig eindeutiger Dateiname>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Beschreibung: Führt Tests aus den angegebenen Dateien aus. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Syntax: vstest.console.exe [Argumente] [Optionen] [[--] <RunSettings-Argumente>...]] No test source files were specified. - - + Es wurden keine Testquelldateien angegeben. No arguments were specified. - - + Es wurden keine Argumente angegeben. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Hiermit führen Sie Tests über die angegebenen Dateien oder das Platzhaltermuster aus. Trennen Sie mehrere Testdateinamen oder Muster durch Leerzeichen. Legen Sie die Ausführlichkeit der Konsolenprotokollierung auf "detailed" fest, um übereinstimmende Testdateien anzuzeigen. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Die folgende Einstellungenanbieter-Add-Ins sind verfügbar: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Einstellungsdatei> Einstellungen für die Ausführung der Tests. The /Settings parameter requires a settings file to be provided. - - + Für den Parameter "/Settings" muss eine Einstellungsdatei angegeben werden. The Settings file '{0}' could not be found. - - + Die Einstellungsdatei "{0}" wurde nicht gefunden. Test Run Failed. - - + Fehler beim Testlauf. Test Run Successful. - - + Der Testlauf war erfolgreich. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + Das Argument "{0}" wird im Befehl "InIsolation" nicht erwartet. Geben Sie den Befehl ohne das Argument an (Beispiel: vstest.console.exe myTests.dll /InIsolation), und versuchen Sie es erneut. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Der /UseVsixExtensions-Parameter erfordert einen Wert. Wenn TRUE, werden die installierten VSIX-Extensions (falls vorhanden) im Testlauf verwendet. Wenn FALSE, werden sie ignoriert. Beispiel: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + Das Argument "{0}" wird im Befehl "UseVsixExtensions" nicht erwartet. Geben Sie den Befehl mit der Angabe an, ob die VSIX-Extensions verwendet oder übersprungen werden sollen (Beispiel: vstest.console.exe myTests.dll /UseVsixExtensions:true), und versuchen Sie es erneut. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + /InIsolation/InIsolation Führt die Tests in einem isolierten Prozess aus. Auf diese Weise ist es unwahrscheinlicher, dass der Prozess "vstest.console.exe" bei einem Fehler in den Tests beendet wird. @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Bewirkt, dass der Prozess "vstest.console.exe" die installierten VSIX-Extensions (sofern vorhanden) im Testlauf verwendet oder überspringt. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + Das Argument "/BatchSize" erfordert die Größe des Batches. Beispiel: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Ungültige Batchgröße {0}. Die Batchgröße muss größer als null sein. Beispiel: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Zum Ausführen von Tests: >vstest.console.exe tests.dll Zum Ausführen von Tests mit zusätzlichen Einstellungen wie Datensammlern: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + / ListDiscoverers Listet die installierten Testdiscoverer auf. /ListExecutors Lists installed test executors. - - + / ListExecutors Listet die installierten Testexecutors auf. /ListLoggers Lists installed test loggers. - - + / ListLoggers Listet die installierten Testprotokollierungen auf. /ListSettingsProviders Lists installed test settings providers. - - + / ListSettingsProviders Listet die installierten Testeinstellungenanbieter auf. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<Dateiname> Listet alle gefundenen Tests aus dem angegebenen Testcontainer auf. Time elapsed : - - + Verstrichene Zeit: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + Das /Tests-Argument erfordert mindestens einen bestimmten Testnamen oder seine Teilzeichenfolgen. Beispiele: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Insgesamt {0} Tests wurden ermittelt, aber kein Test stimmt mit den angegebenen Auswahlkriterien ({1}) überein. Verwenden Sie die richtigen Werte, und versuchen Sie es erneut. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Der Isolationsmodus wird zum Ausführen der Tests verwendet, weil Adapter für diagnostische Daten in den "runsettings" aktiviert wurden. Verwenden Sie den Parameter "/inIsolation", um diese Warnung zu unterdrücken. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Der Isolationsmodus wird zum Ausführen der Komponententests für Windows Store-Apps verwendet. Verwenden Sie den Parameter "/inIsolation", um diese Warnung zu unterdrücken. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Adapter für diagnostische Daten werden beim Ausführen von Komponententests für Windows Store-Apps nicht unterstützt. Entfernen Sie die Einstellungen für den Adapter für diagnostische Daten aus den Einstellungen. FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + Unterstützte Dateitypen: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + Standard-Executor-URI: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Ungültiger Plattformtyp: {0}. Gültige Plattformtypen sind x86, x64 und Arm. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + Für das /Platform-Argument muss der Zielplattformtyp für den Testlauf angegeben werden. Beispiel: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Plattformtyp> Zielplattformarchitektur für die Testausführung. Gültige Werte sind x86, x64 und ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Der Isolationsmodus wird zum Ausführen von Tests gemäß den Einstellungen der effektiven Plattform {0} und von .NET Framework {1} für den Testlauf verwendet. Verwenden Sie den /inIsolation-Parameter, um diese Warnung zu unterdrücken. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Frameworkversion> Die .NET-Framework-Zielversion für die Testausführung. Gültige Werte sind ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" usw. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + Das /Framework-Argument erfordert die .NET Framework-Zielversion für den Testlauf. Beispiel: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Ungültige .NET Framework-Version: {0}. Geben Sie den vollständigen Namen von TargetFramework an (Beispiel: .NETCoreApp,Version=v2.0). Weitere unterstützte .NET Framework-Versionen sind "Framework40", "Framework45", "FrameworkCore10" und "FrameworkUap10". Could not start test run for unit tests for Windows Store app: {0}. - - + Der Testlauf für Komponententests für die Windows Store-App konnte nicht gestartet werden: {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Ausdruck> Führt Tests aus, die mit dem angegebenen Ausdruck übereinstimmen. <Ausdruck> entspricht dem Format <Eigenschaft>Operator<Wert>[|&<Ausdruck>], @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + Für das Argument /TestCaseFilter ist der Filterwert erforderlich. Filterwert kann von folgendem Typ sein: <Eigenschaft>=<Wert>. Beispiele: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Das Argument "/TestCaseFilter" kann nicht mit "/Tests" angegeben werden. Das Filtern von Testfällen ist nicht anwendbar, wenn Tests angegeben werden. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} wurde für {1}/{2} erstellt. Den in einem Testlauf angegebenen Testassemblys muss ein .NET-Zielframework und eine Zielplattform gemeinsam sein. Only one app package (.appx file) can be specified for running tests. - - + Zum Ausführen von Tests kann nur ein App-Paket (APPX-Datei) angegeben werden. Starting test discovery, please wait... - - + Die Testermittlung wird gestartet, bitte warten... Starting test execution, please wait... - - + Die Testausführung wird gestartet, bitte warten... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + Das Lesen der Einstellungen des Adapters für diagnostische Daten hat eine ausgeführte "{0}" ausgelöst. Alle Adapter für diagnostische Daten werden in diesem Testlauf übersprungen. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Aktiviert den Datensammler "CodeCoverage" für den Testlauf. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + Das Argument "{0}" wird im Befehl "EnableCodeCoverage" nicht erwartet. Geben Sie den Befehl ohne das Argument an (Beispiel: vstest.console.exe myTests.dll /EnableCodeCoverage), und versuchen Sie es erneut. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + Das App-Paket "{0}" weist keinen Testexecutor-Einstiegspunkt auf. Erstellen Sie zum Ausführen von Komponententests für Windows Store-Apps ein App-Paket mithilfe des Komponententest-Bibliotheksprojekts der Windows Store-App. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Code Coverage ist für Windows Store-Apps nicht verfügbar. Die Code Coverage-Analyse wird für diesen Testlauf übersprungen. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Insgesamt {0} Tests wurden ermittelt, aber einige Tests stimmen nicht mit den angegebenen Auswahlkriterien ({1}) überein. Verwenden Sie die richtigen Werte, und versuchen Sie es erneut. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Hierdurch verwendet der Prozess "vstest.console.exe" im Testlauf benutzerdefinierte Testadapter aus einem angegeben Pfad (soweit vorhanden). @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Der /TestAdapterPath-Parameter erfordert einen Wert. Dabei handelt es sich um den Pfad eines Speicherorts mit benutzerdefinierten Testadaptern. Beispiel: /TestAdapterPath:c:\MeineBenutzerdefiniertenAdapter The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Der in "TestAdapterPath" angegebene Pfad "{0}" ist ungültig. Fehler: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Der angegebene benutzerdefinierte Testadapter-Suchpfad wurde nicht gefunden. Geben Sie einen gültigen Pfad an, und versuchen Sie es erneut. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Der in "TestAdapterPath" angegebene Pfad "{0}" enthält keine Testadapter. Geben Sie einen gültigen Pfad an, und versuchen Sie es erneut. Could not start test run for the tests for Windows Phone app: {0}. - - + Der Testlauf für die Tests für die Windows Phone-App konnte nicht gestartet werden: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Der Isolationsmodus wird zum Ausführen der Komponententests für Windows Phone-Apps verwendet. Verwenden Sie den Parameter "/inIsolation", um diese Warnung zu unterdrücken. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Code Coverage ist für Windows Phone-Apps nicht verfügbar. Die Code Coverage-Analyse wird für diesen Testlauf übersprungen. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Adapter für diagnostische Daten werden beim Ausführen von Komponententests für Windows Phone-Apps nicht unterstützt. Entfernen Sie die Einstellungen für den Adapter für diagnostische Daten aus den Einstellungen. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + Das App-Paket "{0}" weist keinen Testexecutor-Einstiegspunkt auf. Erstellen Sie zum Ausführen von Komponententests für Windows Phone-Apps ein App-Paket mithilfe des Komponententest-Bibliotheksprojekts der Windows Phone-App. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Das Framework {0} wird zum Ausführen der Tests verwendet. Geben Sie /Framework:{1} an, um diese Warnung zu unterdrücken. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Es wurde kein Test in den angegebenen Testcontainern gefunden. Darüber hinaus unterstützt der Microsoft Windows Store-Komponententestadapter keine APPXBUNDLE-Dateien. Erstellen Sie eine APPX-Datei (legen Sie die Option "App-Bundle generieren" auf "Nie" fest), wenn Sie das App-Paket erstellen, und versuchen Sie es erneut. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Gibt an, dass die Tests parallel ausgeführt werden. Standardmäßig werden alle verfügbaren Kerne auf dem Computer verwendet. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + Das Argument "{0}" wird im Befehl "Parallel" nicht erwartet. Geben Sie den Befehl ohne das Argument an (Beispiel: vstest.console.exe myTests.dll /Parallel), und versuchen Sie es erneut. Cannot be null or empty - - + Darf nicht NULL oder leer sein. --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Port> Der Port für die Socketverbindung und das Empfangen von Ereignismeldungen. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + Das Argument "--Port|/Port" erfordert die Portnummer (Integerwert). Geben Sie den Port für die Socketverbindung und den Empfang von Ereignismeldungen an. Unable to find the assembly under test. Please make sure that the project is built. - - + Die aktuell getestete Assembly wurde nicht gefunden. Stellen Sie sicher, dass das Projekt erstellt wird. The Path {0} does not exist. - - + Der Pfad "{0}" ist nicht vorhanden. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<Buildbasispfad> Das Verzeichnis mit den temporären Ausgaben. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Konfiguration> Die Konfiguration, für die das Projekt erstellt wird, d. h. Debug/Release. The given configuration is invalid. - - + Die angegebene Konfiguration ist ungültig. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Ausgabe> Das Verzeichnis mit den auszuführenden Binärdateien. The BuildBasePath was not found, provide a valid path and try again. - - + Der BuildBasePath wurde nicht gefunden. Geben Sie einen gültigen Pfad ein, und versuchen Sie es erneut. The Output path was not found, provide a valid path and try again. - - + Der Ausgabepfad wurde nicht gefunden. Geben Sie einen gültigen Pfad ein, und versuchen Sie es erneut. Additional Information Messages: - - + Weitere Informationsmeldungen: Days - - + Tage Error Message: - - + Fehlermeldung: Total time: {0:0.0000} {1} - - + Gesamtzeit: {0:0.0000} {1} Hours - - + Stunden Could not find a test logger with URI or FriendlyName '{0}'. - - + Es wurde keine Testprotokollierung mit dem URI oder FriendlyName "{0}" gefunden. Minutes - - + Minuten Seconds - - + Sekunden Stack Trace: - - + Stapelverfolgung: Standard Error Messages: - - + Standardfehlermeldungen: Standard Output Messages: - - + Standardausgabemeldungen: Attachments: - - + Anlagen: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + In "{0}" ist kein Test verfügbar. Stellen Sie sicher, dass die installierten Test-Discoverer und -Executor und die Versionseinstellungen für Plattform und Framework richtig sind, und wiederholen Sie den Vorgang. @@ -867,34 +750,29 @@ Skipped - - + Übersprungen Discovery failed for given sources. Exception : {0} - - + Fehler bei der Ermittlung für die angegebenen Quellen. Ausnahme: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ÜbergeordneteProzess-ID> Die Prozess-ID des übergeordneten Prozesses, der für das Starten des aktuellen Prozesses zuständig ist. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + Das Argument "--ParentProcessId|/ParentProcessId" erfordert die Prozess-ID (Integerwert). Geben Sie die Prozess-ID des übergeordneten Prozesses an, der diesen Prozess gestartet hat. Arguments: - - + Argumente: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Pfad zur Protokolldatei> Aktivieren Sie die Protokolle für die Testplattform. Protokolle werden in die bereitgestellte Datei geschrieben. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Die angegebene Datei "{0}" ist schreibgeschützt. Timeout to connect or process request for DesignModeClient on port: {0} Timeout zum Herstellen einer Verbindung oder zum Verarbeiten von Anfragen für DesignModeClient an Port: {0} - - + Not Run Nicht ausgeführt - - + RunSettings arguments: @@ -942,14 +816,12 @@ An die RunSettings-Konfigurationen über die Befehlszeile zu übergebende Argumente. Argumente werden unter Umständen als Name-Wert-Paar der Form [Name]=[Wert] nach "-- " übergeben. Beachten Sie das Leerzeichen nach "--". Trennen Sie mehrere Paare der Form [Name]=[Wert] mithilfe von Leerzeichen. Weitere Informationen zur Unterstützung von RunSettings-Argumenten: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Mindestens eine angegebene RUNSETTINGS-Datei enthält ein ungültiges Token - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory Das Testergebnisverzeichnis wird im angegebenen Pfad erstellt, wenn es noch nicht vorhanden ist. Beispiel: /ResultsDirectory:<Pfad_zu_Ergebnisverzeichnis> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Der Parameter "/ResultsDirectory" erfordert einen Wert, wobei die Testergebnisse gespeichert werden müssen. Beispiel: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Der in "ResultsDirectory" angegebene Pfad "{0}" ist ungültig. Fehler: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process Das Flag "/InIsolation" ist veraltet. Die Tests werden immer in einem separaten Prozess ausgeführt. - - + Logging Vstest Diagnostics in file: {0} Die Vstest-Diagnose wird in der Datei {0} protokolliert. - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<Datensammler-Anzeigename> Aktiviert den Datensammler für den Testlauf. Weitere Informationen finden Sie unter https://aka.ms/vstest-collect. - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Der benutzerfreundliche Name des Datensammlers "{0}" ist ungültig. Der Datensammler wird ignoriert. - - + Debug Traces Messages: Meldungen zu Debugablaufverfolgungen: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Beispiel: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Testlauf abgebrochen. - - + Test Run Canceled. Testlauf abgebrochen. - - + Error opening response file '{0}' Fehler beim Öffnen der Antwortdatei "{0}". - - + @<file> Read response file for more options. @<Datei> Antwortdatei mit weiteren Optionen lesen - - + Total tests: Unknown Gesamtzahl Tests: unbekannt - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Der Pfad zu Testadaptern kann zudem mit dem Befehl /TestAdapterPath angegeben werden. Beispiel: /TestAdapterPath:<Pfad_zu_benutzerdefinierten_Adaptern>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions wird demnächst eingestellt. Verwenden Sie stattdessen /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Beispiel: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" wird nicht unterstützt, wenn der Testlauf mithilfe von "testsettings" konfiguriert wurde. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Eingebettete Testeinstellungen werden – mit Ausnahme von Code Coverage und Microsoft Fakes – nicht für Datensammler unterstützt, die über Ausführungseinstellungen konfiguriert wurden. Weitere Informationen finden Sie unter https://aka.ms/vstest-configure-datacollector. Ausführungseinstellungen: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Ändern Sie das Präfix für die Diagnoseebene für die Konsolenprotokollierung wie folgt: Beispiel: /logger:console;prefix=<Standardmäßig "false"> Weitere Informationen zur Konsolenprotokollierung finden Sie hier: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Das Sammeln von Absturzabbildern über die Option "CollectDump" für "Blame" wird für diese Plattform nicht unterstützt. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Der mit "blame" angegebene blame-Parameter "{0}" ist ungültig. Dieser Parameter wird ignoriert. - - + Diag file path '{0}' is not valid. Der Diagnosedateipfad "{0}" ist ungültig. - - + Blame argument '{0}' is not valid. Das blame-Argument "{0}" ist ungültig. - - + Diag argument '{0}' is not valid. Das diag-Argument "{0}" ist ungültig. - - + Logger argument '{0}' is not valid. Das logger-Argument "{0}" ist ungültig. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 wird nicht unterstützt. Bei Projekten für Zielversion .NET Framework 3.5 wird der Test im CLR 4.0-Kompatibilitätsmodus ausgeführt. - - + Test run in progress Testlauf wird ausgeführt. - - + Total tests: {0} Gesamtzahl Tests: {0} - - + Failed: {0} Nicht bestanden: {0} - - + Passed: {0} Bestanden: {0} - - + Skipped: {0} Übersprungen: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. Das Argument "{0}" ist ungültig. Verwenden Sie die /help-Option, um die Liste gültiger Argumente anzuzeigen. - - + A total of {0} test files matched the specified pattern. Insgesamt {0} Testdateien stimmten mit dem angegebenen Muster überein. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") Das Parameterargument "{0}" für den Testlauf ist ungültig. Verwenden Sie das nachstehende Format. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Das Sammeln von Abbildern bei Reaktionsunfähigkeit über die Option "CollectDump" mit "TestTimeout" für "Blame" wird für diese Plattform nicht unterstützt. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0}: Fehler: {1}, erfolgreich: {2}, übersprungen: {3}, gesamt: {4}, Dauer: {5} - - + None Keine - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Beispiel: -e:VARIABLE1=WERT1 -e:WEITERE_VARIABLE="WERT MIT LEERZEICHEN" -e:WEITERE_VARIABLE="WERT;getrennt durch;Semikolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. Die Umgebungsvariable "{0}" wurde bereits definiert, sie wird jedoch durch das Argument "-Environment" überschrieben. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.es.xlf b/src/vstest.console/Resources/xlf/Resources.es.xlf index 463c895fb8..ab4f668b14 100644 --- a/src/vstest.console/Resources/xlf/Resources.es.xlf +++ b/src/vstest.console/Resources/xlf/Resources.es.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + No se encuentra '{0}'. The following Test Discovery Add-Ins are available: - - + Los siguientes complementos de detección de pruebas están disponibles: The following Test Execution Add-Ins are available: - - + Los siguientes complementos de ejecución de pruebas están disponibles: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Los siguientes complementos de registrador de pruebas están disponibles: @@ -44,8 +39,7 @@ Error: {0} - - + Error: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + El parámetro "{0}" debe proporcionarse solo una vez. Exception occurred when instantiating extension '{0}': {1} - - + Se produjo una excepción al crear una instancia de la extensión '{0}': {1} The following Tests are available: - - + Las siguientes pruebas están disponibles: Unrecognized parameter "{0}". - - + No se reconoce el parámetro "{0}". The test source file "{0}" provided was not found. - - + No se encuentra el archivo de código fuente de prueba "{0}" proporcionado. 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. Information: {0} - - + Información: {0} Warning: {0} - - + Advertencia: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Muestra este mensaje de uso. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Todos los derechos reservados. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Herramienta de línea de comandos de ejecución de pruebas de Microsoft(R), versión {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<URI del registrador/Nombre descriptivo> Especifica un registrador para los resultados de las pruebas. Por ejemplo, para registrar los resultados en un archivo de resultados de pruebas de Visual Studio (TRX) use /logger:trx[;LogFileName=<Valor predeterminado: nombre de archivo único>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Descripción: Ejecuta pruebas de los archivos especificados. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Uso: vstest.console.exe [Argumentos] [Opciones] [[--] <Argumentos de RunSettings>...]] No test source files were specified. - - + No se han especificado archivos de código fuente de prueba. No arguments were specified. - - + No se han especificado argumentos. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Ejecuta las pruebas del patrón con comodines o los archivos especificados. Separe varios patrones o nombres de archivo de prueba con espacios. Establezca el nivel de detalle del @@ -197,58 +174,49 @@ The following Settings Providers Add-Ins are available: - - + Los siguientes complementos de proveedores de configuración están disponibles: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<archivoConfiguración> Configuración que se usará cuando se ejecuten pruebas. The /Settings parameter requires a settings file to be provided. - - + El parámetro /Settings requiere que se proporcione un archivo de configuración. The Settings file '{0}' could not be found. - - + No se encuentra el archivo de configuración '{0}'. Test Run Failed. - - + No se pudo ejecutar la serie de pruebas. Test Run Successful. - - + La serie de pruebas se ejecutó correctamente. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + El argumento {0} no se espera en el comando 'InIsolation'. Especifique el comando sin este argumento (por ejemplo: vstest.console.exe myTests.dll /InIsolation) y vuelva a intentarlo. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + El parámetro /UseVsixExtensions requiere un valor. Si es “true”, se usarán las extensiones VSIX instaladas (si las hay) en la serie de pruebas. Si es “false”, se omitirá. Ejemplo: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + El argumento {0} no se espera en el comando 'UseVsixExtensions'. Especifique el comando indicando si deben usarse u omitirse las extensiones vsix (ejemplo: vstest.console.exe myTests.dll /UseVsixExtensions:true) y vuelva a intentarlo. @@ -256,8 +224,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Ejecuta las pruebas en un proceso aislado. De ese modo, es menos probable que el proceso vstest.console.exe se detenga ante un error en las pruebas, pero es posible que @@ -268,8 +235,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Hace que el proceso vstest.console.exe utilice u omita las extensiones VSIX instaladas (si las hay) en la serie de @@ -278,14 +244,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + El argumento /BatchSize requiere el tamaño del lote. Ejemplo: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Tamaño de lote no válido ({0}). El tamaño de lote debe ser mayor que cero. Ejemplo: /BatchSize:10 @@ -293,8 +257,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Para ejecutar pruebas: >vstest.console.exe tests.dll Para ejecutar pruebas con configuración adicional como recolectores de datos: @@ -303,67 +266,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Enumera los programas de detección de pruebas instalados. /ListExecutors Lists installed test executors. - - + /ListExecutors Enumera los ejecutores de pruebas instalados. /ListLoggers Lists installed test loggers. - - + /ListLoggers Enumera los registradores de pruebas instalados. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Enumera los proveedores de configuración de pruebas instalados. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<nombreArchivo Muestra todas las pruebas detectadas del contenedor de pruebas especificado. Time elapsed : - - + Tiempo transcurrido: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + El argumento /Tests requiere uno o varios nombres de pruebas específicas o sus subcadenas. Ejemplos: /Tests:MétodoDePrueba1, /Tests:MétodoDePrueba1,método2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Se ha detectado un total de {0} pruebas, pero ninguna de ellas coincide con los criterios de selección especificados ({1}). Use valores correctos y vuelva a intentarlo. , - - + , @@ -381,96 +335,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Se usará el modo de aislamiento para ejecutar las pruebas, ya que los adaptadores de datos de diagnóstico estaban habilitados en RunSettings. Use el parámetro de aislamiento /inIsolation para suprimir esta advertencia. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Se usará el modo de aislamiento para ejecutar pruebas unitarias para aplicaciones de la Tienda Windows. Use el parámetro /InIsolation para suprimir esta advertencia. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + No se admiten adaptadores de datos de diagnóstico cuando se ejecutan pruebas unitarias para aplicaciones de la Tienda Windows. Quite la configuración de adaptadores de datos de diagnóstico de la configuración. FriendlyName: {0} - - + Nombre descriptivo: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + Nombre de configuración: {0} Supported File Types: - - + Tipos de archivos admitidos: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + URI del ejecutor predeterminado: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Tipo de plataforma no válido: {0}. Los tipos de plataforma válidos son x86, x64 y ARM. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + El argumento /Platform requiere que se proporcione el tipo de plataforma de destino para la serie de pruebas. Ejemplo: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<tipoPlataforma> Arquitectura de la plataforma de destino que se usará para la ejecución de pruebas. Los valores válidos son x86, x64 y ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Se usará el modo de aislamiento para ejecutar las pruebas, según requiere la configuración de la plataforma efectiva ({0}) y .Net Framework ({1}) para la serie de pruebas. Use el parámetro /inIsolation para suprimir esta advertencia. @@ -478,8 +417,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Versión de Framework> Versión de .NET Framework de destino que se usará para la ejecución de pruebas. Los valores válidos son ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0", etc. @@ -487,20 +425,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + El argumento /Framework requiere la versión de .Net Framework de destino para la serie de pruebas. Ejemplo: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Versión de .Net Framework no válida: {0}. Proporcione el nombre completo de TargetFramework (ejemplo: .NETCoreApp,Version=v2.0). Otras versiones de .Net Framework admitidas son Framework40, Framework45, FrameworkCore10 y FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + No se puede iniciar la serie de pruebas unitarias para la aplicación de la Tienda Windows: {0}. @@ -513,8 +448,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expresión> Ejecuta pruebas que coinciden con la expresión dada. <Expresión> tiene el formato <propiedad>Operador<valor>[|&<Expresión>] @@ -529,78 +463,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + El argumento /TestCaseFilter requiere el valor del filtro. El valor del filtro puede ser del tipo <propiedad>=<valor>. Ejemplos: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + El argumento /TestCaseFilter no se puede especificar con /Tests. El filtrado de casos de prueba no es aplicable cuando se especifican pruebas. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} se ha creado para {1}/{2}. Los ensamblados de prueba especificados en una ejecución deben tener una versión de .Net Framework y una plataforma comunes. Only one app package (.appx file) can be specified for running tests. - - + Solo se puede especificar un paquete de aplicación (archivo .appx) para ejecutar pruebas. Starting test discovery, please wait... - - + Iniciando la detección de pruebas, espere... Starting test execution, please wait... - - + Iniciando la ejecución de pruebas, espere... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + Al leer la configuración de adaptador de datos de diagnóstico, se produjo una excepción al ejecutar '{0}'. Se omitirán todos los adaptadores de datos de diagnóstico en esta ejecución. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Habilita el recopilador de datos "CodeCoverage" para la serie de pruebas. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + El argumento {0} no se espera en el comando 'EnableCodeCoverage'. Especifique el comando sin este argumento (por ejemplo: vstest.console.exe myTests.dll /EnableCodeCoverage) y vuelva a intentarlo. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + El paquete de la aplicación '{0}' no tiene un punto de entrada de ejecutor de pruebas. Para ejecutar pruebas unitarias de aplicaciones de la Tienda Windows, cree un paquete de aplicación usando el proyecto Biblioteca de pruebas unitarias para aplicaciones de la Tienda Windows. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + La cobertura de código no está disponible para aplicaciones de la Tienda Windows. Se omitirá el análisis de cobertura de código para esta serie de pruebas. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Se ha detectado un total de {0} pruebas, pero algunas no coinciden con los criterios de selección especificados ({1}). Use valores correctos y vuelva a intentarlo. @@ -608,8 +530,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Permite que el proceso vstest.console.exe use adaptadores de pruebas personalizados de una ruta de acceso especificada (si existe alguna) en la serie de pruebas. @@ -617,68 +538,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + El parámetro /TestAdapterPath requiere un valor, que es la ruta de acceso de una ubicación que contiene adaptadores de prueba personalizados. Ejemplo: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + La ruta de acceso '{0}' especificada en 'TestAdapterPath' no es válida. Error: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + No se encuentra la ruta de búsqueda de adaptadores de prueba personalizados especificada. Proporcione una ruta de acceso válida y vuelva a intentarlo. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + La ruta de acceso '{0}' especificada en 'TestAdapterPath' no contiene ningún adaptador de prueba. Proporcione una ruta de acceso válida y vuelva a intentarlo. Could not start test run for the tests for Windows Phone app: {0}. - - + No se puede iniciar la serie de pruebas para la aplicación de Windows Phone: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Se usará el modo de aislamiento para ejecutar pruebas unitarias para aplicaciones de Windows Phone. Use el parámetro /InIsolation para suprimir esta advertencia. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + La cobertura de código no está disponible para aplicaciones de Windows Phone. Se omitirá el análisis de cobertura de código para esta serie de pruebas. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + No se admiten adaptadores de datos de diagnóstico cuando se ejecutan pruebas unitarias para aplicaciones de Windows Phone. Quite la configuración de adaptadores de datos de diagnóstico de la configuración. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + El paquete de aplicación '{0}' no tiene un punto de entrada de ejecutor de pruebas. Para ejecutar pruebas unitarias de aplicaciones de Windows Phone, cree un paquete de aplicación usando el proyecto Aplicación de pruebas unitarias para Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Se usará el marco {0} para ejecutar las pruebas. Especifique /Framework:{1} para suprimir esta advertencia. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + No se han encontrado pruebas en los contenedores de pruebas especificados. Además, el adaptador de pruebas unitarias de la Tienda Microsoft Windows no admite archivos .appxbundle. Cree un archivo .appx (establezca la opción Generar paquete de aplicaciones en Nunca) cuando cree el paquete de la aplicación y vuelva a intentarlo. @@ -686,8 +596,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Especifica que las pruebas se ejecuten en paralelo. De forma predeterminada, se pueden usar todos los núcleos disponibles @@ -696,166 +605,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + El argumento {0} no se espera en el comando 'Parallel'. Especifique el comando sin el argumento (ejemplo: vstest.console.exe myTests.dll /Parallel) y vuelva a intentarlo. Cannot be null or empty - - + No puede ser nulo ni estar vacío --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Puerto> Puerto para la conexión de socket y la recepción de mensajes de eventos. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + El argumento --Port|/Port requiere el número de puerto, que es un entero. Especifique el puerto para la conexión de socket y la recepción de mensajes de eventos. Unable to find the assembly under test. Please make sure that the project is built. - - + No se encuentra el ensamblado sometido a pruebas. Asegúrese de que el proyecto se ha compilado. The Path {0} does not exist. - - + La ruta de acceso {0} no existe. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<Ruta de acceso base de la compilación> Directorio que contiene las salidas temporales. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuración> Configuración para la que se ha compilado el proyecto, es decir, Debug/Release The given configuration is invalid. - - + La configuración dada no es válida. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Salida> Directorio que contiene los binarios que se van a ejecutar. The BuildBasePath was not found, provide a valid path and try again. - - + No se encuentra la ruta de acceso base de la compilación. Proporcione una ruta de acceso válida y vuelva a intentarlo. The Output path was not found, provide a valid path and try again. - - + No se encuentra la ruta de acceso de salida. Proporcione una ruta de acceso válida y vuelva a intentarlo. Additional Information Messages: - - + Mensajes con información adicional: Days - - + Días Error Message: - - + Mensaje de error: Total time: {0:0.0000} {1} - - + Tiempo total: {0:0.0000} {1} Hours - - + Horas Could not find a test logger with URI or FriendlyName '{0}'. - - + No se encuentra un registrador de pruebas con el URI o el nombre descriptivo '{0}'. Minutes - - + Minutos Seconds - - + Segundos Stack Trace: - - + Seguimiento de la pila: Standard Error Messages: - - + Mensajes de error estándar: Standard Output Messages: - - + Mensajes de salida estándar: Attachments: - - + Datos adjuntos: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + No hay ninguna prueba disponible en {0}. Asegúrese de que la configuración de detectores y ejecutores de pruebas, plataforma y versión de .NET Framework sea correcta e inténtelo de nuevo. @@ -870,34 +753,29 @@ Skipped - - + Omitidas Discovery failed for given sources. Exception : {0} - - + No se pudo llevar a cabo la detección en los orígenes dados. Excepción: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<idProcesoPrimario> Identificador del proceso primario responsable del inicio del proceso actual. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + El argumento --ParentProcessId|/ParentProcessId requiere el identificador del proceso, que es un entero. Especifique el identificador del proceso principal que inició este proceso. Arguments: - - + Argumentos: @@ -908,8 +786,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Ruta al archivo de registro> Habilita los registros para la plataforma de pruebas. Los registros se escriben en el archivo proporcionado. @@ -920,21 +797,18 @@ The file {0} provided is read only - - + El archivo {0} proporcionado es de solo lectura Timeout to connect or process request for DesignModeClient on port: {0} Tiempo de espera para conectar o procesar la solicitud para DesignModeClient en el puerto: {0} - - + Not Run Sin ejecutar - - + RunSettings arguments: @@ -945,14 +819,12 @@ Argumentos para pasar configuraciones de runsettings a través de la línea de comandos. Los argumentos se pueden especificar como un par nombre-valor en la forma [nombre]=[valor] después de "-- ". Observe que hay un espacio después de --. Use un espacio para separar varios pares de [nombre]=[valor]. Más información sobre la compatibilidad de argumentos de RunSettings: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Uno o varios runsettings proporcionados contienen un token no válido. - - + --ResultsDirectory|/ResultsDirectory @@ -961,52 +833,44 @@ --ResultsDirectory|/ResultsDirectory El directorio de resultados de pruebas se creará en la ruta de acceso especificada, si no existe. Ejemplo /ResultsDirectory:<Ruta al directorio de resultados> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory El parámetro /ResultsDirectory requiere un valor, donde deben guardarse los resultados de la prueba. Ejemplo: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} La ruta de acceso "{0}" especificada en "ResultsDirectory" no es válida. Error: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process La marca /InIsolation está en desuso. Las pruebas se ejecutan siempre en un proceso independiente - - + Logging Vstest Diagnostics in file: {0} Registrando diagnósticos de Vstest en el archivo: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<Nombre descriptivo del recopilador de datos> Habilita el recopilador de datos para la serie de pruebas. Más información aquí: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. El nombre descriptivo del recopilador de datos "{0}" no es válido. El recopilador de datos se ignorará. - - + Debug Traces Messages: Depurar mensajes de trazas: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1033,78 +897,66 @@ Ejemplo: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Serie de pruebas anulada. - - + Test Run Canceled. Serie de pruebas cancelada. - - + Error opening response file '{0}' Error al abrir el archivo de respuesta "{0}" - - + @<file> Read response file for more options. @<file> Leer el archivo de respuesta para ver más opciones. - - + Total tests: Unknown Pruebas totales: desconocido - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Además, la ruta de acceso a los adaptadores de pruebas se puede especificar con el comando /TestAdapterPath. Ejemplo /TestAdapterPath:<rutaAAdaptadoresPersonalizados>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions se está quedando obsoleto. Utilice /TestAdapterPath en su lugar. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Ejemplo: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" no se admite si la serie de pruebas está configurada mediante testsettings. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Los recopiladores de datos diferentes de Cobertura de código y Microsoft Fakes configurados a través de la configuración de ejecución no se admiten con la configuración de pruebas integrada. Consulte https://aka.ms/vstest-configure-datacollector para obtener más información. Configuración de ejecución: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1131,124 +983,104 @@ Cambie el prefijo de nivel de diagnóstico para el registrador de consola tal y como se muestra a continuación Ejemplo: /logger:console;prefix=<Valor predeterminado: "false"> Aquí encontrará más información sobre el registrador de consola: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. La recopilación de volcados de memoria mediante la opción CollectDump para Blame no se admite en esta plataforma. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. El parámetro blame especificado con blame, {0} no es válido. Se omitirá este parámetro. - - + Diag file path '{0}' is not valid. La ruta de acceso al archivo Diag "{0}" no es válida. - - + Blame argument '{0}' is not valid. El argumento de Blame "{0}" no es válido. - - + Diag argument '{0}' is not valid. El argumento de Diag "{0}" no es válido. - - + Logger argument '{0}' is not valid. El argumento de Logger "{0}" no es válido. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". No se admite Framework35. Para los proyectos que tienen como destino .NET Framework 3.5, la prueba se ejecutará en el "modo de compatibilidad" de CLR 4.0. - - + Test run in progress Serie de pruebas en curso - - + Total tests: {0} Pruebas totales: {0} - - + Failed: {0} Incorrecto: {0} - - + Passed: {0} Correcto: {0} - - + Skipped: {0} Omitido: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. El argumento {0} no es válido. Use la opción /help para comprobar la lista de argumentos válidos. - - + A total of {0} test files matched the specified pattern. {0} archivos de prueba en total coincidieron con el patrón especificado. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") El argumento del parámetro de la serie de pruebas "{0}" no es válido. Use el formato siguiente. Formato: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. La recopilación de volcados de memoria mediante la opción CollectDump con TestTimeout para Blame no se admite en esta plataforma. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - Con error: {1}, Superado: {2}, Omitido: {3}, Total: {4}, Duración: {5} - - + None Ninguno - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1267,14 +1099,12 @@ Ejemplo: -e:VARIABLE1=VALOR1 -e:OTRA_VARIABLE="VALOR CON ESPACIOS" -e:OTRA_VARIABLE="VALOR;separado por;puntoycoma" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. La variable de entorno "{0}" ya se definió, pero se reemplaza por el argumento -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.fr.xlf b/src/vstest.console/Resources/xlf/Resources.fr.xlf index bb62e8fc1e..1d4f8e8a90 100644 --- a/src/vstest.console/Resources/xlf/Resources.fr.xlf +++ b/src/vstest.console/Resources/xlf/Resources.fr.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}' introuvable. The following Test Discovery Add-Ins are available: - - + Les compléments de découverte de tests suivants sont disponibles : The following Test Execution Add-Ins are available: - - + Les compléments d'exécution de tests suivants sont disponibles : @@ -27,14 +24,12 @@ {0}: {1} - - + {0} : {1} The following Test Logger Add-Ins are available: - - + Les compléments suivants de type enregistreur d'événements de tests sont disponibles : @@ -44,8 +39,7 @@ Error: {0} - - + Erreur : {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Le paramètre "{0}" ne doit être fourni qu'une seule fois. Exception occurred when instantiating extension '{0}': {1} - - + Une exception s'est produite durant l'instanciation de l'extension '{0}' : {1} The following Tests are available: - - + Les tests suivants sont disponibles : Unrecognized parameter "{0}". - - + Paramètre non reconnu "{0}". The test source file "{0}" provided was not found. - - + Le fichier source de test "{0}" fourni est introuvable. 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é. Information: {0} - - + Informations : {0} Warning: {0} - - + Avertissement : {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Permet d'afficher ce message d'utilisation. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Tous droits réservés. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Outil en ligne de commande d'exécution de tests Microsoft (R), version {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<URI/nom convivial du journaliseur> Spécifiez un journaliseur pour les résultats des tests. Par exemple, pour journaliser des résultats dans un fichier de résultats des tests Visual Studio (TRX), utilisez /logger:trx[;LogFileName=<nom de fichier unique par défaut>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Description : exécute les tests à partir des fichiers spécifiés. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Utilisation : vstest.console.exe [Arguments] [Options] [[--] <arguments de RunSettings>...]] No test source files were specified. - - + Aucun fichier source de test n'a été spécifié. No arguments were specified. - - + Aucun argument n'a été spécifié. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Exécutez des tests à partir des fichiers ou des modèles de caractères génériques spécifiés. Séparez plusieurs modèles ou noms de fichiers de test par des espaces. Affectez à la verbosité du journaliseur de console la valeur Detailed pour voir les fichiers de test correspondants. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Les compléments suivants de type fournisseurs de paramètres sont disponibles : --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<fichier de paramètres> Paramètres à utiliser durant l'exécution des tests. The /Settings parameter requires a settings file to be provided. - - + Le paramètre /Settings nécessite un fichier de paramètres. The Settings file '{0}' could not be found. - - + Le fichier de paramètres '{0}' est introuvable. Test Run Failed. - - + Échec de la série de tests. Test Run Successful. - - + Série de tests réussie. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + L'argument {0} n'est pas attendu dans la commande 'InIsolation'. Spécifiez la commande sans l'argument (exemple : vstest.console.exe myTests.dll /InIsolation), puis réessayez. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Le paramètre /UseVsixExtensions nécessite une valeur. Si la valeur est 'true', les extensions VSIX installées (le cas échéant) sont utilisées dans la série de tests. Si la valeur est false, elles sont ignorées. Exemple : /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + L'argument {0} n'est pas attendu dans la commande 'UseVsixExtensions'. Spécifiez la commande indiquant si les extensions vsix doivent être utilisées ou ignorées (exemple : vstest.console.exe myTests.dll /UseVsixExtensions:true), puis réessayez. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Exécute les tests dans un processus isolé. Le processus vstest.console.exe est moins susceptible de s'arrêter en cas d'erreur durant les tests, mais ces derniers @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Le processus vstest.console.exe utilise ou ignore les extensions VSIX installées (le cas échéant) durant la série de tests. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + L'argument /BatchSize nécessite la taille du lot. Exemple : /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Taille de lot non valide {0}. La taille du lot doit être supérieure à zéro. Exemple : /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Pour exécuter les tests : >vstest.console.exe tests.dll Pour exécuter les tests avec des paramètres supplémentaires, par exemple des collecteurs de données : @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Liste les découvreurs de tests installés. /ListExecutors Lists installed test executors. - - + /ListExecutors Liste les exécuteurs de tests installés. /ListLoggers Lists installed test loggers. - - + /ListLoggers Liste les enregistreurs d'événements de tests installés. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Liste les fournisseurs de paramètres de test installés. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<nom de fichier> Liste tous les tests découverts dans le conteneur de tests spécifié. Time elapsed : - - + Temps écoulé : The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + L'argument /Tests nécessite un ou plusieurs noms de tests spécifiques ou leurs sous-chaînes. Exemples : /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Au total, {0} tests ont été découverts mais aucun d'entre eux ne correspond aux critères de sélection spécifiés ({1}). Utilisez les valeurs appropriées, puis réessayez. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Utilisation du mode Isolation pour exécuter les tests, car les adaptateurs de données de diagnostic ont été activés dans les paramètres d'exécution. Utilisez le paramètre /inIsolation pour supprimer cet avertissement. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Utilisation du mode Isolation pour exécuter les tests unitaires des applications du Windows Store. Utilisez le paramètre /InIsolation pour supprimer cet avertissement. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Les adaptateurs de données de diagnostic ne sont pas pris en charge durant l'exécution de tests unitaires pour les applications du Windows Store. Supprimez les adaptateurs de données de diagnostic des paramètres. FriendlyName: {0} - - + FriendlyName : {0} Uri: {0} - - + URI : {0} SettingName: {0} - - + SettingName : {0} Supported File Types: - - + Types de fichier pris en charge : {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + URI de l'exécuteur par défaut : {0} Uri: {0} - - + URI : {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Type de plateforme non valide : {0}. Les types de plateforme valides sont x86, x64 et ARM. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + Si vous utilisez l'argument /Platform, le type de plateforme cible de la série de tests doit être fourni. Exemple : /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<type de plateforme> Architecture de plateforme cible à utiliser pour l'exécution des tests. Les valeurs valides sont x86, x64 et ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Utilisation du mode Isolation pour exécuter les tests, conformément aux paramètres effectifs de la plateforme : {0} et du .Net Framework :{1} de la série de tests. Utilisez le paramètre /inIsolation pour supprimer cet avertissement. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<version du framework> Version cible du .Net Framework à utiliser pour l'exécution des tests. Les valeurs valides sont : ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0", etc. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + L'argument /Framework nécessite la version cible du .Net Framework pour la série de tests. Exemple : /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Version non valide du .Net Framework : {0}. Indiquez le nom complet de TargetFramework (exemple : .NETCoreApp,Version=v2.0). Les autres versions du .Net Framework prises en charge sont Framework40, Framework45, FrameworkCore10 et FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Impossible de démarrer la série de tests des tests unitaires pour une application du Windows Store : {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<expression> Permet d'exécuter les tests qui correspondent à l'expression indiquée. <Expression> est au format <property>Operator<value>[|&<Expression>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + L'argument /TestCaseFilter requiert la valeur du filtre. La valeur du filtre peut être de type <property>=<value>. Exemples : "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Impossible de spécifier l'argument /TestCaseFilter avec /Tests. Le filtrage des cas de test est non applicable quand des tests sont spécifiés. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} est généré pour {1}/{2}. Les assemblys de tests spécifiés dans une série doivent avoir une version cible du .Net Framework et une plateforme communes. Only one app package (.appx file) can be specified for running tests. - - + Un seul package d'application (fichier .appx) peut être spécifié pour l'exécution de tests. Starting test discovery, please wait... - - + Démarrage de la découverte de tests, patientez... Starting test execution, please wait... - - + Démarrage de l'exécution de tests, patientez... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + La lecture des paramètres de l'adaptateur de données de diagnostic a levé une exception durant l'exécution de '{0}'. Tous les adaptateurs de données de diagnostic seront ignorés dans cette série. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Active le collecteur de données 'CodeCoverage' pour la série de tests. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + L'argument {0} n'est pas attendu dans la commande 'EnableCodeCoverage'. Spécifiez la commande sans l'argument (exemple : vstest.console.exe myTests.dll /EnableCodeCoverage), puis réessayez. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + Le package d'application '{0}' n'a pas de point d'entrée pour l'exécuteur de tests. Pour exécuter les tests unitaires des applications du Windows Store, créez un package de l'application à l'aide du projet de bibliothèque de tests unitaires d'applications du Windows Store. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + La couverture du code n'est pas disponible pour les applications du Windows Store. L'analyse de la couverture du code a été ignorée pour cette série de tests. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Au total, {0} tests ont été découverts mais certains d'entre eux ne correspondent pas aux critères de sélection spécifiés ({1}). Utilisez les valeurs appropriées, puis réessayez. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Le processus vstest.console.exe utilise des adaptateurs de tests personnalisés à partir du chemin spécifié (le cas échéant) dans la série de tests. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Le paramètre /TestAdapterPath nécessite une valeur qui représente le chemin des adaptateurs de tests personnalisés. Exemple : /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Le chemin '{0}' spécifié dans 'TestAdapterPath' est non valide. Erreur : {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Le chemin de recherche fourni pour l'adaptateur de test personnalisé est introuvable. Indiquez un chemin valide, puis réessayez. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Le chemin '{0}' spécifié dans 'TestAdapterPath' ne contient aucun adaptateur de test. Indiquez un chemin valide, puis réessayez. Could not start test run for the tests for Windows Phone app: {0}. - - + Impossible de démarrer la série de tests pour les tests d'une application Windows Phone : {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Utilisation du mode Isolation pour exécuter les tests unitaires des applications Windows Phone. Utilisez le paramètre /InIsolation pour supprimer cet avertissement. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + La couverture du code n'est pas disponible pour les applications Windows Phone. L'analyse de la couverture du code a été ignorée pour cette série de tests. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Les adaptateurs de données de diagnostic ne sont pas pris en charge durant l'exécution de tests unitaires pour les applications Windows Phone. Supprimez les adaptateurs de données de diagnostic des paramètres. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + Le package d'application '{0}' n'a pas de point d'entrée pour l'exécuteur de tests. Pour exécuter les tests unitaires des applications Windows Phone, créez un package de l'application à l'aide du projet d'application de tests unitaires Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Utilisation du framework {0} pour exécuter les tests. Spécifiez /Framework:{1} pour supprimer cet avertissement. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Tests introuvables dans les conteneurs de tests spécifiés. De plus, l'Adaptateur de test unitaire Microsoft Windows Store ne prend pas en charge les fichiers .appxbundle. Créez un fichier .appx (affectez la valeur Jamais à l'option Générer l'ensemble d'applications) durant la création du package de l'application, puis réessayez. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Spécifie que les tests doivent être exécutés en parallèle. Par défaut, il est possible d'utiliser la totalité des cœurs disponibles sur la machine. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + L'argument {0} n'est pas attendu dans la commande 'Parallel'. Spécifiez la commande sans l'argument (exemple : vstest.console.exe myTests.dll /Parallel), puis réessayez. Cannot be null or empty - - + Ne peut pas avoir une valeur null ou être vide --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<port> Port de connexion du socket et de réception des messages d'événement. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + L'argument --Port|/Port nécessite le numéro de port, qui doit être indiqué sous forme d'entier. Spécifiez le port de connexion du socket et de réception des messages d'événement. Unable to find the assembly under test. Please make sure that the project is built. - - + L'assembly testé est introuvable. Vérifiez que le projet est généré. The Path {0} does not exist. - - + Le chemin {0} n'existe pas. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<chemin de base de la build> Répertoire contenant les sorties temporaires. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<configuration> Configuration pour laquelle le projet est généré. Exemple : Debug/Release The given configuration is invalid. - - + La configuration indiquée est non valide. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<sortie> Répertoire contenant les fichiers binaires à exécuter. The BuildBasePath was not found, provide a valid path and try again. - - + BuildBasePath est introuvable. Fournissez un chemin valide, puis réessayez. The Output path was not found, provide a valid path and try again. - - + Le chemin associé à Output est introuvable. Fournissez un chemin valide, puis réessayez. Additional Information Messages: - - + Messages d'informations supplémentaires : Days - - + Jours Error Message: - - + Message d'erreur : Total time: {0:0.0000} {1} - - + Durée totale : {0:0.0000} {1} Hours - - + Heures Could not find a test logger with URI or FriendlyName '{0}'. - - + Impossible de localiser un enregistreur d'événements de tests ayant pour URI ou FriendlyName '{0}'. Minutes - - + Minutes Seconds - - + Secondes Stack Trace: - - + Arborescence des appels de procédure : Standard Error Messages: - - + Messages d'erreur standard : Standard Output Messages: - - + Messages de sortie standard : Attachments: - - + Pièces jointes : {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + Aucun test disponible dans {0}. Vérifiez que les paramètres des découvreurs, des exécuteurs, de la plateforme et de la version de Framework installés sont appropriés, puis réessayez. @@ -867,34 +750,29 @@ Skipped - - + Ignoré Discovery failed for given sources. Exception : {0} - - + Échec de la découverte pour les sources indiquées. Exception : {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<id du processus parent> ID de processus du processus parent chargé de lancer le processus actuel. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + L'argument --ParentProcessId|/ParentProcessId nécessite l'ID de processus, qui doit être indiqué sous forme d'entier. Spécifiez l'ID de processus du processus parent qui a lancé ce processus. Arguments: - - + Arguments : @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<chemin du fichier journal> Permet d'activer les journaux pour la plateforme de test. Les journaux sont écrits dans le fichier fourni. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Le fichier {0} fourni est en lecture seule Timeout to connect or process request for DesignModeClient on port: {0} Délai expiré pour se connecter ou traiter la requête pour DesignModeClient sur le port : {0} - - + Not Run Pas exécuté - - + RunSettings arguments: @@ -942,14 +816,12 @@ Arguments pour passer des configurations runsettings via la ligne de commande. Les arguments peuvent être spécifiés comme paire nom-valeur sous la forme [nom]=[valeur] après "-- ". Notez l'espace après --. Utilisez un espace pour séparer plusieurs [nom]=[valeur]. Plus d'informations sur la prise en charge des arguments RunSettings : https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Un ou plusieurs paramètres d'exécution fournis contiennent un jeton non valide - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory Le répertoire des résultats des tests est créé dans le chemin spécifié, s'il n'existe pas. Exemple : /ResultsDirectory:<chemin du répertoire des résultats> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Le paramètre /ResultsDirectory nécessite une valeur, où les résultats des tests doivent être enregistrés. Exemple : /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Le chemin '{0}' spécifié dans 'ResultsDirectory' est non valide. Erreur : {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process L'indicateur /InIsolation est déprécié. Les tests sont toujours exécutés dans un processus distinct - - + Logging Vstest Diagnostics in file: {0} Journalisation des diagnostics Vstest dans le fichier : {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<nom convivial du collecteur de données> Active le collecteur de données pour la série de tests. Plus d'informations ici : https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Le nom convivial du collecteur de données '{0}' n'est pas valide. Le collecteur de données est ignoré. - - + Debug Traces Messages: Déboguer les messages de traces : - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Exemple : /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Série de tests abandonnée. - - + Test Run Canceled. Série de tests annulée. - - + Error opening response file '{0}' Erreur au moment de l'ouverture du fichier réponse '{0}' - - + @<file> Read response file for more options. @<fichier> Consultez le fichier réponse pour plus d'options. - - + Total tests: Unknown Nombre total de tests : inconnu - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. De plus, vous pouvez spécifier le chemin des adaptateurs de tests à l'aide de la commande /TestAdapterPath. Exemple : /TestAdapterPath:<chemin d'adaptateurs personnalisés>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions est progressivement déprécié. Utilisez /TestAdapterPath à la place. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Exemple : /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" n'est pas pris en charge si la série de tests est configurée avec testsettings. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Les collecteurs de données autres que la couverture du code et Microsoft Fakes configurés via les paramètres d'exécution ne sont pas pris en charge avec les paramètres de test incorporés. Pour plus d'informations, consultez https://aka.ms/vstest-configure-datacollector. Paramètres d'exécution : {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Change le préfixe du niveau de diagnostic pour le journaliseur de la console, comme indiqué ci-dessous Exemple : /logger:console;prefix=<"false" par défaut> En savoir plus sur le journaliseur de la console : https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. La collecte des vidages sur incident à l'aide de l'option CollectDump pour Blame n'est pas prise en charge pour cette plateforme. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Le paramètre blame spécifié avec blame, {0} n'est pas valide. Ce paramètre est ignoré. - - + Diag file path '{0}' is not valid. Le chemin du fichier Diag '{0}' n'est pas valide. - - + Blame argument '{0}' is not valid. L'argument blame '{0}' n'est pas valide. - - + Diag argument '{0}' is not valid. L'argument diag '{0}' n'est pas valide. - - + Logger argument '{0}' is not valid. L'argument logger '{0}' n'est pas valide. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 n'est pas pris en charge. Pour les projets ciblant .NET Framework 3.5, le test s'exécutera dans CLR 4.0 en « mode de compatibilité ». - - + Test run in progress Série de tests en cours - - + Total tests: {0} Nombre total de tests : {0} - - + Failed: {0} Non réussi(s) : {0} - - + Passed: {0} Réussi(s) : {0} - - + Skipped: {0} Ignoré(s) : {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. L’argument {0} n'est pas valide. Utilisez l'option /help pour vérifier la liste des arguments valides. - - + A total of {0} test files matched the specified pattern. Au total, {0} fichiers de test ont correspondu au modèle spécifié. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") L'argument de paramètre de série de tests '{0}' est non valide. Utilisez le format ci-dessous. Format : TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. La collecte des vidages sur blocage par l'option CollectDump avec TestTimeout pour Blame n'est pas prise en charge pour cette plateforme. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - échec : {1}, réussite : {2}, ignorée(s) : {3}, total : {4}, durée : {5} - - + None Aucun(e) - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Exemple : -e:VARIABLE1=VALEUR1 -e:AUTRE_VARIABLE="VALEUR AVEC ESPACES" -e:AUTRE_VARIABLE="VALEUR;séparée;par;des;points-virgules" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. La variable d'environnement '{0}' est déjà définie, mais elle est substituée par l'argument -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.it.xlf b/src/vstest.console/Resources/xlf/Resources.it.xlf index 96284e2abf..73f6ab3b3f 100644 --- a/src/vstest.console/Resources/xlf/Resources.it.xlf +++ b/src/vstest.console/Resources/xlf/Resources.it.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}' non è stato trovato. The following Test Discovery Add-Ins are available: - - + Sono disponibili i componenti aggiuntivi di individuazione dei test seguenti: The following Test Execution Add-Ins are available: - - + Sono disponibili i componenti aggiuntivi di esecuzione dei test seguenti: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Sono disponibili i componenti aggiuntivi di logger di test seguenti: @@ -44,8 +39,7 @@ Error: {0} - - + Errore: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Il parametro "{0}" deve essere specificato una sola volta. Exception occurred when instantiating extension '{0}': {1} - - + Si è verificata un'eccezione durante la creazione dell'istanza dell'estensione '{0}': {1} The following Tests are available: - - + Sono disponibili i test seguenti: Unrecognized parameter "{0}". - - + Il parametro "{0}" non è stato riconosciuto. The test source file "{0}" provided was not found. - - + Il file di origine test "{0}" specificato non è stato trovato. 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. Information: {0} - - + Informazioni: {0} Warning: {0} - - + Avviso: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Visualizza questo messaggio relativo alla sintassi. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Tutti i diritti sono riservati. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Strumento da riga di comando per l'esecuzione di test Microsoft (R) Versione {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<URI/Nome descrittivo logger> Specifica un logger per i risultati dei test. Ad esempio, per registrare risultati in un file di risultati dei test di Visual Studio (TRX), usare /logger:trx[;LogFileName=<impostazione predefinita: nome file univoco>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Descrizione: esegue test dai file specificati. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Utilizzo: vstest.console.exe [Argomenti] [Opzioni] [[--] <argomenti di RunSettings>...]] No test source files were specified. - - + Non sono stati specificati file di origine test. No arguments were specified. - - + Non sono stati specificati argomenti. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [NomiFileDiTest] Esegue i test corrispondenti ai file specificati o al carattere jolly. Separare più nomi di file di test o caratteri jolly con uno spazio. Impostare il livello di dettaglio del logger della console su dettagliato per visualizzare i file di test corrispondenti. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Sono disponibili i componenti aggiuntivi di provider di impostazioni seguenti: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<FileImpostazioni> Impostazioni da usare per l'esecuzione dei test. The /Settings parameter requires a settings file to be provided. - - + Con il parametro /Settings è necessario specificare un file di impostazioni. The Settings file '{0}' could not be found. - - + Il file di impostazioni '{0}' non è stato trovato. Test Run Failed. - - + L'esecuzione dei test non è riuscita. Test Run Successful. - - + L'esecuzione dei test è riuscita. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + L'argomento {0} non è previsto nel comando 'InIsolation'. Specificare il comando senza l'argomento, ad esempio: vstest.console.exe myTests.dll /InIsolation, quindi riprovare. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Con il parametro /UseVsixExtensions è richiesto un valore. Se è 'true', le estensioni VSIX eventualmente installate verranno usate nell'esecuzione dei test. Se è false, verranno ignorate. Esempio: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + L'argomento {0} non è previsto nel comando 'UseVsixExtensions'. Specificare il comando indicando se le estensioni vsix devono essere usate o ignorate, ad esempio vstest.console.exe myTests.dll /UseVsixExtensions:true, quindi riprovare. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Esegue i test in un processo isolato. In questo modo è meno probabile che il processo vstest.console.exe venga arrestato in caso di errore nei test, @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Determina se il processo vstest.console.exe usa o ignora le estensioni VSIX eventualmente installate nell'esecuzione dei test. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + Con l'argomento /BatchSize sono richieste le dimensioni del batch. Esempio: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Le dimensioni {0} del batch non sono valide. Devono essere maggiori di zero. Esempio: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Per eseguire test: >vstest.console.exe tests.dll Per eseguire test con impostazioni aggiuntive, quali agenti di raccolta dati: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Elenca gli agenti di individuazione test installati. /ListExecutors Lists installed test executors. - - + /ListExecutors Elenca gli executor di test installati. /ListLoggers Lists installed test loggers. - - + /ListLoggers Elenca i logger di test installati. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Elenca i provider di impostazioni test installati. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<Nome file> Elenca tutti i test individuati dal contenitore di test specificato. Time elapsed : - - + Tempo trascorso: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + Con l'argomento /Tests sono richiesti uno o più nomi di test specifici o relative sottostringhe. Esempi: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + In totale sono stati individuati {0} test, ma nessuno corrisponde ai criteri di selezione specificati ({1}). Usare i valori corretti e riprovare. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Per eseguire i test, verrà usata la modalità di isolamento perché gli adattatori dati di diagnostica sono stati abilitati in runsettings. Usare il parametro /inIsolation per non visualizzare più questo avviso. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Per eseguire gli unit test per le app di Windows Store, verrà usata la modalità di isolamento. Usare il parametro /InIsolation per non visualizzare più questo avviso. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Gli adattatori dati di diagnostica non sono supportati durante l'esecuzione di unit test per app di Windows Store. Rimuovere le impostazioni degli adattatori dati di diagnostica dalle impostazioni. FriendlyName: {0} - - + Nome descrittivo: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + Nome impostazione: {0} Supported File Types: - - + Tipi di file supportati: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + URI executor predefinito: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Tipo piattaforma non valido: {0}. Tipi di piattaforma validi: x86, x64 e ARM. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + L'argomento /Platform richiede il tipo di piattaforma di destinazione per l'esecuzione dei test. Ad esempio: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Tipo di piattaforma> Architettura della piattaforma di destinazione da usare per l'esecuzione dei test. Valori validi: x86, x64 e ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Per eseguire i test, verrà usata la modalità di isolamento in base a quanto specificato nelle impostazioni effettive di piattaforma {0} e .NET Framework {1} per l'esecuzione dei test. Usare il parametro /inIsolation per non visualizzare più questo avviso. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Versione framework> Versione di .NET Framework di destinazione da usare per l'esecuzione dei test. Valori validi: ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" e così via. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + Con l'argomento /Framework è richiesta la versione di .NET Framework di destinazione per l'esecuzione dei test. Esempio: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + La versione di .NET Framework {0} non è valida. Specificare il nome completo della versione di .NET Framework di destinazione ad esempio .NETCoreApp,Version=v2.0. Altre versioni di .NET Framework supportate: Framework40, Framework45, FrameworkCore10 e FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Non è stato possibile avviare l'esecuzione dei test per unit test per l'app di Windows Store: {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Espressione> Esegue test corrispondenti all'espressione specificata. <Espressione> è nel formato <proprietà>Operatore<valore>[|&<Espressione>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + L'argomento /TestCaseFilter richiede il valore di filtro. Il valore di filtro può essere di tipo <proprietà>=<valore>. Esempi: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Non è possibile specificare l'argomento /TestCaseFilter con /Tests. Il filtro dei test case non è applicabile quando si specificano test. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} è compilato per {1}/{2}. Gli assembly di test specificati in un'esecuzione devono disporre di una piattaforma e di un .NET Framework di destinazione comuni. Only one app package (.appx file) can be specified for running tests. - - + Per i test in esecuzione è possibile specificare un solo pacchetto dell'app (file con estensione appx). Starting test discovery, please wait... - - + Avvio dell'individuazione dei test in corso. Attendere... Starting test execution, please wait... - - + Avvio dell'esecuzione dei test in corso. Attendere... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + La lettura delle impostazioni dell'adattatore dati di diagnostica ha generato un oggetto '{0}' di esecuzione. Tutti gli adattatori dati di diagnostica verranno ignorati durante questa esecuzione. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Abilita l'agente di raccolta dati 'CodeCoverage' per l'esecuzione dei test. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + L'argomento {0} non è previsto nel comando 'EnableCodeCoverage'. Specificare il comando senza l'argomento, ad esempio: vstest.console.exe myTests.dll /EnableCodeCoverage, quindi riprovare. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + Il pacchetto dell'app '{0}' non contiene un punto di ingresso dell'executor di test. Per eseguire unit test per le app di Windows Store, creare il pacchetto dell'app usando il progetto Libreria unit test per app di Windows Store. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Il code coverage non è disponibile per le app di Windows Store. L'analisi del code coverage verrà ignorata per questa esecuzione dei test. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + In totale sono stati individuati {0} test, ma alcuni test non corrispondono ai criteri di selezione specificati ({1}). Usare i valori corretti e riprovare. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Determina se il processo vstest.console.exe usa adattatori di test personalizzati da un percorso eventualmente specificato nell'esecuzione dei test. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Con il parametro /TestAdapterPath è richiesto un valore, corrispondente al percorso di una posizione contenente adattatori di test personalizzati. Esempio: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Il percorso '{0}' specificato in 'TestAdapterPath' non è valido. Errore: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Il percorso di ricerca dell'adattatore di test personalizzato non è stato trovato. Specificare un percorso valido e riprovare. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Il percorso '{0}' specificato in 'TestAdapterPath' non contiene alcun adattatore di test. Specificare un percorso valido e riprovare. Could not start test run for the tests for Windows Phone app: {0}. - - + Non è stato possibile avviare l'esecuzione dei test per i test per l'app di Windows Phone: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Per eseguire gli unit test per le app di Windows Phone, verrà usata la modalità di isolamento. Usare il parametro /InIsolation per non visualizzare più questo avviso. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Il code coverage non è disponibile per le app di Windows Phone. L'analisi del code coverage verrà ignorata per questa esecuzione dei test. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Gli adattatori dati di diagnostica non sono supportati durante l'esecuzione di unit test per app di Windows Phone. Rimuovere le impostazioni degli adattatori dati di diagnostica dalle impostazioni. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + Il pacchetto dell'app '{0}' non contiene un punto di ingresso dell'executor di test. Per eseguire unit test per le app di Windows Phone, creare il pacchetto dell'app con il progetto App unit test di Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Per eseguire i test, verrà usato il framework {0}. Specificare /Framework:{1} per non visualizzare più questo avviso. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Non è stato trovato alcun test nei contenitori di test specificati. L'adattatore di unit test di Microsoft Windows Store, inoltre, non supporta i file con estensione appxbundle. Durante la creazione di un pacchetto dell'app, creare un file appx impostando l'opzione Genera il bundle dell'app su Mai, quindi riprovare. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Specifica che i test devono essere eseguiti in parallelo. Per impostazione predefinita, è possibile usare al massimo tutti i core disponibili in questo computer. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + L'argomento {0} non è previsto nel comando 'Parallel'. Specificare il comando senza l'argomento, ad esempio: vstest.console.exe myTests.dll /Parallel, quindi riprovare. Cannot be null or empty - - + Non può essere Null o vuoto --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Porta> Porta per la connessione socket e la ricezione dei messaggi dell'evento. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + Con l'argomento --Port|/Port è richiesto un numero di porta che corrisponde a un numero intero. Specificare la porta per la connessione socket e la ricezione dei messaggi dell'evento. Unable to find the assembly under test. Please make sure that the project is built. - - + L'assembly sottoposto a test non è stato trovato. Assicurarsi che il progetto sia compilato. The Path {0} does not exist. - - + Il percorso {0} non esiste. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<PercorsoBaseCompilazione> Directory che contiene gli output temporanei. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configurazione> Configurazione per cui viene compilato il progetto, ad esempio Debug/Release The given configuration is invalid. - - + La configurazione specificata non è valida. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Output> Directory contenente i file binari da eseguire. The BuildBasePath was not found, provide a valid path and try again. - - + Il percorso di base di compilazione non è stato trovato. Specificare un percorso valido e riprovare. The Output path was not found, provide a valid path and try again. - - + Il percorso di output non è stato trovato. Specificare un percorso valido e riprovare. Additional Information Messages: - - + Ulteriori messaggi informativi: Days - - + Giorni Error Message: - - + Messaggio di errore: Total time: {0:0.0000} {1} - - + Tempo totale: {0:0.0000} {1} Hours - - + Ore Could not find a test logger with URI or FriendlyName '{0}'. - - + Non è stato trovato alcun logger di test con URI o nome descrittivo '{0}'. Minutes - - + Minuti Seconds - - + Secondi Stack Trace: - - + Analisi dello stack: Standard Error Messages: - - + Messaggi di errore standard: Standard Output Messages: - - + Messaggi di output standard: Attachments: - - + Allegati: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + Non è disponibile alcun test in {0}. Verificare che le impostazioni delle versioni installate di piattaforma e framework, agenti di individuazione ed executor di test siano appropriate e riprovare. @@ -867,34 +750,29 @@ Skipped - - + Ignorato Discovery failed for given sources. Exception : {0} - - + L'individuazione non è riuscita per le origini specificate. Eccezione: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> ID del processo padre responsabile dell'avvio del processo corrente. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + Con l'argomento --ParentProcessId|/ParentProcessId è richiesto l'ID processo che corrisponde a un numero intero. Specificare l'ID del processo padre che ha avviato questo processo. Arguments: - - + Argomenti: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<percorso del file di log> Abilita i log per la piattaforma di test. I log vengono scritti nel file specificato. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Il file specificato {0} è di sola lettura Timeout to connect or process request for DesignModeClient on port: {0} Timeout per la connessione o l'elaborazione della richiesta relativa a DesignModeClient sulla porta: {0} - - + Not Run Non eseguito - - + RunSettings arguments: @@ -942,14 +816,12 @@ Argomenti per passare le configurazioni di runsettings tramite la riga di comando. È possibile specificare gli argomenti come coppia nome-valore in formato [nome]=[valore] dopo "-- ". Notare lo spazio dopo --. Usare uno spazio per separare più coppie [nome]=[valore]. Per altre informazioni sul supporto degli argomenti di RunSettings, vedere: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Uno o più file runsettings specificati contengono un token non valido - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory Se non esiste già, la directory dei risultati dei test verrà creata nel percorso specificato. Esempio: /ResultsDirectory:<percorsoDirectoryRisultati> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Con il parametro /ResultsDirectory è richiesto un valore, corrispondente alla directory in cui verranno salvati i risultati dei test. Esempio: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Il percorso '{0}' specificato in 'ResultsDirectory' non è valido. Errore: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process Il flag /InIsolation è deprecato. I test verranno sempre eseguiti in un processo separato - - + Logging Vstest Diagnostics in file: {0} Registrazione della diagnostica di Vstest nel file: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<Nome descrittivo agente di raccolta dati> Abilita l'agente di raccolta dati per l'esecuzione dei test. Per altre informazioni, vedere: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Il nome descrittivo '{0}' dell'agente di raccolta dati non è valido. L'agente di raccolta dati verrà ignorato. - - + Debug Traces Messages: Messaggi delle tracce di debug: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Esempio: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Esecuzione dei test interrotta. - - + Test Run Canceled. Esecuzione dei test annullata. - - + Error opening response file '{0}' Si è verificato un errore durante l'apertura del file di risposta '{0}' - - + @<file> Read response file for more options. @<file> Legge il file di risposta per altre opzioni. - - + Total tests: Unknown Totale test: sconosciuto - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. È anche possibile specificare il percorso degli adattatori di test con il comando /TestAdapterPath. Esempio: /TestAdapterPath:<percorsoAdattatoriPersonalizzati>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions verrà deprecato. Usare /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Esempio: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" non è supportato se l'esecuzione dei test viene configurata con testsettings. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Gli agenti di raccolta dati diversi da Code Coverage e Microsoft Fakes configurati tramite le impostazioni esecuzione test non sono supportati con impostazioni di test incorporate. Per altre informazioni, vedere https://aka.ms/vstest-configure-datacollector. Impostazioni esecuzione test: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Consente di cambiare il prefisso del livello di diagnostica per il logger di console come illustrato di seguito: Esempio: /logger:console;prefix=<impostazione predefinita: "false"> Per altre informazioni sul logger di console, vedere: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. L'opzione CollectDump per Blame non supporta la raccolta dei dump di arresto anomalo del sistema per questa piattaforma. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Il parametro di Blame specificato con Blame {0} non è valido e verrà ignorato. - - + Diag file path '{0}' is not valid. Il percorso '{0}' del file di Diag non è valido. - - + Blame argument '{0}' is not valid. L'argomento '{0}' di Blame non è valido. - - + Diag argument '{0}' is not valid. L'argomento '{0}' di Diag non è valido. - - + Logger argument '{0}' is not valid. L'argomento '{0}' di Logger non è valido. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 non è supportato. Per i progetti destinati a .NET Framework 3.5, i test verranno eseguiti nella modalità di compatibilità di CLR 4.0. - - + Test run in progress Esecuzione dei test in corso - - + Total tests: {0} Totale test: {0} - - + Failed: {0} Non superati: {0} - - + Passed: {0} Superati: {0} - - + Skipped: {0} Ignorati: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. L'argomento {0} non è valido. Usare l'opzione/help per verificare l'elenco di argomenti validi. - - + A total of {0} test files matched the specified pattern. Un totale di {0} file di test corrisponde al criterio specificato. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") L'argomento '{0}' del parametro di esecuzione dei test non è valido. Usare il formato seguente. Formato: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. L'opzione CollectDump con TestTimeout per Blame non supporta la raccolta dei dump di blocco per questa piattaforma. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - Non superati: {1}. Superati: {2}. Ignorati: {3}. Totale: {4}. Durata: {5} - - + None Nessuno - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Esempio: -e:VARIABILE1=VALORE1 -e:ALTRA_VARIABILE="VALORE CON SPAZI" -e:ALTRA_VARIABILE="VALORE;delimitato da;punti e virgola" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. La variabile di ambiente '{0}' è già stata definita, ma viene sostituita dall'argomento -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.ja.xlf b/src/vstest.console/Resources/xlf/Resources.ja.xlf index 37bc951f0e..ef2a0828e8 100644 --- a/src/vstest.console/Resources/xlf/Resources.ja.xlf +++ b/src/vstest.console/Resources/xlf/Resources.ja.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}' が見つかりません。 The following Test Discovery Add-Ins are available: - - + 次のテスト探索アドインを使用できます: The following Test Execution Add-Ins are available: - - + 次のテスト実行アドインを使用できます: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + 次のテスト ロガー アドインを使用できます: @@ -44,8 +39,7 @@ Error: {0} - - + エラー: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + パラメーター "{0}" は一度しか指定できません。 Exception occurred when instantiating extension '{0}': {1} - - + 拡張をインスタンス化しているときに例外が発生しました: '{0}': {1} The following Tests are available: - - + 次のテストを使用できます: Unrecognized parameter "{0}". - - + パラメーター "{0}" は認識されていません。 The test source file "{0}" provided was not found. - - + 指定されたテスト ソース ファイル "{0}" が見つかりませんでした。 The Test Logger URI '{0}' is not valid. The Test Logger will be ignored. - - + テスト ロガーの URI '{0}' は無効です。テスト ロガーは無視されます。 Information: {0} - - + 情報: {0} Warning: {0} - - + 警告: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help この使用方法に関するメッセージを表示します。 Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. All rights reserved. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Test Execution Command Line Tool Version {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<Logger Uri/FriendlyName> テスト結果のロガーを指定します。たとえば、結果のログを Visual Studio のテスト結果ファイル (TRX) に記録するには、/logger:trx[;LogFileName=<Defaults to unique file name>] を使用します @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + 説明: 指定されたファイルからテストを実行します。 @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + 使用法: vstest.console.exe [引数] [オプション] [[--] <RunSettings arguments>...]] No test source files were specified. - - + テスト ソース ファイルが指定されていません。 No arguments were specified. - - + 引数が指定されていません。 @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] 指定されたファイルまたはワイルド カード パターンからテストを実行します。複数のテスト ファイル名または パターンをスペースで区切ります。一致したテスト ファイルを表示するには、コンソール ロガーの詳細度を detailed に設定します。 @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + 次の設定プロバイダー アドインを使用できます: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Settings File> テストを実行する際に使用する設定です。 The /Settings parameter requires a settings file to be provided. - - + /Settings パラメーターには、設定ファイルを指定する必要があります。 The Settings file '{0}' could not be found. - - + 設定ファイル '{0}' が見つかりませんでした。 Test Run Failed. - - + テストの実行に失敗しました。 Test Run Successful. - - + テストの実行に成功しました。 Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + 'InIsolation' コマンドでは、引数 {0} は適切ではありません。引数なしでコマンドを指定し (例: vstest.console.exe myTests.dll /InIsolation)、もう一度お試しください。 The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + /UseVsixExtensions パラメーターに値を指定する必要があります。'true' を指定すると、インストール済みの VSIX 拡張機能 (ある場合) がテストの実行で使用されます。false を指定すると、これらは無視されます。例: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + 'UseVsixExtensions' コマンドでは、引数 {0} は適切ではありません。vsix 拡張機能を使用するのかスキップするのかを示すコマンドを指定し (例: vstest.console.exe myTests.dll /UseVsixExtensions:true)、もう一度お試しください。 @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation 分離プロセスでテストを実行します。これにより、vstest.console.exe プロセスがテスト時にエラーで停止する可能性は低くなりますが、 @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions これにより、テストの実行で vstest.console.exe プロセスによってインストール済みの VSIX 拡張機能 (ある場合) が使用またはスキップされます。 @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + /BatchSize 引数には、バッチのサイズが必要です。例: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + バッチ サイズ {0} は無効です。バッチ サイズには、0 より大きい値を指定してください。例: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + テストを実行する: >vstest.console.exe tests.dll テストをデータ コレクターなどの追加設定を指定して実行する: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers インストール済みのテスト探索プログラムを一覧表示します。 /ListExecutors Lists installed test executors. - - + /ListExecutors インストール済みのテスト実行プログラムを一覧表示します。 /ListLoggers Lists installed test loggers. - - + /ListLoggers インストール済みのテスト ロガーを一覧表示します。 /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders インストール済みのテスト設定プロバイダーを一覧表示します。 -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<ファイル名> 指定されたテスト コンテナーから、すべての探索されたテストを一覧表示します。 Time elapsed : - - + 経過時間: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + /Tests 引数には、1 つ以上の特定のテスト名またはその部分文字列が必要です。 例: /Tests:TestsMethod1、/Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + 合計 {0} 個のテストが検出されましたが、指定された選択条件 ({1}) に一致するテストはありません。適切な値を使用して、もう一度お試しください。 , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + 診断データ アダプターが実行設定で有効になっていたので、テストの実行に分離モードを使用しています。この警告が表示されないようにするには、/inIsolation パラメーターを使用します。 Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Windows ストア アプリの単体テストを実行するために、分離モードを使用しています。この警告が表示されないようにするには、/InIsolation パラメーターを使用します。 Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Windows ストア アプリの単体テストの実行時は、診断データ アダプターはサポートされません。設定から診断データ アダプターの設定を削除してください。 FriendlyName: {0} - - + 表示名: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + サポートされているファイルの種類: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + 既定の実行プログラムの URI: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + プラットフォームの種類が無効です: {0}。有効なプラットフォームの種類は、x86、x64、および Arm です。 The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + /Platform 引数には、テストの実行対象とするプラットフォームの種類を指定する必要があります。例: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Platform type> テストの実行に使用するターゲット プラットフォームのアーキテクチャです。 有効な値は、x86、x64、ARM です。 Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + テスト実行のための効果的なプラットフォーム: {0} および .Net Framework: {1} の設定で必要とされるため、テストの実行に分離モードを使用しています。この警告が表示されないようにするには、/inIsolation パラメーターを使用します。 @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Framework Version> テストの実行に使用する、.Net Framework のターゲット バージョン。 有効な値は ".NETFramework,Version=v4.5.1"、".NETCoreApp,Version=v1.0" などです。 @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + /Framework 引数には、テストの実行対象とする .Net Framework バージョンが必要です。例: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + .Net Framework バージョンが無効です: {0}。TargetFramework の完全な名前を指定してください (例: .NETCoreApp,Version=v2.0)。その他のサポートされる .Net Framework バージョンは Framework40、Framework45、FrameworkCore10、FrameworkUap10 です。 Could not start test run for unit tests for Windows Store app: {0}. - - + Windows ストア アプリの単体テストのテスト実行を開始できません: {0}。 @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expression> 指定された式と一致するテストを実行します。 <Expression> の形式は <property>演算子<value>[|&<Expression>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + /TestCaseFilter 引数には、フィルター値が必要です。 フィルター値は、<プロパティ>=<値> という型で指定できます。 例: "Priority=1"、"TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + /TestCaseFilter 引数を /Tests と共に指定することはできません。テストが指定されている場合、テスト ケースのフィルター処理は適用できません。 {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} は {1}/{2} 用にビルドされています。実行で指定されるテスト アセンブリは、対象とする .NET Framework およびプラットフォームを共通にする必要があります。 Only one app package (.appx file) can be specified for running tests. - - + 実行する複数のテストには、1 つのアプリ パッケージ (.appx ファイル) だけを指定できます。 Starting test discovery, please wait... - - + テスト探索を開始しています。お待ちください... Starting test execution, please wait... - - + テスト実行を開始しています。お待ちください... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + 診断データ アダプターの設定の読み取り中に実行中の '{0}' がスローされました。この実行では、すべての診断データ アダプターがスキップされます。 /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage テストの実行用にデータ コレクター 'CodeCoverage' を有効にします。 Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + 引数 {0} は、'EnableCodeCoverage' コマンドでは必要ではありません。引数なしでコマンドを指定し (例: vstest.console.exe myTests.dll /EnableCodeCoverage)、もう一度お試しください。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + アプリ パッケージ '{0}' に、テスト実行プログラムのエントリ ポイントがありません。Windows ストア アプリの単体テストを実行する場合は、Windows ストア アプリ単体テスト ライブラリ プロジェクトを使用して、アプリ パッケージを作成してください。 Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Windows ストア アプリではコード カバレッジを使用できません。このテスト実行ではコード カバレッジ分析はスキップされました。 A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + 合計 {0} 個のテストが検出されましたが、指定された選択条件 ({1}) に一致しないテストがあります。適切な値を使用して、もう一度お試しください。 @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath テストの実行で、vstest.console.exe プロセスが指定されたパス (ある場合) からのカスタム テスト アダプターを使用するようにします。 @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + /TestAdapterPath パラメーターには、値として、カスタム テスト アダプターがある場所のパスが必要です。例: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + 'TestAdapterPath' に指定されているパス '{0}' は無効です。エラー: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + カスタム テスト アダプターの指定された検索パスが見つかりませんでした。有効なパスを指定して、もう一度お試しください。 The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + 'TestAdapterPath' に指定されているパス '{0}' には、テスト アダプターがありません。有効なパスを指定して、もう一度お試しください。 Could not start test run for the tests for Windows Phone app: {0}. - - + Windows Phone アプリに対するテストのテスト実行を開始できません: {0}。 Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Windows Phone アプリの単体テストを実行するために、分離モードを使用しています。この警告が表示されないようにするには、/InIsolation パラメーターを使用します。 Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Windows Phone アプリではコード カバレッジを使用できません。このテスト実行ではコード カバレッジ分析はスキップされました。 Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Windows Phone アプリの単体テストの実行時は、診断データ アダプターはサポートされません。設定から診断データ アダプターの設定を削除してください。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + アプリ パッケージ '{0}' に、テスト実行プログラムのエントリ ポイントがありません。Windows Phone アプリの単体テストを実行する場合は、Windows Phone 単体テスト アプリ プロジェクトを使用して、アプリ パッケージを作成してください。 Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + フレームワーク {0} を使用してテストを実行します。この警告を表示しないようにするには、/Framework:{1} を指定します。 No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + 指定されたテスト コンテナーにテストが見つかりません。さらに、Microsoft Windows ストア単体テスト アダプターで .appxbundle ファイルがサポートされていません。アプリ パッケージの作成時に appx ([アプリ バンドルの生成] オプションを [しない] に設定) し、もう一度お試しください。 @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel テストを並列で実行するように指定します。既定では、 コンピューター上の使用可能なコア数まで使用できます。 @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + 引数 {0} は 'Parallel' コマンド内で使用できません。引数を使用せずにコマンドを指定して (例: vstest.console.exe myTests.dll /Parallel)、もう一度お試しください。 Cannot be null or empty - - + null または空にすることはできません。 --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Port> ソケット接続およびイベント メッセージを受信するためのポートです。 The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + --Port|/Port 引数には、整数であるポート番号を指定する必要があります。ソケット接続およびイベント メッセージ受信用のポートを指定してください。 Unable to find the assembly under test. Please make sure that the project is built. - - + テスト中のアセンブリが見つかりません。プロジェクトがビルドされたことをご確認ください。 The Path {0} does not exist. - - + パス {0} は存在しません。 --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> 一時的な出力を含むディレクトリです。 -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuration> プロジェクトをビルドする構成です。つまり、Debug/Release The given configuration is invalid. - - + 指定の構成が無効です。 -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Output> 実行するバイナリを含むディレクトリです。 The BuildBasePath was not found, provide a valid path and try again. - - + BuildBasePath が見つかりませんでした。有効なパスを指定してもう一度お試しください。 The Output path was not found, provide a valid path and try again. - - + Output パスが見つかりませんでした。有効なパスを指定してもう一度お試しください。 Additional Information Messages: - - + 追加情報メッセージ: Days - - + 日数 Error Message: - - + エラー メッセージ: Total time: {0:0.0000} {1} - - + 合計時間: {0:0.0000} {1} Hours - - + 時間 Could not find a test logger with URI or FriendlyName '{0}'. - - + URI または FriendlyName が '{0}' のテスト ロガーは見つかりませんでした。 Minutes - - + 分 Seconds - - + 秒 Stack Trace: - - + スタック トレース: Standard Error Messages: - - + 標準エラー メッセージ: Standard Output Messages: - - + 標準出力メッセージ: Attachments: - - + 添付ファイル: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + {0} で使用できるテストはありません。インストールされているテスト探索プログラム、実行プログラム、プラットフォーム、およびフレームワークのバージョン設定が適切であることを確認し、再試行してください。 @@ -867,34 +750,29 @@ Skipped - - + スキップ Discovery failed for given sources. Exception : {0} - - + 指定したソースで検出が失敗しました。例外 : {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> 現在のプロセスを起動する親プロセスのプロセス ID です。 The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + --ParentProcessId|/ParentProcessId 引数には整数であるプロセス ID を指定する必要があります。このプロセスを開始した親プロセスのプロセス ID を指定してください。 Arguments: - - + 引数: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Path to log file> テスト プラットフォームに対してログを有効にします。 ログは指定されたファイルに書き込まれます。 @@ -917,21 +794,18 @@ The file {0} provided is read only - - + 指定されたファイル {0} は読み取り専用です。 Timeout to connect or process request for DesignModeClient on port: {0} ポートで接続または DesignModeClient の要求処理のタイムアウト: {0} - - + Not Run 未実行 - - + RunSettings arguments: @@ -942,14 +816,12 @@ commandline 経由で runsettings 構成を渡す引数。引数は、"-- " の後に [name]=[value] の形式で名前と値のペアとして指定できます。-- の後のスペースにご注意ください。 複数の [name]=[value] を区切るにはスペースを使用します。 RunSettings 引数のサポートに関する詳細情報: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token 指定の runsettings の 1 つ以上に無効なトークンが含まれています。 - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory 存在しない場合、テスト結果のディレクトリが指定されたパスに作成されます。 例: /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory /ResultsDirectory パラメーターには値が必要であり、そこにテスト結果が保存されます。例: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} 'ResultsDirectory' に指定されているパス '{0}' は無効です。エラー: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process /InIsolation フラグは非推奨です。テストは常に別個のプロセスで実行されます - - + Logging Vstest Diagnostics in file: {0} 次のファイルで Vstest 診断をログ記録しています: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> テストの実行用のデータ コレクターを有効にします。詳細情報はこちら: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. データ コレクターのフレンドリ名 '{0}' が無効です。データ コレクターは無視されます。 - - + Debug Traces Messages: デバッグ トレース メッセージ: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ 例: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. テスト実行が中止されました。 - - + Test Run Canceled. テスト実行が取り消されました。 - - + Error opening response file '{0}' 応答ファイル '{0}' を開くときにエラーが発生しました - - + @<file> Read response file for more options. @<file> その他のオプションについては、応答ファイルを参照してください。 - - + Total tests: Unknown テストの合計数: 不明 - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. さらに、/TestAdapterPath コマンドを使用してテスト アダプターのパスを指定できます。例: /TestAdapterPath:<pathToCustomAdapters>。 - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions は非推奨になりました。代わりに /TestAdapterPath を使用してください。 - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> 例: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" は、testsettings を使用してテストの実行が構成されている場合、サポートされません。 - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. 実行設定を経由して構成されているコード カバレッジと Microsoft Fakes 以外のデータ コレクターは、埋め込まれたテストの設定ではサポートされていません。詳細については、https://aka.ms/vstest-configure-datacollector をご覧ください。実行設定: {0}。 - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ コンソール ロガーの診断レベルのプレフィックスを次のように変更します 例: /logger:console;prefix=<Defaults to "false"> コンソール ロガーの詳細についてはこちらをご覧ください: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. このプラットフォームでは、Blame の CollectDump オプションによるクラッシュ ダンプの収集はサポートされていません。 - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. blame で指定された blame パラメーター {0} は無効です。このパラメーターは無視されます。 - - + Diag file path '{0}' is not valid. Diag ファイル パス '{0}' は無効です。 - - + Blame argument '{0}' is not valid. Blame 引数 '{0}' は無効です。 - - + Diag argument '{0}' is not valid. Diag 引数 '{0}' は無効です。 - - + Logger argument '{0}' is not valid. Logger 引数 '{0}' は無効です。 - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 はサポートされていません。.Net Framework 3.5 を対象にしたプロジェクトでは、CLR 4.0 の「互換モード」でテストが実行されます。 - - + Test run in progress テストの実行が処理中 - - + Total tests: {0} テストの合計数: {0} - - + Failed: {0} 失敗: {0} - - + Passed: {0} 成功: {0} - - + Skipped: {0} スキップ: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. 引数 {0} が無効です。有効な引数の一覧を確認するには、/help オプションを使用してください。 - - + A total of {0} test files matched the specified pattern. 合計 {0} 個のテスト ファイルが指定されたパターンと一致しました。 - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") テストの実行パラメーターの引数 '{0}' が無効です。以下の形式を使用してください。 形式: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. このプラットフォームでは、Blame の TestTimeout を使用する CollectDump オプションによるハング ダンプの収集はサポートされていません。 - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} -失敗: {1}、合格: {2}、スキップ: {3}、合計: {4}、期間: {5} - - + None なし - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ 例: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. 環境変数 '{0}' は既に定義されていますが、-Environment 引数でオーバーライドされます。 - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.ko.xlf b/src/vstest.console/Resources/xlf/Resources.ko.xlf index 195a1c6aa5..40ea38ae94 100644 --- a/src/vstest.console/Resources/xlf/Resources.ko.xlf +++ b/src/vstest.console/Resources/xlf/Resources.ko.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}'을(를) 찾을 수 없습니다. The following Test Discovery Add-Ins are available: - - + 다음 테스트 검색 추가 기능을 사용할 수 있습니다. The following Test Execution Add-Ins are available: - - + 다음 테스트 실행 추가 기능을 사용할 수 있습니다. @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + 다음 테스트 로거 추가 기능을 사용할 수 있습니다. @@ -44,8 +39,7 @@ Error: {0} - - + 오류: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + "{0}" 매개 변수는 한 번만 제공해야 합니다. Exception occurred when instantiating extension '{0}': {1} - - + '{0}' 확장을 인스턴스화할 때 예외가 발생했습니다. {1} The following Tests are available: - - + 다음 테스트를 사용할 수 있습니다. Unrecognized parameter "{0}". - - + "{0}" 매개 변수를 인식할 수 없습니다. The test source file "{0}" provided was not found. - - + 제공된 테스트 소스 파일 "{0}"을(를) 찾을 수 없습니다. The Test Logger URI '{0}' is not valid. The Test Logger will be ignored. - - + 테스트 로거 URI '{0}'이(가) 잘못되었습니다. 테스트 로거를 무시합니다. Information: {0} - - + 정보: {0} Warning: {0} - - + 경고: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help 이 사용법 메시지를 표시합니다. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. All rights reserved. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Test Execution Command Line Tool Version {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<Logger Uri/FriendlyName> 테스트 결과의 로거를 지정합니다. 예를 들어 Visual Studio TRX(테스트 결과 파일)에 결과를 기록하려면 /logger:trx[;LogFileName=<Defaults to unique file name>]를 사용합니다. @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + 설명: 지정한 파일에서 테스트를 실행합니다. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + 사용법: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] No test source files were specified. - - + 테스트 소스 파일을 지정하지 않았습니다. No arguments were specified. - - + 인수를 지정하지 않았습니다. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] 지정된 파일 또는 와일드카드 패턴에서 테스트를 실행합니다. 여러 테스트 파일 이름 또는 패턴을 공백으로 구분합니다. 일치한 테스트 파일을 보려면 콘솔 로거 세부 정보 표시를 [상세]로 설정합니다. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + 다음 설정 공급자 추가 기능을 사용할 수 있습니다. --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Settings File> 테스트를 실행할 때 사용할 설정입니다. The /Settings parameter requires a settings file to be provided. - - + /Settings 매개 변수에는 설정 파일을 제공해야 합니다. The Settings file '{0}' could not be found. - - + 설정 파일 '{0}'을(를) 찾을 수 없습니다. Test Run Failed. - - + 테스트 실행이 실패했습니다. Test Run Successful. - - + 테스트를 실행했습니다. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + 'InIsolation' 명령에는 {0} 인수가 필요하지 않습니다. 인수 없이 명령을 지정한 다음(예: vstest.console.exe myTests.dll /InIsolation) 다시 시도하세요. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + /UseVsixExtensions 매개 변수에는 값이 필요합니다. 'true'인 경우 테스트 실행에서 설치된 VSIX 확장(있는 경우)이 사용됩니다. false인 경우에는 확장이 무시됩니다. 예: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + 'UseVsixExtensions' 명령에는 {0} 인수가 필요하지 않습니다. vstest.console.exe myTests.dll /UseVsixExtensions:true와 같이 vsix 확장을 사용할지 건너뛸지를 나타내는 명령을 지정하고 다시 시도하세요. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation 격리 모드에서 테스트를 실행합니다. 이렇게 하면 테스트에서 오류가 발생해도 vstest.console.exe가 중지될 가능성이 작아지지만 테스트 실행 속도가 @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions 이 옵션을 사용하면 vstest.console.exe 프로세스가 테스트 실행에서 설치된 VSIX 확장(있는 경우)을 사용하거나 건너뛸 수 있습니다. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + /BatchSize 인수에는 일괄 처리 크기가 필요합니다. 예: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + 일괄 처리 크기 {0}이(가) 잘못되었습니다. 일괄 처리 크기는 0보다 커야 합니다. 예: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + 테스트를 실행하려면: >vstest.console.exe tests.dll 데이터 수집기와 같은 추가 설정을 사용하여 테스트를 실행하려면: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers 설치된 테스트 Discoverer를 나열합니다. /ListExecutors Lists installed test executors. - - + /ListExecutors 설치된 테스트 Executor를 나열합니다. /ListLoggers Lists installed test loggers. - - + /ListLoggers 설치된 테스트 로거를 나열합니다. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders 설치된 테스트 설정 공급자를 나열합니다. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<File Name> 지정된 테스트 컨테이너에서 검색된 모든 테스트를 나열합니다. Time elapsed : - - + 경과 시간: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + /Tests 인수에는 하나 이상의 특정 테스트 이름 또는 해당 하위 문자열이 필요합니다. 예: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + 총 {0}개의 테스트가 검색되었지만 지정된 선택 기준({1})과 일치하는 테스트가 없습니다. 올바른 값을 사용하여 다시 시도하세요. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + 진단 데이터 어댑터가 runsettings에서 사용하도록 설정되었으므로 격리 모드를 사용하여 테스트를 실행합니다. 이 경고를 표시하지 않으려면 /inIsolation 매개 변수를 사용하세요. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + 격리 모드를 사용하여 Windows 스토어 앱에 대한 단위 테스트를 실행합니다. 이 경고를 표시하지 않으려면 /InIsolation 매개 변수를 사용하세요. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Windows 스토어 앱에 대한 단위 테스트를 실행할 때는 진단 데이터 어댑터가 지원되지 않습니다. 설정에서 진단 데이터 어댑터 설정을 제거하세요. FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + 지원되는 파일 형식: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + 기본 Executor URI: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + 플랫폼 형식({0})이 잘못되었습니다. 올바른 플랫폼 형식은 x86, x64, Arm입니다. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + /Platform 인수에는 테스트 실행의 대상 플랫폼 형식을 제공해야 합니다. 예: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Platform type> 테스트를 실행하는 데 사용할 대상 플랫폼 아키텍처입니다. 유효한 값은 x86, x64 및 ARM입니다. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + 유효 플랫폼 {0} 및 .NET Framework {1} 설정에서 테스트 실행에 요구하는 대로 격리 모드를 사용하여 테스트를 실행합니다. 이 경고를 표시하지 않으려면 /inIsolation 매개 변수를 사용하세요. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Framework Version> 테스트 실행에 사용할 대상 .NET Framework 버전입니다. 유효한 값은 ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" 등입니다. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + /Framework 인수에는 테스트 실행의 대상 .NET Framework 버전이 필요합니다. 예: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + .NET Framework 버전 {0}이(가) 잘못되었습니다. TargetFramework의 전체 이름을 지정하세요(예: .NETCoreApp,Version=v2.0). 지원되는 다른 .NET Framework 버전은 Framework40, Framework45, FrameworkCore10 및 FrameworkUap10입니다. Could not start test run for unit tests for Windows Store app: {0}. - - + Windows 스토어 앱에 대한 단위 테스트의 테스트 실행을 시작할 수 없습니다. {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expression> 지정된 식과 일치하는 테스트를 실행합니다. <Expression>은 <property>연산자<value>[|&<Expression>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + /TestCaseFilter 인수에는 필터 값이 필요합니다. 필터 값은 <property>=<value> 형식이 될 수 있습니다. 예: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + /TestCaseFilter 인수는 /Tests로 지정할 수 없습니다. 테스트가 지정된 경우 테스트 사례 필터링은 적용할 수 없습니다. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0}은(는) {1}/{2}에 대해 빌드됩니다. 실행 중에 지정된 테스트 어셈블리는 공통 대상 .NET Framework와 플랫폼을 사용해야 합니다. Only one app package (.appx file) can be specified for running tests. - - + 테스트 실행을 위해 하나의 app 패키지(.appx file)만 지정할 수 있습니다. Starting test discovery, please wait... - - + 테스트 검색을 시작하는 중입니다. 잠시 기다려 주세요... Starting test execution, please wait... - - + 테스트 실행을 시작하는 중입니다. 잠시 기다려 주세요... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + 진단 데이터 어댑터 설정을 읽는 중에 실행 중인 '{0}'이(가) throw되었습니다. 이 실행에서 모든 진단 데이터 어댑터를 건너뜁니다. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage 테스트 실행에 대해 데이터 수집기 'CodeCoverage'를 사용하도록 설정합니다. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + 'EnableCodeCoverage' 명령에는 {0} 인수가 필요하지 않습니다. 인수 없이 명령을 지정한 다음(예: vstest.console.exe myTests.dll /EnableCodeCoverage) 다시 시도하세요. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + 앱 패키지 '{0}'에 테스트 Executor 진입점이 없습니다. Windows 스토어 앱에 대한 단위 테스트를 실행하려면 Windows 스토어 앱 단위 테스트 라이브러리 프로젝트를 사용하여 앱 패키지를 만드세요. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Windows 스토어 앱에서는 코드 검사를 사용할 수 없습니다. 이 테스트 실행에 대해 코드 검사 분석을 건너뛰었습니다. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + 총 {0}개의 테스트가 검색되었지만 일부 테스트는 지정된 선택 기준({1})과 일치하지 않습니다. 올바른 값을 사용하여 다시 시도하세요. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath 이 옵션을 사용하면 vstest.console.exe 프로세스가 테스트 실행 시 지정된 경로(있는 경우)에서 사용자 지정 테스트 어댑터를 사용합니다. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + /TestAdapterPath 매개 변수에는 사용자 지정 테스트 어댑터가 포함된 위치의 일부인 값이 필요합니다. 예: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + 'TestAdapterPath'에 지정된 경로 '{0}'이(가) 잘못되었습니다. 오류: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + 제공한 사용자 지정 테스트 어댑터 검색 경로를 찾을 수 없습니다. 올바른 경로를 제공하고 다시 시도하세요. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + 'TestAdapterPath'에 지정된 경로 '{0}'에 테스트 어댑터가 포함되지 않습니다. 올바른 경로를 제공하고 다시 시도하세요. Could not start test run for the tests for Windows Phone app: {0}. - - + Windows Phone 앱 {0}에 대한 테스트를 위해 테스트 실행을 시작할 수 없습니다. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + 격리 모드를 사용하여 Windows Phone 앱에 대한 단위 테스트를 실행합니다. 이 경고를 표시하지 않으려면 /InIsolation 매개 변수를 사용하세요. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Windows Phone 앱에서는 코드 검사를 사용할 수 없습니다. 이 테스트 실행에 대해 코드 검사 분석을 건너뛰었습니다. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Windows Phone 앱에 대한 단위 테스트를 실행할 때는 진단 데이터 어댑터가 지원되지 않습니다. 설정에서 진단 데이터 어댑터 설정을 제거하세요. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + 앱 패키지 '{0}'에 테스트 Executor 진입점이 없습니다. Windows Phone 앱에 대한 단위 테스트를 실행하려면 Windows Phone 앱 단위 테스트 앱 프로젝트를 사용하여 앱 패키지를 만드세요. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + {0} 프레임워크를 사용하여 테스트를 실행합니다. 이 경고가 표시되지 않게 하려면 /Framework:{1}을(를) 지정하세요. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + 지정한 테스트 컨테이너에 테스트가 없습니다. 또한 Microsoft Windows 스토어 단위 테스트 어댑터에서 .appxbundle 파일을 지원하지 않습니다. 앱 패키지를 만들 때는 appx를 생성([앱 번들 생성] 옵션을 [사용 안 함]으로 설정)하고 다시 시도하세요. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel 테스트가 병렬로 실행되도록 지정합니다. 기본적으로 컴퓨터에서 사용 가능한 모든 코어를 사용할 수 있습니다. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + 'Parallel' 명령에는 {0} 인수가 필요하지 않습니다. 인수 없이 명령을 지정한 다음(예: vstest.console.exe myTests.dll /Parallel) 다시 시도하세요. Cannot be null or empty - - + null이거나 비워 둘 수 없습니다. --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Port> 소켓 연결 및 이벤트 메시지 수신용 포트입니다. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + --Port|/Port 인수에는 정수인 포트 번호가 필요합니다. 소켓 연결 및 이벤트 메시지 수신에 사용할 포트를 지정하세요. Unable to find the assembly under test. Please make sure that the project is built. - - + 테스트 중인 어셈블리를 찾을 수 없습니다. 프로젝트가 빌드되었는지 확인하세요. The Path {0} does not exist. - - + {0} 경로가 없습니다. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> 임시 출력을 포함하는 디렉터리입니다. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuration> 디버그/릴리스를 위해 프로젝트가 빌드되는 구성입니다. The given configuration is invalid. - - + 지정된 구성이 잘못되었습니다. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Output> 실행할 이진 파일을 포함하는 디렉터리입니다. The BuildBasePath was not found, provide a valid path and try again. - - + BuildBasePath를 찾을 수 없습니다. 올바른 경로를 제공하고 다시 시도하세요. The Output path was not found, provide a valid path and try again. - - + 출력 경로를 찾을 수 없습니다. 올바른 경로를 제공하고 다시 시도하세요. Additional Information Messages: - - + 추가 정보 메시지: Days - - + 일 Error Message: - - + 오류 메시지: Total time: {0:0.0000} {1} - - + 총 시간: {0:0.0000} {1} Hours - - + 시간 Could not find a test logger with URI or FriendlyName '{0}'. - - + URI 또는 FriendlyName이 '{0}'인 테스트 로거를 찾을 수 없습니다. Minutes - - + 분 Seconds - - + 초 Stack Trace: - - + 스택 추적: Standard Error Messages: - - + 표준 오류 메시지: Standard Output Messages: - - + 표준 출력 메시지: Attachments: - - + 첨부 파일: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + {0}에서 테스트를 사용할 수 없습니다. 설치된 테스트 Discoverer와 Executor, 플랫폼 및 프레임워크 버전 설정이 적절한지 확인한 후에 다시 시도하세요. @@ -867,34 +750,29 @@ Skipped - - + 건너뜀 Discovery failed for given sources. Exception : {0} - - + 지정한 소스에 대한 검색이 실패했습니다. 예외: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> 현재 프로세스를 시작해야 하는 부모 프로세스의 프로세스 ID입니다. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + --ParentProcessId|/ParentProcessId 인수에는 정수인 프로세스 ID가 필요합니다. 이 프로세스를 시작한 부모 프로세스의 프로세스 ID를 지정하세요. Arguments: - - + 인수: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Path to log file> 테스트 플랫폼의 로그를 사용하도록 설정합니다. 로그는 제공된 파일에 기록됩니다. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + 제공한 {0} 파일은 읽기 전용입니다. Timeout to connect or process request for DesignModeClient on port: {0} 포트에서 DesignModeClient에 대한 요청을 연결하거나 처리하는 작업에 대한 시간 제한: {0} - - + Not Run 실행되지 않음 - - + RunSettings arguments: @@ -942,14 +816,12 @@ 명령줄을 통해 runsettings 구성을 전달하기 위한 인수입니다. 인수는 "--" 뒤에 [name]=[value] 형식의 이름-값 쌍으로 지정할 수 있습니다. -- 뒤의 공백에 주의하세요. 여러 [name]=[value]를 구분하려면 공백을 사용합니다. RunSettings 인수 지원에 대한 자세한 정보: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token 제공된 하나 이상의 runsettings에 잘못된 토큰이 포함되어 있습니다. - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory 테스트 결과 디렉터리가 지정된 경로에 생성됩니다(없는 경우). 예: /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory /ResultsDirectory 매개 변수에는 테스트 결과가 저장되어야 하는 값이 필요합니다. 예: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} 'ResultsDirectory'에 지정된 경로 '{0}'이(가) 잘못되었습니다. 오류: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process /InIsolation 플래그는 사용되지 않습니다. 테스트는 항상 별도의 프로세스에서 실행됩니다. - - + Logging Vstest Diagnostics in file: {0} 파일에 Vstest Diagnostics 로깅 중: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> 테스트 실행을 위해 데이터 수집기를 사용하도록 설정합니다. 자세한 내용은 https://aka.ms/vstest-collect를 참조하세요. - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. 데이터 수집기 이름 '{0}'이(가) 잘못되었습니다. 데이터 수집기가 무시됩니다. - - + Debug Traces Messages: 디버그 추적 메시지: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ 예: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. 테스트 실행이 중단되었습니다. - - + Test Run Canceled. 테스트 실행이 취소되었습니다. - - + Error opening response file '{0}' 지시 파일 '{0}'을(를) 여는 중 오류가 발생했습니다. - - + @<file> Read response file for more options. @<file> 추가 옵션에 대한 지시 파일을 읽습니다. - - + Total tests: Unknown 총 테스트 수: 알 수 없음 - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. 또한 테스트 어댑터의 경로는 /TestAdapterPath 명령을 사용하여 지정할 수 있습니다. 예: /TestAdapterPath:<pathToCustomAdapters>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions는 더 이상 사용되지 않습니다. 대신 /TestAdapterPath를 사용하세요. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> 예: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:testsettings를 사용하여 테스트 실행을 구성하는 경우 "{0}"은(는) 지원되지 않습니다. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. 실행 설정을 통해 구성된 코드 검사 및 Microsoft Fakes 이외의 데이터 수집기는 포함된 테스트 설정으로는 지원되지 않습니다. 자세한 내용은 https://aka.ms/vstest-configure-datacollector를 참조하세요. 실행 설정: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ 아래 표시된 대로 콘솔 로거에 대한 진단 수준 접두사를 변경합니다. 예: /logger:console;prefix=<Defaults to "false"> 콘솔 로거에 대한 자세한 내용은 https://aka.ms/console-logger를 참조하세요. - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Blame에 대한 CollectDump 옵션에 의한 크래시 덤프 수집은 이 플랫폼에서 지원되지 않습니다. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. blame으로 지정된 blame 매개 변수 {0}이(가) 잘못되었습니다. 이 매개 변수를 무시합니다. - - + Diag file path '{0}' is not valid. Diag 파일 경로 '{0}'이(가) 잘못되었습니다. - - + Blame argument '{0}' is not valid. Blame 인수 '{0}'이(가) 잘못되었습니다. - - + Diag argument '{0}' is not valid. Diag 인수 '{0}'이(가) 잘못되었습니다. - - + Logger argument '{0}' is not valid. Logger 인수 '{0}'이(가) 잘못되었습니다. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35가 지원되지 않습니다. .NET Framework 3.5를 대상으로 하는 프로젝트의 경우 테스트가 CLR 4.0 "호환 모드"에서 실행됩니다. - - + Test run in progress 테스트 실행 중 - - + Total tests: {0} 총 테스트 수: {0} - - + Failed: {0} 실패: {0} - - + Passed: {0} 통과: {0} - - + Skipped: {0} 건너뜀: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. {0} 인수가 잘못되었습니다. /help 옵션을 사용하여 유효한 인수 목록을 확인하세요. - - + A total of {0} test files matched the specified pattern. 지정된 패턴과 일치한 총 테스트 파일 수는 {0}개입니다. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") 테스트 실행 매개 변수 인수 '{0}'이(가) 잘못되었습니다. 아래 형식을 사용하세요. 형식: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Blame에 대한 TestTimeout이 있는 CollectDump 옵션에 의한 중단 덤프 수집은 이 플랫폼에서 지원되지 않습니다. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - 실패: {1}, 통과: {2}, 건너뜀: {3}, 전체: {4}, 기간: {5} - - + None 없음 - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ 예: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. 환경 변수 '{0}'이(가) 이미 정의되어 있지만 -Environment 인수로 재정의되었습니다. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.pl.xlf b/src/vstest.console/Resources/xlf/Resources.pl.xlf index 82996ac5d4..beff7c5df1 100644 --- a/src/vstest.console/Resources/xlf/Resources.pl.xlf +++ b/src/vstest.console/Resources/xlf/Resources.pl.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + Nie można odnaleźć elementu „{0}”. The following Test Discovery Add-Ins are available: - - + Dostępne są następujące dodatki służące do wykrywania testów: The following Test Execution Add-Ins are available: - - + Dostępne są następujące dodatki służące do wykonywania testów: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Dostępne są następujące dodatki rejestratora testów: @@ -44,8 +39,7 @@ Error: {0} - - + Błąd: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Parametr „{0}” należy podać tylko raz. Exception occurred when instantiating extension '{0}': {1} - - + Wystąpił wyjątek podczas tworzenia wystąpienia rozszerzenia „{0}”: {1} The following Tests are available: - - + Dostępne są następujące testy: Unrecognized parameter "{0}". - - + Nierozpoznany parametr „{0}”. The test source file "{0}" provided was not found. - - + Nie odnaleziono podanego pliku źródłowego testu „{0}”. 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. Information: {0} - - + Informacje: {0} Warning: {0} - - + Ostrzeżenie: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Wyświetla ten komunikat dotyczący sposobu użycia. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Wszelkie prawa zastrzeżone. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Narzędzie wiersza polecenia firmy Microsoft (R) służące do wykonania testów (wersja {0}) @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<identyfikator URI/przyjazna nazwa rejestratora> Określa rejestrator dla wyników testu. Aby na przykład rejestrować wyniki testu do pliku wyników testu (TRX) programu Visual Studio, użyj parametru /logger:trx [;LogFileName=<wartość domyślna to unikatowa nazwa pliku>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Opis: uruchamia testy z określonych plików. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Sposób użycia: vstest.console.exe [argumenty] [opcje] [[--] <argumenty RunSettings>...]] No test source files were specified. - - + Nie określono żadnych plików źródłowych testów. No arguments were specified. - - + Nie określono żadnych argumentów. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Uruchom testy z określonych plików lub wzorca symbolu wieloznacznego. Rozdziel wiele nazw lub wzorców plików testowych spacjami. Ustaw szczegółowość rejestratora konsoli na Szczegółowy, aby wyświetlić dopasowane pliki testowe. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Dostępne są następujące dodatki dostawców ustawień: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<plik ustawień> Ustawienia, które mają być używane podczas uruchamiania testów. The /Settings parameter requires a settings file to be provided. - - + Parametr /Settings wymaga podania pliku ustawień. The Settings file '{0}' could not be found. - - + Nie można odnaleźć pliku ustawień „{0}”. Test Run Failed. - - + Przebieg testu nie powiódł się. Test Run Successful. - - + Przebieg testu zakończony powodzeniem. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + Argument {0} nie jest oczekiwany w poleceniu „InIsolation”. Określ polecenie bez argumentu (przykład: vstest.console.exe mojeTesty.dll /InIsolation) i spróbuj ponownie. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Parametr /UseVsixExtensions wymaga podania wartości. Jeśli wartość to „true”, zainstalowane rozszerzenia VSIX (jeśli istnieją) zostaną użyte w ramach przebiegu testu. Jeśli wartość to „false”, rozszerzenia zostaną zignorowane. Przykład: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + Argument {0} nie jest oczekiwany w poleceniu „UseVsixExtensions”. Określ polecenie wskazujące, czy rozszerzenia vsix mają zostać użyte, czy pominięte (przykład: vstest.console.exe mojeTesty.dll /UseVsixExtensions:true), a następnie spróbuj ponownie. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Uruchamia testy w procesie izolowanym. Dzięki temu mniej prawdopodobne jest zatrzymanie procesu vstest.console.exe po wystąpieniu błędu w testach, ale @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Powoduje to, że proces vstest.console.exe używa lub pomija zainstalowane rozszerzenia VSIX (jeśli istnieją) w przebiegu testu. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + Argument /BatchSize wymaga podania wielkości partii. Przykład: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Rozmiar partii {0} jest nieprawidłowy. Rozmiar partii powinien być większy niż zero. Przykład: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Aby uruchomić testy: >vstest.console.exe tests.dll Aby uruchomić testy z użyciem ustawień dodatkowych, takich jak moduły zbierające dane: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Wyświetla listę zainstalowanych wykrywaczy testów. /ListExecutors Lists installed test executors. - - + /ListExecutors Wyświetla listę zainstalowanych modułów wykonywania testów. /ListLoggers Lists installed test loggers. - - + /ListLoggers Wyświetla listę zainstalowanych rejestratorów testów. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Wyświetla listę zainstalowanych dostawców ustawień testów. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<nazwa pliku> Wyświetla listę wszystkich wykrytych testów z danego kontenera testów. Time elapsed : - - + Czas, który upłynął: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + Argument /Tests wymaga co najmniej jednej określonej nazwy testu lub jej podciągu. Przykłady: /Tests:MetodaTestowa1, /Tests:MetodaTestowa1,metoda2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Wykryto łącznie następującą liczbę testów: {0}. Żaden z nich nie jest zgodny z określonymi kryteriami wyboru ({1}). Użyj prawidłowych wartości i spróbuj ponownie. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Używanie trybu izolacji do uruchomienia testów jako adapterów danych diagnostycznych zostało włączone w pliku runsettings. Użyj parametru /inIsolation, aby pominąć to ostrzeżenie. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Używanie trybu izolacji do uruchomienia testów jednostkowych dla aplikacji ze Sklepu Windows. Użyj parametru /InIsolation, aby pominąć to ostrzeżenie. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Adaptery danych diagnostycznych nie są obsługiwane podczas uruchamiania testów jednostkowych dla aplikacji ze Sklepu Windows. Usuń ustawienia adapterów danych diagnostycznych z ustawień. FriendlyName: {0} - - + Przyjazna nazwa: {0} Uri: {0} - - + Identyfikator URI: {0} SettingName: {0} - - + Nazwa ustawienia: {0} Supported File Types: - - + Obsługiwane typy plików: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + Domyślny identyfikator URI modułu wykonywania: {0} Uri: {0} - - + Identyfikator URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Nieprawidłowy typ platformy: {0}. Prawidłowe typy platform to x86, x64 i Arm. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + Argument /Platform wymaga podania typu platformy docelowej dla przebiegu testu. Przykład: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<typ platformy> Docelowa architektura platformy, która zostanie użyta do wykonania testu. Prawidłowe wartości to x86, x64 i ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Używanie trybu izolacji do uruchomienia testów w sposób wymagany przez obowiązujące ustawienia platformy ({0}) i programu .NET Framework ({1}) dla przebiegu testu. Użyj parametru /InIsolation, aby pominąć to ostrzeżenie. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<wersja struktury> Docelowa wersja programu .NET Framework, która zostanie użyta na potrzeby wykonania testu. Prawidłowe wartości to ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" itp. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + Argument /Framework wymaga docelowej wersji programu .NET Framework na potrzeby przebiegu testu. Przykład: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Nieprawidłowa wersja programu .NET Framework: {0}. Podaj pełną nazwę struktury docelowej (np. .NETCoreApp,Version=v2.0). Inne obsługiwane wersje programu .NET Framework to Framework40, Framework45, FrameworkCore10 i FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Nie można rozpocząć przebiegu testu dla testów jednostkowych aplikacji ze Sklepu Windows: {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<wyrażenie> Uruchamia testy, które są zgodne z danym wyrażeniem. Element <wyrażenie> jest w formacie <właściwość>Operator<wartość>[|&<wyrażenie>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + Argument /TestCaseFilter wymaga wartości filtru. Wartość filtru może być typu <property>=<value> . Przykłady: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Nie można określać argumentu /TestCaseFilter z argumentem /Tests. Filtrowanie przypadków testowych nie jest stosowane, gdy testy zostały określone. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + Element {0} jest kompilowany dla elementu {1}/{2}. Zestawy testowe określone w ramach uruchomienia powinny mieć wspólny docelowy program .NET Framework i wspólną docelową platformę. Only one app package (.appx file) can be specified for running tests. - - + Na potrzeby uruchamiania testów można określić tylko jeden pakiet aplikacji (plik appx). Starting test discovery, please wait... - - + Trwa rozpoczynanie wykrywania testu, czekaj... Starting test execution, please wait... - - + Trwa rozpoczynanie wykonywania testu, czekaj... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + Podczas odczytywania ustawień adaptera danych diagnostycznych został zgłoszony uruchomiony element „{0}”. Wszystkie adaptery danych diagnostycznych zostaną pominięte podczas tego uruchomienia. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Włącza moduł zbierający dane „CodeCoverage” dla przebiegu testu. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + Argument {0} nie jest oczekiwany w poleceniu „EnableCodeCoverage”. Określ polecenie bez argumentu (przykład: vstest.console.exe mojeTesty.dll /EnableCodeCoverage) i spróbuj ponownie. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + Pakiet aplikacji „{0}” nie ma punktu wejścia modułu wykonywania testów. Aby uruchamiać testy jednostkowe dla aplikacji ze Sklepu Windows, utwórz pakiet aplikacji za pomocą projektu biblioteki testów jednostkowych aplikacji ze Sklepu Windows. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Pokrycie kodu nie jest dostępne dla aplikacji ze Sklepu Windows. Pominięto analizę pokrycia kodu dla tego przebiegu testu. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Wykryto łącznie następującą liczbę testów: {0}. Niektóre z nich nie są zgodne z określonymi kryteriami wyboru ({1}). Użyj prawidłowych wartości i spróbuj ponownie. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath | / TestAdapterPath Powoduje to, że proces vstest.console.exe używa niestandardowych adapterów testowych z podanej ścieżki (jeśli istnieje) w ramach przebiegu testu. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Parametr /TestAdapterPath wymaga wartości, którą jest ścieżką do lokalizacji zawierającej niestandardowe adaptery testowe. Przykład: /TestAdapterPath:c:\MojeAdapteryNiestandardowe The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Ścieżka „{0}” określona w parametrze „TestAdapterPath” jest nieprawidłowa. Błąd: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Nie odnaleziono podanej ścieżki wyszukiwania niestandardowego adaptera testowego. Podaj prawidłową ścieżkę i spróbuj ponownie. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Ścieżka „{0}” określona w parametrze „TestAdapterPath” nie zawiera żadnych adapterów testowych. Podaj prawidłową ścieżkę i spróbuj ponownie. Could not start test run for the tests for Windows Phone app: {0}. - - + Nie można rozpocząć przebiegu testu dla testów dla aplikacji Windows Phone: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Używanie trybu izolacji do uruchamiania testów jednostkowych dla aplikacji systemu Windows Phone. Użyj parametru /InIsolation, aby pominąć to ostrzeżenie. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Pokrycie kodu nie jest dostępne dla aplikacji systemu Windows Phone. Pominięto analizę pokrycia kodu dla tego przebiegu testu. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Adaptery danych diagnostycznych nie są obsługiwane podczas uruchamiania testów jednostkowych dla aplikacji systemu Windows Phone. Usuń ustawienia adapterów danych diagnostycznych z ustawień. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + Pakiet aplikacji „{0}” nie ma punktu wejścia modułu wykonywania testów. Aby uruchamiać testy jednostkowe dla aplikacji systemu Windows Phone, utwórz projekt aplikacji testów jednostkowych systemu Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Używanie platformy {0} do uruchamiania testów. Określ parametr /Framework:{1}, aby pominąć to ostrzeżenie. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Nie odnaleziono żadnych testów w określonych kontenerach testów. Ponadto adapter testów jednostkowych Sklepu Windows firmy Microsoft nie obsługuje plików appxbundle. Utwórz plik appx (ustaw opcję generowania zbioru aplikacji na wartość Nigdy) podczas tworzenia pakietu aplikacji, a następnie spróbuj ponownie. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Określa, że testy będą wykonywane równolegle. Domyślnie mogą zostać użyte wszystkie dostępne rdzenie maszyny. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + Argument {0} nie jest oczekiwany w poleceniu „Parallel”. Określ polecenie bez tego argumentu (przykład: vstest.console.exe mojeTesty.dll /Parallel), a następnie spróbuj ponownie. Cannot be null or empty - - + Nie może mieć wartości null ani być pusty --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<port> Port służący do połączenia z gniazdem i odbierania komunikatów zdarzeń. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + Argument --Port|/Port wymaga numeru portu będącego liczbą całkowitą. Określ port na potrzeby połączenia z gniazdem i odbierania komunikatów zdarzeń. Unable to find the assembly under test. Please make sure that the project is built. - - + Nie można odnaleźć testowanego zestawu. Upewnij się, że projekt został skompilowany. The Path {0} does not exist. - - + Ścieżka {0} nie istnieje. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<podstawowa ścieżka do kompilacji> Katalog zawierający tymczasowe dane wyjściowe. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<konfiguracja> Konfiguracja, na potrzeby której kompilowany jest projekt, na przykład Debug/Release The given configuration is invalid. - - + Podana konfiguracja jest nieprawidłowa. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<dane wyjściowe> Katalog zawierający pliki binarne do uruchomienia. The BuildBasePath was not found, provide a valid path and try again. - - + Nie można odnaleźć parametru BuildBasePath. Podaj prawidłową ścieżkę i spróbuj ponownie. The Output path was not found, provide a valid path and try again. - - + Nie można odnaleźć ścieżki wyjściowej. Podaj prawidłową ścieżkę i spróbuj ponownie. Additional Information Messages: - - + Dodatkowe komunikaty informacyjne: Days - - + Dni Error Message: - - + Komunikat o błędzie: Total time: {0:0.0000} {1} - - + Łączny czas: {0:0.0000} {1} Hours - - + Godziny Could not find a test logger with URI or FriendlyName '{0}'. - - + Nie można odnaleźć rejestratora testów z identyfikatorem URI lub przyjazną nazwą „{0}”. Minutes - - + Minuty Seconds - - + Sekundy Stack Trace: - - + Ślad stosu: Standard Error Messages: - - + Standardowe komunikaty o błędach: Standard Output Messages: - - + Standardowe komunikaty wyjściowe: Attachments: - - + Załączniki: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + Brak dostępnych testów w elemencie {0}. Upewnij się, że ustawienia zainstalowanych wykrywaczy testów, modułów wykonywania, platform i wersji struktur są odpowiednie, i spróbuj ponownie. @@ -867,34 +750,29 @@ Skipped - - + Pominięto Discovery failed for given sources. Exception : {0} - - + Wykrywanie nie powiodło się dla podanych źródeł. Wyjątek: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<identyfikator procesu nadrzędnego> Identyfikator procesu nadrzędnego odpowiedzialnego za uruchomienie bieżącego procesu. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + Argument --ParentProcessId|/ParentProcessId wymaga identyfikatora procesu będącego liczbą całkowitą. Określ identyfikator procesu nadrzędnego, który uruchomił ten proces. Arguments: - - + Argumenty: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<ścieżka do pliku dziennika> Włącz dzienniki dla platformy testowej. Dzienniki są zapisywanie w podanym pliku. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Podany plik {0} jest tylko do odczytu Timeout to connect or process request for DesignModeClient on port: {0} Przekroczono limit czasu żądania nawiązywania połączenia lub przetwarzania dla elementu DesignModeClient na porcie: {0} - - + Not Run Nie uruchomiono - - + RunSettings arguments: @@ -942,14 +816,12 @@ Argumenty do przekazania konfiguracji runsettings za pośrednictwem wiersza polecenia. Argumenty mogą być określone jako para nazwa-wartość formularza [nazwa]=[wartość] po „-- ”. Pamiętaj o spacji po --. Oddziel wiele par [nazwa]=[wartość] za pomocą spacji. Więcej informacji na temat obsługi argumentów RunSettings: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Co najmniej jedne z podanych ustawień uruchamiania zawierają nieprawidłowy token - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory Jeśli katalog wyników nie istnieje, zostanie utworzony w określonej ścieżce. Przykład /ResultsDirectory:<ŚcieżkaDoKataloguWyników> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Parametr /ResultsDirectory wymaga wartości określającej miejsce zapisania wyników testu. Przykład: /ResultsDirectory:c:\KatalogWynikówTestu - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Ścieżka „{0}” określona w parametrze „ResultsDirectory” jest nieprawidłowa. Błąd: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process Flaga /InIsolation jest przestarzała. Testy zawsze są uruchamiane w oddzielnym procesie - - + Logging Vstest Diagnostics in file: {0} Rejestrowanie diagnostyki Vstest w pliku: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<przyjazna nazwa modułu zbierającego dane> Włącza moduł zbierający dane dla przebiegu testu. Więcej informacji: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Przyjazna nazwa modułu zbierającego dane „{0}” jest nieprawidłowa. Moduł zbierający dane będzie ignorowany. - - + Debug Traces Messages: Komunikaty śledzenia debugowania: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Przykład: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Przebieg testu został przerwany. - - + Test Run Canceled. Przebieg testu został anulowany. - - + Error opening response file '{0}' Błąd podczas otwierania pliku odpowiedzi „{0}” - - + @<file> Read response file for more options. @<file> Przeczytaj zawartość pliku odpowiedzi w celu uzyskania dodatkowych opcji. - - + Total tests: Unknown Łączna liczba testów: nieznana - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Dodatkowo ścieżkę do adapterów testów można określić za pomocą polecenia /TestAdapterPath. Przykład: /TestAdapterPath:<ścieżka_do_adapterów_niestandardowych>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. Polecenie /UseVsixExtensions jest wycofywane. Użyj zamiast niego polecenia /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Przykład: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect: element „{0}” nie jest obsługiwany, jeśli przebieg testu został skonfigurowany za pomocą pliku testsettings. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Moduły zbierające dane inne niż Pokrycie kodu i Microsoft Fakes skonfigurowane za pośrednictwem ustawień uruchamiania nie są obsługiwane przez osadzone ustawienia testów. Zobacz https://aka.ms/vstest-configure-datacollector w celu uzyskania dalszych informacji. Ustawienia uruchamiania: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Zmień prefiks poziomu diagnostyki dla rejestratora konsoli, jak pokazano poniżej Przykład: /logger:console;prefix=<wartość domyślna to „false”> Więcej informacji o rejestratorze konsoli: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Zbieranie zrzutów awaryjnych przez opcję CollectDump programu Blame nie jest obsługiwane w przypadku tej platformy. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Parametr blame określony z argumentem blame, {0} jest nieprawidłowy. Ten parametr jest ignorowany. - - + Diag file path '{0}' is not valid. Ścieżka pliku Diag „{0}” jest nieprawidłowa. - - + Blame argument '{0}' is not valid. Argument Blame „{0}” jest nieprawidłowy. - - + Diag argument '{0}' is not valid. Argument Diag „{0}” jest nieprawidłowy. - - + Logger argument '{0}' is not valid. Argument Logger „{0}” jest nieprawidłowy. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Program Framework35 nie jest obsługiwany. W przypadku projektów przeznaczonych dla programu .Net Framework 3.5 testy zostaną uruchomione w aparacie CLR 4.0 w trybie zgodności. - - + Test run in progress Uruchomienie testu w toku - - + Total tests: {0} Łączna liczba testów: {0} - - + Failed: {0} Zakończone niepowodzeniem: {0} - - + Passed: {0} Zakończone pomyślnie: {0} - - + Skipped: {0} Pominięte: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. Argument {0} jest nieprawidłowy. Użyj opcji /help, aby sprawdzić listę prawidłowych argumentów. - - + A total of {0} test files matched the specified pattern. Łączna liczba plików testowych dopasowanych do określonego wzorca: {0}. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") Argument parametru przebiegu testu „{0}” jest nieprawidłowy. Użyj poniższego formatu. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Zbieranie zrzutów po zawieszeniu przez opcję CollectDump z opcją TestTimeout programu Blame nie jest obsługiwane w przypadku tej platformy. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} — niepowodzenie: {1}, powodzenie: {2}, pominięto: {3}, łącznie: {4}, czas trwania: {5} - - + None Brak - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Przykład: -e:ZMIENNA1=WARTOŚĆ1 -e:INNA_ZMIENNA="WARTOŚĆ ZE SPACJAMI" -e:INNA_ZMIENNA="WARTOŚCI;oddzielone;średnikami" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. Zmienna środowiskowa „{0}” została już zdefiniowana, ale została przysłonięta przez argument by-Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.pt-BR.xlf b/src/vstest.console/Resources/xlf/Resources.pt-BR.xlf index 463632dacc..279baa38a6 100644 --- a/src/vstest.console/Resources/xlf/Resources.pt-BR.xlf +++ b/src/vstest.console/Resources/xlf/Resources.pt-BR.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}' não encontrado. The following Test Discovery Add-Ins are available: - - + Os seguintes Suplementos de Descoberta de Teste estão disponíveis: The following Test Execution Add-Ins are available: - - + Os seguintes Suplementos de Execução de Teste estão disponíveis: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Os seguintes Suplementos de Agente de Teste estão disponíveis: @@ -44,8 +39,7 @@ Error: {0} - - + Erro: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + O parâmetro "{0}" deve ser fornecido apenas uma vez. Exception occurred when instantiating extension '{0}': {1} - - + Ocorreu uma exceção ao criar uma instância da extensão '{0}': {1} The following Tests are available: - - + Os Testes a seguir estão disponíveis: Unrecognized parameter "{0}". - - + Parâmetro "{0}" não reconhecido. The test source file "{0}" provided was not found. - - + O arquivo de origem de teste "{0}" fornecido não foi encontrado. 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. Information: {0} - - + Informações: {0} Warning: {0} - - + Aviso: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Exibe esta mensagem de uso. Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (c) Microsoft Corporation. Todos os direitos reservados. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Ferramenta de Linha de Comando de Execução de Teste da Microsoft (R) Versão {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<Logger Uri/FriendlyName> Especifique um agente para os resultados de teste. Por exemplo, para registrar os resultados em um Arquivo de Resultados de Teste (TRX) do Visual Studio use /logger:trx[;LogFileName=<Defaults to unique file name>] @@ -151,8 +133,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Description: Runs tests from the specified files. - - + Descrição: executa testes dos arquivos especificados. @@ -162,20 +143,17 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Uso: vstest.console.exe [Argumentos] [Opções] [[--] <RunSettings arguments>...]] No test source files were specified. - - + Nenhum arquivo de origem de teste foi especificado. No arguments were specified. - - + Nenhum argumento foi especificado. @@ -185,8 +163,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Execute testes por meio dos arquivos especificados ou do padrão curinga. Separe vários nomes de arquivos de teste ou padrões por espaços. Defina o detalhamento do agente do console como detalhado para exibir os arquivos de teste correspondentes. @@ -196,58 +173,49 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a The following Settings Providers Add-Ins are available: - - + Os seguintes Suplementos de Provedores de Configurações estão disponíveis: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Settings File> Configurações a serem usadas durante a execução de testes. The /Settings parameter requires a settings file to be provided. - - + O parâmetro /Settings exige que um arquivo de configurações seja fornecido. The Settings file '{0}' could not be found. - - + O arquivo de Configurações '{0}' não pôde ser encontrado. Test Run Failed. - - + Falha na Execução de Teste. Test Run Successful. - - + Execução de Teste Bem-sucedida. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + O argumento {0} não é esperado no comando 'InIsolation'. Especifique o comando sem o argumento (exemplo: vstest.console.exe myTests.dll /InIsolation) e tente novamente. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + O parâmetro /UseVsixExtensions requer um valor. Se ele for 'true', as extensões VSIX instaladas (caso haja alguma) serão usadas na execução de teste. Se ele for false, elas serão ignoradas. Exemplo: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + O argumento {0} não é esperado no comando 'UseVsixExtensions'. Especifique o comando que indica se as extensões vsix devem ser usadas ou ignoradas (exemplo: vstest.console.exe myTests.dll /UseVsixExtensions:true) e tente novamente. @@ -255,8 +223,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Executa os testes em um processo isolado. Isso diminui a probabilidade de que o processo vstest.console.exe seja interrompido em um erro nos testes, mas os testes @@ -267,8 +234,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Faz o processo vstest.console.exe usar ou ignorar as extensões VSIX instaladas (caso haja alguma) na execução de teste. @@ -276,14 +242,12 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + O argumento /BatchSize requer o tamanho do lote. Exemplo: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Tamanho do lote inválido {0}. O tamanho do lote deve ser maior que zero. Exemplo: /BatchSize:10 @@ -291,8 +255,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Para executar testes: >vstest.console.exe tests.dll Para executar testes com configurações adicionais, como coletores de dados: @@ -301,67 +264,58 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Lista os discoverers de teste instalados. /ListExecutors Lists installed test executors. - - + /ListExecutors Lista os executores de teste instalados. /ListLoggers Lists installed test loggers. - - + /ListLoggers Lista os agentes de teste instalados. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Lista os provedores de configurações de teste instalados. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<File Name> Lista todos os testes detectados no contêiner de testes especificado. Time elapsed : - - + Tempo decorrido: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + O argumento /Tests requer um ou mais nomes de teste específicos ou suas subcadeias de caracteres. Exemplos: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Foram descobertos {0} testes no total, mas nenhum teste corresponde ao critério de seleção especificado ({1}). Use valores corretos e tente novamente. , - - + , @@ -379,96 +333,81 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Usando o modo de isolamento para executar os testes pois os adaptadores de dados de diagnóstico foram habilitados nas runsettings. Use o parâmetro /inIsolation para suprimir esse aviso. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Usando o modo de isolamento para executar testes de unidade para aplicativos da Windows Store. Use o parâmetro /InIsolation para suprimir esse aviso. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Não há suporte para adaptadores de dados de diagnóstico ao executar testes de unidade para aplicativos da Windows Store. Remova as configurações de adaptadores de dados de diagnóstico das configurações. FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + Tipos de arquivos com suporte: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + URI do executor padrão: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Tipo de plataforma inválido: {0}. Os tipos de plataforma válidos são x86, x64 e Arm. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + O argumento /Platform requer que o tipo de plataforma de destino para a execução de teste seja fornecido. Exemplo: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Platform type> Arquitetura da plataforma destino a ser usada na execução de teste. Os valores válidos são x86, x64 e ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Usando o modo de isolamento para executar testes conforme o exigido pelas configurações em vigor da Plataforma: {0} e do .Net Framework: {1} para execução de teste. Use o parâmetro /inIsolation para suprimir esse aviso. @@ -476,8 +415,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Versão do Framework> Versão de destino do .NET Framework a ser usada para execução de teste. Os valores válidos são ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. @@ -485,20 +423,17 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + O argumento /Framework requer a versão do .Net Framework de destino para a execução de teste. Exemplo: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Versão inválida do .Net Framework: {0}. Forneça o nome completo do TargetFramework(Exemplo: .NETCoreApp,Version=v2.0). Outras versões compatíveis do .Net Framework são Framework40, Framework45, FrameworkCore10 e FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Não foi possível iniciar a execução de testes de unidade para o aplicativo da Windows Store: {0}. @@ -511,8 +446,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expression> Executa testes que correspondem à expressão fornecida. <Expression> tem o formato <property>Operator<value>[|&<Expression>] @@ -527,78 +461,66 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + O argumento /TestCaseFilter exige um valor de filtro. O valor de filtro pode ser do tipo <propriedade>=<valor> . Exemplos: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + O argumento /TestCaseFilter não pode ser especificado com /Tests. A filtragem de casos de teste não se aplica quando os testes são especificados. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} é construído para {1}/{2}. Os assemblies de testes especificados em uma execução devem ter um destino comum de do Net. framework e da plataforma. Only one app package (.appx file) can be specified for running tests. - - + Somente um pacote do aplicativo (arquivo .appx) pode ser especificado para a execução de testes. Starting test discovery, please wait... - - + Iniciando descoberta de teste, espere... Starting test execution, please wait... - - + Iniciando execução de teste, espere... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + A leitura das configurações do adaptador de dados de diagnóstico emitiu uma execução '{0}'. Todos os adaptadores de dados de diagnóstico serão ignorados nessa execução. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Habilita o coletor de dados 'CodeCoverage' para a execução de teste. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + O argumento {0} não é esperado no comando 'EnableCodeCoverage'. Especifique o comando sem o argumento (exemplo: vstest.console.exe myTests.dll /EnableCodeCoverage) e tente novamente. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + O pacote do aplicativo '{0}' não tem o ponto de entrada do executor de teste. Para executar testes de unidade para aplicativos da Windows Store, crie o pacote do aplicativo usando o projeto de Biblioteca de Teste de Unidade de aplicativo da Windows Store. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + A cobertura do teste não está disponível para aplicativos da Windows Store. Análise de cobertura de código ignorada nesta execução de teste. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Foram descobertos {0} testes no total, mas alguns testes não correspondem ao critério de seleção especificado ({1}). Use valores corretos e tente novamente. @@ -606,8 +528,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Faz com que o processo vstest.console.exe use adaptadores de teste personalizados de um arquivo fornecido (caso haja algum) na execução de teste. @@ -615,68 +536,57 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + O parâmetro /TestAdapterPath exige um valor, que é o caminho de um local contendo adaptadores de teste personalizados. Exemplo: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + O caminho '{0}' especificado em 'TestAdapterPath' é inválido. Erro: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + O caminho de pesquisa do adaptador de teste personalizado fornecido não foi encontrado, forneça um caminho válido e tente novamente. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + O caminho '{0}' especificado em 'TestAdapterPath' não contém nenhum adaptador de teste, forneça um caminho válido e tente novamente. Could not start test run for the tests for Windows Phone app: {0}. - - + Não foi possível iniciar a execução de testes para o aplicativo do Windows Phone: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Usando o modo de isolamento para executar testes de unidade para aplicativos do Windows Phone. Use o parâmetro /InIsolation para suprimir esse aviso. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + A cobertura do teste não está disponível para aplicativos do Windows Phone. Análise de cobertura do teste ignorada nesta execução de teste. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Não há suporte para adaptadores de dados de diagnóstico ao executar testes de unidade para aplicativos do Windows Phone. Remova as configurações de adaptadores de dados de diagnóstico das configurações. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + O pacote do aplicativo '{0}' não tem o ponto de entrada do executor de teste. Para executar testes de unidade para aplicativos do Windows Phone, crie o pacote do aplicativo usando o projeto de Biblioteca de Teste de Unidade de aplicativo do Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Usando a estrutura {0} para executar os testes. Especifique /Framework:{1} para suprimir esse aviso. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Nenhum teste foi encontrado nos contêineres de teste especificados. Além disso, o adaptador de teste de unidade da Microsoft Windows Store não dá suporte a arquivos .appxbundle. Crie um appx (defina a opção Gerar Pacote do Aplicativo como nunca) quando criar o Pacote do Aplicativo e tente novamente. @@ -684,8 +594,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Especifica que os testes sejam executados em paralelo. Por padrão, podem ser usados todos os núcleos disponíveis no computador. @@ -693,166 +602,140 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + O argumento {0} não é esperado no comando 'Parallel'. Especifique o comando sem o argumento (exemplo: vstest.console.exe myTests.dll /Parallel) e tente novamente. Cannot be null or empty - - + Não pode ser nulo ou estar vazio --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Port> A Porta para a conexão de soquete e o recebimento de mensagens de eventos. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + O argumento --Port|/Port requer o número da porta que é um número inteiro. Especifique a porta de conexão de soquete e de recebimento de mensagens de evento. Unable to find the assembly under test. Please make sure that the project is built. - - + Não é possível localizar o assembly em teste. Verifique se o projeto foi criado. The Path {0} does not exist. - - + O caminho {0} não existe. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> O diretório que contém as saídas temporárias. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuration> A configuração para a qual o projeto foi compilado, ou seja, Debug/Release The given configuration is invalid. - - + A configuração fornecida é inválida. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Output> O diretório que contém os binários a serem executados. The BuildBasePath was not found, provide a valid path and try again. - - + O BuildBasePath não foi encontrado, forneça um caminho válido e tente novamente. The Output path was not found, provide a valid path and try again. - - + O caminho de saída não foi encontrado, forneça um caminho válido e tente novamente. Additional Information Messages: - - + Mensagens de informações adicionais: Days - - + Dias Error Message: - - + Mensagem de erro: Total time: {0:0.0000} {1} - - + Tempo total: {0:0.0000} {1} Hours - - + Horas Could not find a test logger with URI or FriendlyName '{0}'. - - + Não foi possível localizar um agente de teste com o URI ou o FriendlyName '{0}'. Minutes - - + Minutos Seconds - - + Segundos Stack Trace: - - + Rastreamento de pilha: Standard Error Messages: - - + Mensagens de erro padrão: Standard Output Messages: - - + Mensagens de saída padrão: Attachments: - - + Anexos: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + Nenhum teste está disponível em {0}. Certifique-se de que os detectores de teste e executores, configurações de versão de estrutura da plataforma instalados sejam apropriados e tente novamente. @@ -867,34 +750,29 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Skipped - - + Ignorado Discovery failed for given sources. Exception : {0} - - + Falha na descoberta para as fontes fornecidas. Exceção: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> ID do Processo Pai responsável pela inicialização do processo atual. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + O argumento --ParentProcessId|/ParentProcessId requer a ID do processo que é um número inteiro. Especifique a ID do processo pai que iniciou esse processo. Arguments: - - + Argumentos: @@ -905,8 +783,7 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Path to log file> Habilitar os logs para a plataforma de teste. Os logs são gravados no arquivo fornecido. @@ -917,21 +794,18 @@ Alterar o nível de rastreamento dos logs, como mostrado abaixo The file {0} provided is read only - - + O arquivo {0} fornecido é somente leitura Timeout to connect or process request for DesignModeClient on port: {0} Tempo limite atingido para conectar-se ou processar a solicitação para DesignModeClient na porta: {0} - - + Not Run Não Executado - - + RunSettings arguments: @@ -942,14 +816,12 @@ Alterar o nível de rastreamento dos logs, como mostrado abaixo Argumentos para transmitir as configurações de runsettings através da commandline. Os argumentos podem ser especificados como um par nome-valor do formulário [name]=[value] após "-- ". Observe o espaço após --. Use um espaço para separar vários [name]=[value]. Mais informações sobre o suporte para os argumentos de RunSettings: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Uma ou mais runsettings fornecidas contêm um token inválido - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ Alterar o nível de rastreamento dos logs, como mostrado abaixo --ResultsDirectory|/ResultsDirectory O diretório de resultados de teste será criado no caminho especificado, caso ainda não exista. Exemplo: /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory O parâmetro /ResultsDirectory exige um valor no qual os resultados de teste deverão ser salvos. Exemplo: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} O caminho '{0}' especificado em 'ResultsDirectory' é inválido. Erro: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process O sinalizador /InIsolation foi preterido. Os testes sempre são executados em um processo separado - - + Logging Vstest Diagnostics in file: {0} Registro em log do diagnóstico Vstest no arquivo: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> Habilita o coletor de dados para a execução de teste. Mais informações aqui: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. O nome amigável '{0}' do Coletor de Dados não é válido. O Coletor de Dados será ignorado. - - + Debug Traces Messages: Depurar Mensagens de Rastreamento: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Alterar o nível de rastreamento dos logs, como mostrado abaixo Exemplo: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Execução de Teste Anulada. - - + Test Run Canceled. Execução de Teste Cancelada. - - + Error opening response file '{0}' Erro ao abrir o arquivo de resposta '{0}' - - + @<file> Read response file for more options. @<file> Ler o arquivo de resposta para obter mais opções. - - + Total tests: Unknown Total de testes: desconhecido - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Além disso, o caminho para os adaptadores de teste podem ser especificados usando o comando /TestAdapterPath. Exemplo /TestAdapterPath:<pathToCustomAdapters>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions está sendo preterido. Em vez disso, use /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Exemplo: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" não é compatível se a execução de teste é configurada usando configurações de teste. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Coletores de dados que não sejam a Cobertura de Código e o Microsoft Fakes definidos por meio de configurações de execução não são compatíveis com configurações de teste inseridas. Consulte https://aka.ms/vstest-configure-datacollector para obter mais informações. Configurações de execução: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Alterar o nível de rastreamento dos logs, como mostrado abaixo Altere o prefixo de nível de diagnóstico do agente de console, como mostrado abaixo Exemplo: /logger:console;prefix=<Defaults to "false"> Veja mais informações sobre o Agente de Console aqui: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. A coleta de despejos de memória pela opção CollectDump para Blame não tem suporte nesta plataforma. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. O parâmetro blame especificado com blame, {0} é inválido. Ignorando este parâmetro. - - + Diag file path '{0}' is not valid. O caminho para o arquivo diag '{0}' não é válido. - - + Blame argument '{0}' is not valid. O argumento blame '{0}' não é válido. - - + Diag argument '{0}' is not valid. O argumento diag '{0}' não é válido. - - + Logger argument '{0}' is not valid. O argumento logger '{0}' não é válido. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Não há suporte para Framework35. Para projetos destinados ao .Net Framework 3.5, o teste será executado no "modo de compatibilidade" do CLR 4.0. - - + Test run in progress Execução de teste em andamento - - + Total tests: {0} Total de testes: {0} - - + Failed: {0} Com falha: {0} - - + Passed: {0} Aprovados: {0} - - + Skipped: {0} Ignorados: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. O argumento {0} é inválido. Use a opção /help para verificar a lista de argumentos válidos. - - + A total of {0} test files matched the specified pattern. {0} arquivos de teste no total corresponderam ao padrão especificado. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") O argumento do parâmetro de execução de teste '{0}' é inválido. Use o formato abaixo. Formato: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. A coleta de despejos de trava pela opção CollectDump com TestTimeout para Blame não é tem suporte para esta plataforma. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} – Com falha: {1}, Aprovado: {2}, Ignorado: {3}, Total: {4}, Duração: {5} - - + None Nenhum - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Altere o prefixo de nível de diagnóstico do agente de console, como mostrado a Exemplo: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperado com;ponto e vírgula" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. A variável de ambiente '{0}' já foi definida, mas foi substituída por um argumento -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.ru.xlf b/src/vstest.console/Resources/xlf/Resources.ru.xlf index 90dea0be6e..f8cb924c03 100644 --- a/src/vstest.console/Resources/xlf/Resources.ru.xlf +++ b/src/vstest.console/Resources/xlf/Resources.ru.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + "{0}": не найдено. The following Test Discovery Add-Ins are available: - - + Доступны следующие надстройки обнаружения тестов: The following Test Execution Add-Ins are available: - - + Доступны следующие надстройки выполнения тестов: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Доступны следующие надстройки средства ведения журнала тестирования: @@ -44,8 +39,7 @@ Error: {0} - - + Ошибка: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + Параметр "{0}" должен быть указан только один раз. Exception occurred when instantiating extension '{0}': {1} - - + При создании экземпляра расширения "{0}" возникло исключение: {1} The following Tests are available: - - + Доступны следующие тесты: Unrecognized parameter "{0}". - - + Нераспознанный параметр "{0}". The test source file "{0}" provided was not found. - - + Указанный исходный файл теста "{0}" не найден. The Test Logger URI '{0}' is not valid. The Test Logger will be ignored. - - + URI средства ведения журнала тестирования "{0}" недопустимо. Это средство ведения журнала тестирования будет игнорироваться. Information: {0} - - + Сведения: {0} Warning: {0} - - + Предупреждение: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Отображение этого сообщения об использовании. Copyright (c) Microsoft Corporation. All rights reserved. - - + (с) Корпорация Майкрософт (Microsoft Corporation). Все права защищены. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Программа Microsoft (R) Test Execution Command Line Tool версии {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<URI/понятное_имя_средства_ведения_журнала> Укажите средство ведения журнала результатов тестирования. Например, чтобы сохранять результаты в файле результатов тестов Visual Studio (TRX), укажите /logger:trx[;LogFileName=<по умолчанию уникальное имя файла>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Описание: выполняет тесты из указанных файлов. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Использование: vstest.console.exe [аргументы] [параметры] [[--] <аргументы RunSettings>...]] No test source files were specified. - - + Исходные файлы тестов не указаны. No arguments were specified. - - + Аргументы не указаны. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Выполняйте тесты из указанных файлов или шаблона с подстановочными знаками. Разделяйте несколько шаблонов или имен тестовых файлов пробелами. Задайте высокий уровень детализации для средства ведения журнала консоли, чтобы просмотреть соответствующие тестовые файлы. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Доступны следующие надстройки поставщиков параметров: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<файл параметров> Параметры, используемые при запуске тестов. The /Settings parameter requires a settings file to be provided. - - + Для параметра /Settings требуется указать файл параметров. The Settings file '{0}' could not be found. - - + Не удалось найти файл параметров "{0}". Test Run Failed. - - + Сбой тестового запуска. Test Run Successful. - - + Тестовый запуск выполнен. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + Аргумент {0} не ожидается в команде InIsolation. Укажите команду без аргумента (например, vstest.console.exe myTests.dll /InIsolation) и повторите попытку. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + Для параметра /UseVsixExtensions требуется значение. Если задано значение true, установленные расширения VSIX (при наличии) будут использоваться в тестовом запуске. Если задано значение false, то они будут игнорироваться. Пример: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + Аргумент {0} не ожидается в команде UseVsixExtensions. Укажите команду, определяющую, требуется ли использовать или игнорировать расширения VSIX (например, vstest.console.exe myTests.dll /UseVsixExtensions:true), и повторите попытку. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Запуск тестов в изолированном процессе. Это снижает вероятность остановки процесса vstest.console.exe из-за ошибки в тестах, но @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Определяет использование или пропуск процессом vstest.console.exe установленных расширений VSIX (при наличии) в тестовом запуске. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + Для аргумента /BatchSize требуется указать размер пакета. Пример: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + Недопустимый размер пакета {0}. Размер пакета должен быть больше нуля. Пример: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Запуск тестов: >vstest.console.exe tests.dll Запуск тестов с дополнительными параметрами, например со сборщиками данных: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Список установленных средств обнаружения тестов. /ListExecutors Lists installed test executors. - - + /ListExecutors Список установленных исполнителей тестов. /ListLoggers Lists installed test loggers. - - + /ListLoggers Список установленных средств ведения журналов тестирования. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Список установленных поставщиков параметров тестирования. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<имя_файла> Перечисление всех обнаруженных тестов из указанного контейнера тестов. Time elapsed : - - + Прошло времени: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + Для аргумента /Tests требуется указать один или несколько конкретных имен тестов или их подстрок. Примеры: /Tests:TestsMethod1, /Tests:TestMethod1, method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Всего обнаружено тестов: {0}, но тесты не соответствуют указанному условию выбора ({1}). Задайте правильные значения и повторите попытку. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + Используется режим изоляции для запуска тестов, так как в файле параметров запуска RUNSETTINGS включены адаптеры диагностических данных. Используйте параметр /InIsolation, чтобы отключить это предупреждение. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Использование режима изоляции для запуска модульных тестов приложений для Магазина Windows. Используйте параметр /InIsolation, чтобы отключить это предупреждение. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Адаптеры диагностических данных не поддерживаются при запуске модульных тестов для приложений для Магазина Windows. Удалите параметры адаптеров диагностических данных из параметров. FriendlyName: {0} - - + Понятное имя: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + Имя параметра: {0} Supported File Types: - - + Поддерживаемые типы файлов: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + URI исполнителя по умолчанию: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Неверный тип платформы: {0}. Допустимые типы платформы: x86, x64 и Arm. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + Для аргумента /Platform требуется указать тип целевой платформы для тестового запуска. Пример: /Platform:x 86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<тип_платформы> Архитектура целевой платформы, в которой будут выполняться тесты. Допустимые значения: x86, x64 и ARM. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Для запуска тестов используется изолированный режим в соответствии с параметрами Platform:{0} и .Net Framework:{1} для тестового запуска. Используйте параметр /InIsolation, чтобы отключить это предупреждение. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<версия платформы> Целевая версия платформы .NET Framework, используемая для выполнения тестов. Допустимые значения: ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" и т. п. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + Аргумент /Framework требует указать целевую версию .NET Framework для тестового запуска. Пример: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Недопустимая версия .NET Framework: {0}. Укажите полное имя целевой платформы (например: .NETCoreApp,Version=v2.0). Другие поддерживаемые версии .NET Framework: Framework40, Framework45, FrameworkCore10 и FrameworkUap10. Could not start test run for unit tests for Windows Store app: {0}. - - + Не удалось запустить тестовый запуск для модульных тестов приложений для Магазина Windows: {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<выражение> Запуск тестов, соответствующих заданному выражению. <выражение> имеет формат <свойство>оператор<значение>[|&<выражение>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + Для аргумента /TestCaseFilter необходимо указать значение фильтра. Значение фильтра можно задать в формате <свойство>=<значение>. Пример: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + Аргумент /TestCaseFilter нельзя указывать при использовании аргумента /Tests. Если указываются тесты, фильтрация тестовых случаев не применяется. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + Сборка {0} выполняется для {1}/{2}. Заданные в запуске тестовые сборки должны иметь одинаковые значения целевой среды .NET Framework и платформы. Only one app package (.appx file) can be specified for running tests. - - + Для выполнения тестов можно указать только один пакет приложения (APPX-файл). Starting test discovery, please wait... - - + Запуск обнаружения тестов; подождите... Starting test execution, please wait... - - + Запуск выполнения тестов; подождите... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + При чтении параметров адаптера диагностических данных возникло выполнение "{0}". Все адаптеры диагностических данных будут пропущены в этом запуске. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Включает сборщик данных "CodeCoverage" для тестового запуска. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + Аргумент {0} не ожидается в команде EnableCodeCoverage. Укажите команду без аргумента (например, vstest.console.exe myTests.dll /EnableCodeCoverage) и повторите попытку. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + У пакета приложения "{0}" нет точки входа исполнителя тестов. Для запуска модульных тестов приложений для Магазина Windows создайте пакет приложения с помощью проекта библиотеки модульных тестов приложений для Магазина Windows. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Покрытие кода недоступно для приложений для Магазина Windows. Анализ покрытия кода пропущен для этого тестового запуска. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Всего обнаружено тестов: {0}, но некоторые тесты не соответствуют указанному условию выбора ({1}). Задайте правильные значения и повторите попытку. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Процесс vstest.console.exe будет использовать пользовательские адаптеры тестов по заданному пути (при наличии) в тестовом запуске. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + Для параметра /TestAdapterPath требуется значение, представляющее собой путь к расположению с пользовательскими адаптерами тестов. Пример: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + Путь {0}, заданный в параметре TestAdapterPath, недопустим. Ошибка: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Указанный путь поиска пользовательского адаптера теста не найден. Укажите допустимый путь и повторите попытку. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + Путь "{0}", заданный в параметре TestAdapterPath, не содержит адаптеров тестов. Укажите допустимый путь и повторите попытку. Could not start test run for the tests for Windows Phone app: {0}. - - + Не удалось запустить тестовый запуск для тестов приложений Windows Phone: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Использование режима изоляции для запуска модульных тестов приложений Windows Phone. Используйте параметр /InIsolation, чтобы отключить это предупреждение. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Покрытие кода недоступно для приложений Windows Phone. Анализ покрытия кода пропущен для этого тестового запуска. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Адаптеры диагностических данных не поддерживаются при запуске модульных тестов для приложений Windows Phone. Удалите параметры адаптеров диагностических данных из параметров. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + У пакета приложения "{0}" нет точки входа исполнителя тестов. Для запуска модульных тестов приложений Windows Phone создайте пакет приложения с помощью проекта приложения модульного тестирования Windows Phone. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Использование платформы {0} для запуска тестов. Укажите /Framework:{1}, чтобы отключить это предупреждение. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + В указанных контейнерах тестов тесты не найдены. Кроме того, адаптер модульных тестов для Магазина Windows (Майкрософт) не поддерживает APPXBUNDLE-файлы. Создайте APPX-файл (установите значение "Никогда" для параметра "Создать набор приложений") при создании пакета приложения и повторите попытку. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Указывает, что тесты должны выполняться параллельно. По умолчанию можно использовать любое имеющееся число ядер на компьютере. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + Аргумент {0} не ожидается в команде Parallel. Укажите команду без аргумента (например, vstest.console.exe myTests.dll /Parallel) и повторите попытку. Cannot be null or empty - - + Неопределенное или отсутствующее значение недопустимо. --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<порт> Порт для подключения через сокет и получения сообщений о событиях. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + Для аргумента --Port|/Port требуется указать номер порта, который должен быть целым числом. Укажите порт для подключения через сокет и получения событий сообщений. Unable to find the assembly under test. Please make sure that the project is built. - - + Не удается найти тестируемую сборку. Убедитесь, что проект создан. The Path {0} does not exist. - - + Путь {0} не существует. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<базовый путь к сборке> Каталог, содержащий временные выходные данные. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<конфигурация> Конфигурация, для которой создан проект, например Debug/Release The given configuration is invalid. - - + Данная конфигурация недопустима. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<вывод> Каталог, содержащий двоичные файлы для запуска. The BuildBasePath was not found, provide a valid path and try again. - - + Базовый путь к сборке не найден, укажите допустимый путь и повторите попытку. The Output path was not found, provide a valid path and try again. - - + Выходной путь не найден, укажите допустимый путь и повторите попытку. Additional Information Messages: - - + Дополнительные информационные сообщения: Days - - + Дни Error Message: - - + Сообщение об ошибке: Total time: {0:0.0000} {1} - - + Общее время: {0:0.0000} {1} Hours - - + Часы Could not find a test logger with URI or FriendlyName '{0}'. - - + Не удалось найти средство ведения журнала тестирования с URI или понятным именем "{0}". Minutes - - + Минуты Seconds - - + Секунды Stack Trace: - - + Трассировка стека: Standard Error Messages: - - + Стандартные сообщения об ошибке: Standard Output Messages: - - + Стандартные выходные сообщения: Attachments: - - + Вложения: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + В {0} нет доступных тестов. Проверьте правильность параметров установленного средства обнаружения и выполнения тестов, а также платформы и версии платформы, и повторите попытку. @@ -867,34 +750,29 @@ Skipped - - + Пропущен Discovery failed for given sources. Exception : {0} - - + Не удалось выполнить обнаружение для заданных источников. Исключение: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ИД_родительского_процесса> Идентификатор родительского процесса, отвечающего за запуск текущего процесса. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + Для аргумента --ParentProcessId|/ParentProcessId требуется указать ИД процесса, который должен быть целым числом. Укажите идентификатор родительского процесса, ответственного за запуск текущего процесса. Arguments: - - + Аргументы: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<путь к файлу журнала> Включение журналов для платформы тестирования. Журналы записываются в предоставленный файл. @@ -917,21 +794,18 @@ The file {0} provided is read only - - + Указанный файл {0} доступен только для чтения. Timeout to connect or process request for DesignModeClient on port: {0} Время ожидания установления подключения или обработки запроса для DesignModeClient на порту {0} истекло. - - + Not Run Не выполнен - - + RunSettings arguments: @@ -942,14 +816,12 @@ Аргументы для передачи конфигураций runsettings через командную строку. Аргументы могут быть указаны как пара "имя-значение" в формате [имя]=[значение] после "-- ". Обратите внимание на пробел после --. Используйте пробел для разделения нескольких пар [имя]=[значение]. Дополнительные сведения о поддержке аргументов RunSettings: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Один или несколько файлов RUNSETTINGS включают в себя недопустимый токен - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory По указанному пути будет создан каталог результатов тестов, если он еще не существует. Пример: /ResultsDirectory:<путь_к_каталогу_результатов> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory Для параметра /ResultsDirectory требуется значение, в котором сохраняются результаты тестирования. Пример: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} Путь "{0}", указанный в "ResultsDirectory", недопустим. Ошибка: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process Флаг /InIsolation использовать не рекомендуется. Тесты всегда запускаются в отдельном процессе - - + Logging Vstest Diagnostics in file: {0} Ведение журналов диагностики Vstest в файле: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<понятное имя сборщика данных> Включает сборщик данных для тестового запуска. Подробнее: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Понятное имя сборщика данных "{0}" недопустимо. Сборщик данных будет пропущен. - - + Debug Traces Messages: Сообщения трассировок отладки: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Пример: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Тестовый запуск прерван. - - + Test Run Canceled. Тестовый запуск отменен. - - + Error opening response file '{0}' Произошла ошибка при открытии файла ответа "{0}" - - + @<file> Read response file for more options. @<файл> Считывание файла ответов с дополнительными параметрами. - - + Total tests: Unknown Всего тестов: неизвестно - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Кроме того, путь к адаптерам тестов можно указать с помощью команды /TestAdapterPath. Пример: /TestAdapterPath:<путь_к_настраиваемым_адаптерам>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. Параметр /UseVsixExtensions устарел. Используйте /TestAdapterPath. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Пример: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect:"{0}" не поддерживается, если тестовый запуск настроен с использованием testsettings. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Сборщики данных, настроенные в параметрах запуска, кроме покрытия кода и Microsoft Fakes, не поддерживаются со встроенными параметрами тестирования. Дополнительные сведения: https://aka.ms/vstest-configure-datacollector. Параметры запуска: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Изменить префикс уровня диагностики для средства ведения журнала консоли можно описанным ниже способом Пример: /logger:console;prefix=<по умолчанию "false"> Подробнее о средстве ведения журнала консоли: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Сбор аварийных дампов с помощью параметра CollectDump для Blame не поддерживается для этой платформы. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Указанный с Blame параметр {0} недопустим. Он будет пропущен. - - + Diag file path '{0}' is not valid. Путь к файлу диагностики "{0}" недопустим. - - + Blame argument '{0}' is not valid. Аргумент Blame "{0}" недопустим. - - + Diag argument '{0}' is not valid. Аргумент диагностики "{0}" недопустим. - - + Logger argument '{0}' is not valid. Аргумент средства ведения журнала "{0}" недопустим. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 не поддерживается. Для проектов, предназначенных для .NET Framework 3.5, тест будет выполняться в среде CLR 4.0 в "режиме совместимости". - - + Test run in progress Выполняется тестовый запуск - - + Total tests: {0} Всего тестов: {0} - - + Failed: {0} Не пройдено: {0} - - + Passed: {0} Пройдено: {0} - - + Skipped: {0} Пропущено: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. Аргумент {0} недопустим. Используйте параметр /help, чтобы просмотреть список допустимых аргументов. - - + A total of {0} test files matched the specified pattern. Общее количество тестовых файлов ({0}), соответствующих указанному шаблону. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") Недопустимый аргумент "{0}" для параметра тестового запуска. Используйте указанный ниже формат. Формат: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Сбор дампов зависаний с помощью параметра CollectDump с TestTimeout для Blame не поддерживается для этой платформы. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0}: не пройдено {1}, пройдено {2}, пропущено {3}, всего {4}, длительность {5}. - - + None Нет - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Пример: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. Переменная среды "{0}" уже определена, но переопределена аргументом -Environment. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.tr.xlf b/src/vstest.console/Resources/xlf/Resources.tr.xlf index cf4a5fe37c..0c86a878b9 100644 --- a/src/vstest.console/Resources/xlf/Resources.tr.xlf +++ b/src/vstest.console/Resources/xlf/Resources.tr.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + '{0}' bulunamadı. The following Test Discovery Add-Ins are available: - - + Şu Test Bulma Eklentileri kullanılabilir: The following Test Execution Add-Ins are available: - - + Şu Test Yürütmesi eklentileri kullanılabilir: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + Şu Test Günlükçüsü Eklentileri kullanılabilir: @@ -44,8 +39,7 @@ Error: {0} - - + Hata: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + "{0}" parametresi yalnızca bir kez belirtilmelidir. Exception occurred when instantiating extension '{0}': {1} - - + '{0}' uzantısının örneği oluşturulurken özel durum oluştu: {1} The following Tests are available: - - + Şu Testler kullanılabilir: Unrecognized parameter "{0}". - - + "{0}" parametresi tanınmıyor. The test source file "{0}" provided was not found. - - + Belirtilen "{0}" test kaynak dosyası bulunamadı. 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. Information: {0} - - + Bilgi: {0} Warning: {0} - - + Uyarı: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help Bu kullanım iletisini görüntüler. Copyright (c) Microsoft Corporation. All rights reserved. - - + Telif Hakkı (c) Microsoft Corporation. Tüm hakları saklıdır. Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Test Yürütmesi Komut Satırı Aracı Sürüm {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<Günlükçü URI/FriendlyName> Test sonuçları için bir günlükçü belirtin. Örneğin, sonuçları bir Visual Studio Test Sonuçları Dosyası'na (TRX) kaydetmek için şunu kullanın: /logger:trx[;LogFileName=<Varsayılan olarak benzersiz dosya adını alır>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + Açıklama: Belirtilen dosyalardan testleri çalıştırır. @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + Kullanım: vstest.console.exe [Bağımsız Değişkenler] [Seçenekler] [[--] <RunSettings bağımsız değişkenleri>...]] No test source files were specified. - - + Test kaynak dosyası belirtilmedi. No arguments were specified. - - + Bağımsız değişken belirtilmedi. @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] Belirtilen dosyalardaki veya joker karakter desenindeki testleri çalıştırın. Birden çok test dosyası adını veya desenini boşluklarla ayırın. Eşleşen test dosyalarını görüntülemek için konsol günlükçüsü ayrıntı düzeyini ayrıntılı olarak ayarlayın. @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + Şu Ayar Sağlayıcısı Eklentileri kullanılabilir: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Ayarlar Dosyası> Testleri çalıştırırken kullanılacak ayarlar. The /Settings parameter requires a settings file to be provided. - - + /Settings parametresi bir ayarlar dosyasının belirtilmesini gerektirir. The Settings file '{0}' could not be found. - - + '{0}' Ayarlar dosyası bulunamadı. Test Run Failed. - - + Test Çalıştırması Başarısız. Test Run Successful. - - + Test Çalıştırması Başarılı. Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + {0} bağımsız değişkeni 'InIsolation' komutunda beklenmiyor. Komutu bağımsız değişken olmadan belirtin (Örnek: vstest.console.exe myTests.dll /InIsolation) ve yeniden deneyin. The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + /UseVsixExtensions parametresi bir değer gerektiriyor. Değer 'true' ise test çalıştırmasında yüklü VSIX uzantıları (varsa) kullanılır. Değer false ise uzantılar yoksayılır. Örnek: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + {0} bağımsız değişkeni 'UseVsixExtensions' komutunda beklenmiyor. Komutta vsix uzantılarının kullanılacağını veya atlanacağını belirtin (Örnek: vstest.console.exe myTests.dll /UseVsixExtensions:true) ve yeniden deneyin. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation Testleri yalıtılmış bir işlemde çalıştırır. Bu, vstest.console.exe işleminin testlerdeki bir hata nedeniyle durdurulması olasılığını azaltır, @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions Bu işlem vstest.console.exe işleminin test çalıştırmasında yüklü VSIX uzantılarını (varsa) kullanmasını veya atlamasını sağlar. @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + /BatchSize bağımsız değişkeni toplu iş boyutunu gerektirir. Örnek: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + {0} toplu iş boyutu geçersiz. Toplu iş boyutu sıfırdan büyük olmalıdır. Örnek: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + Testleri çalıştırmak için: >vstest.console.exe tests.dll Testleri veri toplayıcılar gibi ek ayarlarla çalıştırmak için: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers Yüklü test bulucuları listeler. /ListExecutors Lists installed test executors. - - + /ListExecutors Yüklü test yürütücülerini listeler. /ListLoggers Lists installed test loggers. - - + /ListLoggers Yüklü test günlükçülerini listeler. /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders Yüklü test ayarları sağlayıcılarını listeler. -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<Dosya Adı> Verilen test kapsayıcısında bulunan tüm testleri listeler. Time elapsed : - - + Geçen süre: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + /Tests bağımsız değişkeni, alt dizelerinde bir veya daha fazla belirli test adının olmasını gerektirir. Örnekler: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + Toplam {0} test bulundu, ancak belirtilen ölçütlerle eşleşen test yok({1}). Doğru değerleri kullanın ve yeniden deneyin. , - - + , @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + runsettings içinde tanılama veri bağdaştırıcıları etkinleştirildiğinden testleri çalıştırmak üzere Yalıtım modu kullanılıyor. Bu uyarıyı kapatmak için /inIsolation parametresini kullanın. Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + Windows Mağazası uygulamaları için birim testlerini çalıştırmak üzere Yalıtım modu kullanılıyor. Bu uyarıyı kapatmak için /InIsolation parametresini kullanın. Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + Windows Mağazası uygulamaları için birim testleri çalıştırılırken tanılama veri bağdaştırıcıları desteklenmiyor. Ayarlardan tanılama veri bağdaştırıcısı ayarlarını kaldırın. FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + Desteklenen Dosya Türleri: {0} - - + {0} {0}, - - + {0}, Default Executor Uri: {0} - - + Varsayılan Yürütücü URI’si: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + Geçersiz platform türü: {0}. Geçerli platform türleri x86, x64 ve ARM’dir. The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + /Platform bağımsız değişkeni, test çalıştırması için hedef platform türünün belirtilmesini gerektirir. Örnek: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Platform türü> Test yürütmesi için kullanılacak hedef platform mimarisi. Geçerli değerler x86, x64 ve ARM'dir. Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + Testleri test çalıştırması için etkili Platformun:{0} ve .NET Framework:{1} ayarlarının gerektirdiği şekilde çalıştırmak için Yalıtım modu kullanılıyor. Bu uyarıyı kapatmak için /inIsolation parametresini kullanın. @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Framework Sürümü> Test yürütme için kullanılacak hedef .Net Framework sürümü. Geçerli değerler: ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" vb. @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + /Framework bağımsız değişkeni test çalıştırması için hedef .NET Framework sürümünü gerektirir. Örnek: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + Geçersiz .NET Framework sürümü:{0}. Lütfen TargetFramework tam adını (Örnek: .NETCoreApp,Sürüm=v2.0) belirtin. Desteklenen diğer .NET Framework sürümleri Framework40, Framework45, FrameworkCore10 and FrameworkUap10’dur. Could not start test run for unit tests for Windows Store app: {0}. - - + Windows Mağazası uygulamalarına yönelik birim testleri için test çalıştırması başlatılamadı: {0}. @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<İfade> Verilen ifadeyle eşleşen testleri çalıştırır. <İfade>, <özellik>İşleç<değer>[|&<İfade>] biçimindedir; @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + /TestCaseFilter bağımsız değişkeni filtre değeri gerektirir. Filtre değeri <özellik>=<değer> türünde olabilir. Örnekler: "Priority=1", "TestCategory=Gece" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + /TestCaseFilter bağımsız değişkeni /Tests ile belirtilemez. Testler belirtildiğinde test örneklerinin filtrelemesi geçerli değildir. {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0}, {1}/{2} için derlendi. Bir çalıştırmada belirtilen test bütünleştirilmiş kodu ortak bir hedef .NET framework ve platforma sahip olmalıdır. Only one app package (.appx file) can be specified for running tests. - - + Testleri çalıştırmak için yalnızca bir uygulama paketi (.appx dosyası) belirtilebilir. Starting test discovery, please wait... - - + Test bulma başlatılıyor, lütfen bekleyin... Starting test execution, please wait... - - + Test yürütmesi başlatılıyor, lütfen bekleyin... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + Tanılama veri bağdaştırıcısı ayarlarının okunması çalışan bir '{0}' oluşturdu. Tüm tanılama veri bağdaştırıcıları bu çalıştırmada atlanacak. /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage Test çalıştırması için 'CodeCoverage' veri toplayıcısını etkinleştirir. Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + {0} bağımsız değişkeni 'EnableCodeCoverage' komutunda beklenmiyor. Komutu bağımsız değişken olmadan belirtin (Örnek: vstest.console.exe myTests.dll /EnableCodeCoverage) ve yeniden deneyin. App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + '{0}' uygulama paketi, test yürütücüsü giriş noktasına sahip değil. Windows Mağazası uygulamalarına yönelik birim testlerini çalıştırmak için Windows Mağazası uygulaması Birim Testi Kitaplığı projesini kullanarak uygulama paketini oluşturun. Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Kod kapsamı Windows Mağazası uygulamaları için kullanılamaz. Bu test çalıştırması için kod kapsamı analizi atlandı. A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + Toplam {0} test bulundu, ancak bazı testler belirtilen ölçütlerle eşleşmiyor({1}). Doğru değerleri kullanın ve yeniden deneyin. @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath Bu, vstest.console.exe işleminin test çalıştırmasında verilen yoldan (varsa) özel test bağdaştırıcılarını kullanmasını sağlar. @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + /TestAdapterPath parametresi, özel test bağdaştırıcıları içeren bir konumun yolu olan değeri gerektirir. Örnek: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + 'TestAdapterPath' içinde belirtilen '{0}' yolu geçersiz. Hata: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + Belirtilen özel test bağdaştırıcısı arama yolu bulunamadı; geçerli bir yol belirtin ve yeniden deneyin. The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + 'TestAdapterPath' içinde belirtilen '{0}' yolu hiçbir test bağdaştırıcısı içermiyor; geçerli bir yol belirtin ve yeniden deneyin. Could not start test run for the tests for Windows Phone app: {0}. - - + Windows Phone uygulamasına yönelik testler için test çalıştırması başlatılamadı: {0}. Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + Windows Phone uygulamaları için birim testlerini çalıştırmak üzere Yalıtım modu kullanılıyor. Bu uyarıyı kapatmak için /InIsolation parametresini kullanın. Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Kod kapsamı Windows Phone uygulamaları için kullanılamaz. Bu test çalıştırması için kod kapsamı analizi atlandı. Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + Windows Phone uygulamaları için birim testleri çalıştırılırken tanılama veri bağdaştırıcıları desteklenmiyor. Ayarlardan tanılama veri bağdaştırıcısı ayarlarını kaldırın. App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + '{0}' uygulama paketi, test yürütücüsü giriş noktasına sahip değil. Windows Phone uygulamalarına yönelik birim testlerini çalıştırmak için Windows Phone Birim Testi Uygulaması projesini kullanarak uygulama paketini oluşturun. Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + Testleri çalıştırmak için {0} çerçevesi kullanılıyor. Bu uyarıyı kapatmak için /Framework:{1} değerini belirtin. No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + Belirtilen test kapsayıcılarında test bulunamadı. Ayrıca, Microsoft Windows Mağazası Birim testi bağdaştırıcısı .appxbundle dosyalarını desteklemiyor. Uygulama Paketi oluştururken bir appx oluşturun (Uygulama paketi grubu oluştur seçeneğini Hiçbir Zaman olarak ayarlayın) ve yeniden deneyin. @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel Testlerin paralel olarak yürütülmesini belirtir. Varsayılan olarak makine üzerindeki tüm mevcut çekirdekler kullanılabilir. @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + {0} bağımsız değişkeni 'Parallel' komutunda beklenmiyor. Komutu bağımsız değişken olmadan belirtin (Örnek: vstest.console.exe myTests.dll /Parallel) ve yeniden deneyin. Cannot be null or empty - - + Null veya boş olamaz --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Bağlantı Noktası> Yuva bağlantısı ve olay iletilerini almaya yönelik Bağlantı Noktası. The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + --Port|/Port bağımsız değişkeni tamsayı olan bir bağlantı noktası numarası gerektirir. Yuva bağlantısına ve olay iletilerini almaya yönelik bağlantı noktasını belirtin. Unable to find the assembly under test. Please make sure that the project is built. - - + Test kapsamındaki bütünleştirilmiş kod bulunamıyor. Lütfen projenin oluşturulduğundan emin olun. The Path {0} does not exist. - - + {0} Yolu yok. --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> Geçici çıkışları içeren dizin. -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuration> Projenin derleme nedeni olan yapılandırma (Debug/Release) The given configuration is invalid. - - + Belirtilen yapılandırma geçersiz. -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Çıkış> Çalıştırılacak ikili dosyaları içeren dizin. The BuildBasePath was not found, provide a valid path and try again. - - + BuildBasePath bulunamadı, geçerli bir yol belirtin ve yeniden deneyin. The Output path was not found, provide a valid path and try again. - - + Çıkış yolu bulunamadı, geçerli bir yol belirtin ve yeniden deneyin. Additional Information Messages: - - + Ek Bilgi İletileri: Days - - + Gün Error Message: - - + Hata İletisi: Total time: {0:0.0000} {1} - - + Toplam süre: {0:0.0000} {1} Hours - - + Saat Could not find a test logger with URI or FriendlyName '{0}'. - - + URI veya FriendlyName değeri '{0}' olan bir test günlükçüsü bulunamadı. Minutes - - + Dakika Seconds - - + Saniye Stack Trace: - - + Yığın İzleme: Standard Error Messages: - - + Standart Hata İletileri: Standard Output Messages: - - + Standart Çıkış İletileri: Attachments: - - + Ekler: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + {0} içinde hiç test yok. Yüklü test bulucuları ve yükleyicileri, platform ve çerçeve sürümü ayarlarının uygun olmasına dikkat edin ve yeniden deneyin. @@ -867,34 +750,29 @@ Skipped - - + Atlandı Discovery failed for given sources. Exception : {0} - - + Belirtilen kaynaklar için bulma başarısız oldu. Özel durum: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> Geçerli işlemi başlatmadan sorumlu Üst İşlemin işlem kimliği. The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + --ParentProcessId|/ParentProcessId bağımsız değişkeni, işlem kimliğinin tamsayı olmasını gerektirir. Bu işlemi başlatan üst işlemin işlem kimliğini belirtin. Arguments: - - + Bağımsız değişkenler: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Günlük dosyası yolu> Test platformu için günlükleri sağlayın. Günlükler sağlanan dosyaya yazılır. @@ -917,21 +794,18 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin The file {0} provided is read only - - + Belirtilen {0} dosyası salt okunur Timeout to connect or process request for DesignModeClient on port: {0} Şu bağlantı noktası üzerinde DesignModeClient için bağlantı veya işleme isteği zaman aşımı: {0} - - + Not Run Çalıştırılmadı - - + RunSettings arguments: @@ -942,14 +816,12 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin Komut satırı aracılığıyla runsettings yapılandırmalarını geçirmek için kullanılan bağımsız değişkenler. Bağımsız değişkenler "-- " karakterlerinden sonra [ad]=[değer] biçiminde ad-değer çifti olarak belirtilebilir. -- karakterlerinden sonra boşluk olduğuna dikkat edin. Birden fazla [ad]=[değer] çiftini ayırmak için bir boşluk kullanın. RunSettings bağımsız değişkenleri desteği hakkında daha fazla bilgi: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token Sağlanan bir veya daha fazla runsettings geçersiz belirteç içeriyor - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin --ResultsDirectory|/ResultsDirectory Mevcut değilse test sonuçları dizini belirtilen yolda oluşturulacak. Örnek /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory /ResultsDirectory parametresi test sonuçlarının kaydedileceği bir değer gerektirir. Örnek: /ResultsDirectory:c:\TestSonuçlarıDizinim - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} 'ResultsDirectory' içinde belirtilen '{0}' yolu geçersiz. Hata: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process /InIsolation bayrağı kullanım dışı bırakıldı. Testler her zaman ayrı bir işlem içinde çalıştırılır - - + Logging Vstest Diagnostics in file: {0} Vstest Tanılamaları şu dosyadaki günlüğe kaydediliyor: {0} - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> Test çalıştırması için veri toplayıcıyı etkinleştirir. Daha fazla bilgi: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. Veri Toplayıcı kolay adı '{0}' geçerli değil. Veri Toplayıcı yoksayılacak. - - + Debug Traces Messages: Hata Ayıklama İzleme İletileri: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin Örnek: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. Test Çalıştırması Durduruldu. - - + Test Run Canceled. Test Çalıştırması İptal Edildi. - - + Error opening response file '{0}' '{0}' yanıt dosyası açılırken hata oluştu - - + @<file> Read response file for more options. @<dosya> Daha fazla seçenek için yanıt dosyasını okuyun. - - + Total tests: Unknown Toplam test sayısı: Bilinmiyor - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. Buna ek olarak, test bağdaştırıcıları yolu /TestAdapterPath komutu kullanılarak belirtilebilir. Örnek /TestAdapterPath:<pathToCustomAdapters>. - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions kullanımdan kaldırılıyor. Lütfen bunun yerine /TestAdapterPath kullanın. - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> Örnek: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/Collect: Test çalıştırmasını yapılandırmak için test ayarları kullanıldığında "{0}" desteklenmez. - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. Çalıştırma ayarları aracılığıyla yapılandırılan Kod Kapsamı ve Microsoft Fakes dışındaki veri toplayıcılar, ekli test ayarlarında desteklenmiyor. Daha fazla bilgi için bkz. https://aka.ms/vstest-configure-datacollector. Çalıştırma ayarları: {0}. - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin Konsol günlükçüsü için tanılama düzeyi ön ekini aşağıda gösterildiği gibi değiştirin Örnek: /logger:console;prefix=<Varsayılan olarak "false" değerini alır> Konsol Günlükçüsü hakkında daha fazla bilgi: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. Blame için CollectDump seçeneğine göre kilitlenme bilgi dökümlerinin toplanması bu platform için desteklenmiyor. - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. Blame ile belirtilen blame parametresi {0} geçerli değil. Bu parametre yoksayılıyor. - - + Diag file path '{0}' is not valid. Diag dosya yolu '{0}' geçerli değil. - - + Blame argument '{0}' is not valid. Blame bağımsız değişkeni '{0}' geçerli değil. - - + Diag argument '{0}' is not valid. Diag bağımsız değişkeni '{0}' geçerli değil. - - + Logger argument '{0}' is not valid. Logger bağımsız değişkeni '{0}' geçerli değil. - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". Framework35 desteklenmiyor. İçin hedefleme .net Framework 3.5, test CLR 4.0 "uyumluluk moduna" çalışacak. - - + Test run in progress Test çalıştırması devam ediyor - - + Total tests: {0} Toplam test sayısı: {0} - - + Failed: {0} Başarısız: {0} - - + Passed: {0} Geçti: {0} - - + Skipped: {0} Atlandı: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. {0} bağımsız değişkeni geçersiz. Lütfen geçerli bağımsız değişkenlerin listesini denetlemek için /help seçeneğini kullanın. - - + A total of {0} test files matched the specified pattern. Toplam {0} test dosyası belirtilen desenle eşleşti. - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") '{0}' test çalıştırması parametre bağımsız değişkeni geçersiz. Lütfen aşağıdaki biçimi kullanın. Biçim: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. Blame için TestTimeout ile CollectDump seçeneğine göre asılı kalma bilgi dökümlerinin toplanması bu platform için desteklenmiyor. - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - Başarısız: {1}, Başarılı: {2}, Atlanan: {3}, Toplam: {4}, Süre: {5} - - + None Hiçbiri - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ Günlükler için izleme düzeyini aşağıda gösterildiği gibi değiştirin Örnek: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. '{0}' ortam değişkeni zaten tanımlandı, ancak -Environment bağımsız değişkeni tarafından geçersiz kılındı. - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.zh-Hans.xlf b/src/vstest.console/Resources/xlf/Resources.zh-Hans.xlf index 95574729b7..3b22f37c95 100644 --- a/src/vstest.console/Resources/xlf/Resources.zh-Hans.xlf +++ b/src/vstest.console/Resources/xlf/Resources.zh-Hans.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + 未找到“{0}”。 The following Test Discovery Add-Ins are available: - - + 以下测试发现外接程序可用: The following Test Execution Add-Ins are available: - - + 以下测试执行外接程序可用: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + 以下测试记录器加载项可用: @@ -44,8 +39,7 @@ Error: {0} - - + 错误: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + 应只提供一次参数“{0}”。 Exception occurred when instantiating extension '{0}': {1} - - + 实例化扩展“{0}”时出现异常: {1} The following Tests are available: - - + 以下测试可用: Unrecognized parameter "{0}". - - + 无法识别的参数“{0}”。 The test source file "{0}" provided was not found. - - + 找不到提供的测试源文件“{0}”。 The Test Logger URI '{0}' is not valid. The Test Logger will be ignored. - - + 测试记录器 URI“{0}”无效。将忽略该测试记录器。 Information: {0} - - + 信息: {0} Warning: {0} - - + 警告: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help 显示此用法信息。 Copyright (c) Microsoft Corporation. All rights reserved. - - + 版权所有 (C) Microsoft Corporation。保留所有权利。 Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) 测试执行命令行工具版本 {0} @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<Logger Uri/FriendlyName> 为测试结果指定一个记录器。例如，若要将结果记录到 Visual Studio 测试结果文件(TRX)中，请使用/logger:trx[;LogFileName=<Defaults to unique file name>] @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + 说明: 从指定的文件运行测试。 @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + 用法: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] No test source files were specified. - - + 未指定测试源文件。 No arguments were specified. - - + 未指定参数。 @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] 从指定的文件或通配符模式运行测试。通过空格将多个测试文件或模式分隔开来。 将控制台记录器详细程度设置为“详细”以查看匹配的测试文件。 @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + 以下设置提供程序外接程序可用: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<Settings File> 运行测试时要使用的设置。 The /Settings parameter requires a settings file to be provided. - - + /Settings 参数要求提供设置文件。 The Settings file '{0}' could not be found. - - + 找不到设置文件“{0}”。 Test Run Failed. - - + 测试运行失败。 Test Run Successful. - - + 测试运行成功。 Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + 参数 {0} 不应出现在 "InIsolation" 命令中。指定不带该参数的命令(示例: vstest.console.exe myTests.dll /InIsolation)，然后重试。 The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + /UseVsixExtensions 参数需要一个值。如果值为 "true"，则安装的 VSIX 扩展(如果有)将用在测试运行中。如果值为 "false"，则将其忽略。示例: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + 参数 {0} 不应出现在 "UseVsixExtensions" 命令中.指定指示是否应使用或跳过 vsix 扩展的命令(示例:vstest.console.exe myTests.dll /UseVsixExtensions:true),然后重试. @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation 在独立进程中运行测试。虽然这可使 vstest.console.exe 进程在测试出现错误时停止的可能性较小，但是测试的 @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + / UseVsixExtensions 这可使 vstest.console.exe 进程在测试运行中使用或者跳过 安装的 VSIX 扩展(如果有)。 @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + /BatchSize 参数要求批的大小。示例: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + 批大小 {0} 无效。批大小应大于零。示例: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + 运行测试: >vstest.console.exe tests.dll 使用其他设置(如数据收集器)运行测试: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + / ListDiscoverers 列出已安装的测试发现器。 /ListExecutors Lists installed test executors. - - + / ListExecutors 列出已安装的测试执行器。 /ListLoggers Lists installed test loggers. - - + / ListLoggers 列出已安装的测试记录器。 /ListSettingsProviders Lists installed test settings providers. - - + / ListSettingsProviders 列出已安装的测试设置提供程序。 -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<File Name> 从给定测试容器中列出所有已发现的测试。 Time elapsed : - - + 已用时间: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + /Tests 参数要求一个或多个特定测试名称或其子字符串。 示例: /Tests:TestsMethod1、/Tests:TestMethod1、method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + 共发现 {0} 个测试，但没有与指定选择条件 ({1}) 匹配的测试。使用正确的值，然后重试。 , - - + ， @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + 使用隔离模式运行测试，因为已在 runsettings 中启用了诊断数据适配器。使用 /inIsolation 参数取消此警告。 Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + 使用隔离模式为 Windows 应用商店应用运行单元测试。使用 /InIsolation 参数取消此警告。 Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + 为 Windows 应用商店应用运行单元测试时不支持诊断数据适配器。从设置中删除诊断数据适配器设置。 FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + 支持的文件类型: {0} - - + {0} {0}, - - + {0}， Default Executor Uri: {0} - - + 默认执行器 URI: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + 无效的平台类型: {0}。有效平台类型为 x86、x64 和 ARM。 The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + /Platform 参数要求提供用于测试运行的目标平台类型。示例: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<Platform type> 用于执行测试的目标平台体系结构。 有效值为 x86、x64 和 ARM。 Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + 按照针对测试运行有效的 Platform:{0} 和 .Net Framework:{1} 设置要求，使用隔离模式运行测试。使用 /inIsolation 参数取消此警告。 @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Framework Version> 用于执行测试的目标 .Net Framework 版本。 有效值为 ".NETFramework,Version=v4.5.1".NETCoreApp,Version=v1.0" 等。 @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + /Framework 参数要求用于测试运行的目标 .Net Framework 版本。示例: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + 无效的 .Net Framework 版本: {0}。请提供 TargetFramework 的全名(示例: .NETCoreApp,Version=v2.0)。其他支持的 .Net Framework 版本为 Framework40、Framework45、FrameworkCore10 和 FrameworkUap10。 Could not start test run for unit tests for Windows Store app: {0}. - - + 无法启动针对 Windows 应用商店应用的单元测试的测试运行: {0}。 @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expression> 运行与给定表达式匹配的测试。 <Expression> 的格式为 <property>Operator<value>[|&<Expression>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + /TestCaseFilter 参数需要筛选器值。 筛选器值可以是“<属性>=<值>”类型。 示例: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + 不能使用 /Tests 指定 /TestCaseFilter 参数。指定测试时无法筛选测试用例。 {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} 为 {1}/{2} 而生成。运行中指定的测试程序集应具有共有的目标.Net Framework 和平台。 Only one app package (.appx file) can be specified for running tests. - - + 只能为运行测试指定一个应用包(.appx 文件)。 Starting test discovery, please wait... - - + 正在启动测试发现，请稍候... Starting test execution, please wait... - - + 正在启动测试执行，请稍候... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + 读取诊断数据适配器设置引发了“{0}”的运行。将在此运行中跳过所有诊断数据适配器。 /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage 启动数据收集器“CodeCoverage”以运行测试。 Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + 参数 {0} 不应出现在 "EnableCodeCoverage" 命令中。指定不带参数的命令(示例: vstest.console.exe myTests.dll /EnableCodeCoverage)，然后重试。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + 应用包“{0}”没有测试执行器入口点。为对 Windows 应用商店应用运行单元测试，使用 Windows 应用商店应用单元测试库项目创建应用包。 Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + 代码覆盖率不适用于 Windows 应用商店应用。已对此测试运行跳过代码覆盖率分析。 A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + 共发现 {0} 个测试，但一些测试与指定选择条件 ({1}) 不匹配。使用正确的值，然后重试。 @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath 这将使 vstest.console.exe 进程在测试运行中使用 给定路径(如果有)中的自定义测试适配器。 @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + /TestAdapterPath 参数需要一个值，该值是自定义测试适配器所在位置的路径。示例: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + "TestAdapterPath" 中指定的路径“{0}”无效。错误: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + 找不到提供的自定义测试适配器搜索路径，请提供一个有效路径，然后重试。 The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + "TestAdapterPath" 中指定的路径“{0}”不包含任何测试适配器，请提供有效路径，然后重试。 Could not start test run for the tests for Windows Phone app: {0}. - - + 无法启动针对 Windows Phone 应用的测试的测试运行: {0}。 Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + 使用隔离模式为 Windows Phone 应用运行单元测试。使用 /InIsolation 参数取消此警告。 Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + 代码覆盖率不适用于 Windows Phone 应用。已为此测试运行跳过代码覆盖率分析。 Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + 为 Windows Phone 应用运行单元测试时不支持诊断数据适配器。从设置中删除诊断数据适配器设置。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + 应用包“{0}”没有测试执行器入口点。为对 Windows Phone 应用运行单元测试，使用 Windows Phone 应用单元测试应用项目创建应用包。 Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + 使用框架 {0} 运行测试。指定 /Framework:{1} 取消此警告。 No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + 在指定测试容器中找不到任何测试。此外，Microsoft Windows 应用商店单元测试适配器不支持 .appxbundle 文件。在创建应用包时创建一个 appx (将“生成应用程序包”选项设置为“从不”)并重试。 @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel 指定并行执行测试。默认情况下，最多 可能会使用计算机上所有可用的内核。 @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + 参数 {0} 不应出现在 "Parallel" 命令中。指定不带参数的命令(示例: vstest.console.exe myTests.dll /Parallel)，然后重试。 Cannot be null or empty - - + 不能为 NULL 或为空 --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<Port> 套接字连接和接收事件消息的端口。 The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + --Port|/Port 参数需要为整数的端口号。指定用于套接字连接以及接收事件消息的端口。 Unable to find the assembly under test. Please make sure that the project is built. - - + 测试下找不到程序集。请确保已生成该项目。 The Path {0} does not exist. - - + 路径 {0} 不存在。 --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<BuildBasePath> 包含临时输出的目录。 -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<Configuration> 项目为调试/发布等生成的配置 The given configuration is invalid. - - + 给定的配置无效。 -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<Output> 包含要运行的二进制文件的目录。 The BuildBasePath was not found, provide a valid path and try again. - - + 找不到 BuildBasePath，请提供有效的路径，然后重试。 The Output path was not found, provide a valid path and try again. - - + 找不到 Output 路径，请提供有效的路径，然后重试。 Additional Information Messages: - - + 其他信息性消息: Days - - + 天 Error Message: - - + 错误消息: Total time: {0:0.0000} {1} - - + 总时间: {0:0.0000} {1} Hours - - + 小时 Could not find a test logger with URI or FriendlyName '{0}'. - - + 找不到 URI 或 FriendlyName 为“{0}”的测试记录器。 Minutes - - + 分钟 Seconds - - + 秒 Stack Trace: - - + 堆栈跟踪: Standard Error Messages: - - + 标准错误消息: Standard Output Messages: - - + 标准输出消息: Attachments: - - + 附件: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + {0} 中没有可用测试。请确保安装了适当的测试发现器和执行器且平台和框架版本设置合适，然后重试。 @@ -867,34 +750,29 @@ Skipped - - + 已跳过 Discovery failed for given sources. Exception : {0} - - + 针对给定源的发现失败。异常: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<ParentProcessId> 父进程的进程 ID 负责启动当前进程。 The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + --ParentProcessId|/ParentProcessId 参数要求整数形式的进程 ID。指定启动此进程的父进程的进程 ID。 Arguments: - - + 参数: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<Path to log file> 启用测试平台的日志。 日志将写入所提供的文件。 @@ -917,21 +794,18 @@ The file {0} provided is read only - - + 提供的文件 {0} 是只读文件 Timeout to connect or process request for DesignModeClient on port: {0} 连接或处理端口 {0} 上 DesignModeClient 的请求超时 - - + Not Run 未运行 - - + RunSettings arguments: @@ -942,14 +816,12 @@ 通过命令行传递 runsettings 配置的参数。参数可以指定为名称-值对，其形式为“-- ”后跟 [名称]=[值]。请注意 -- 后的空格。 使用空格分隔多个 [名称]=[值]. 有关 RunSettings 参数支持的详细信息，请访问: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token 所提供的一个或多个 runsettings 包含无效令牌 - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ -ResultsDirectory | / ResultsDirectory 如果不存在测试结果目录，则将在指定路径中创建。 示例 /ResultsDirectory:<pathToResultsDirectory> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory /ResultsDirectory 参数需要一个值，应在其中保存测试结果。例如: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} “ResultsDirectory”中指定的路径“{0}”无效。错误: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process /InIsolation 标志已弃用。测试始终在单独的进程中运行 - - + Logging Vstest Diagnostics in file: {0} 在文件 {0} 中记录 Vstest 诊断 - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<DataCollector FriendlyName> 启用数据收集器以运行测试。可在此处获取详细信息: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. 数据收集器友好名称“{0}”无效。将忽略数据收集器。 - - + Debug Traces Messages: 调试跟踪消息: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ Example: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. 测试运行已中止。 - - + Test Run Canceled. 测试运行已取消。 - - + Error opening response file '{0}' 打开响应文件“{0}”时出错 - - + @<file> Read response file for more options. @<file> 有关更多选项，请阅读响应文件。 - - + Total tests: Unknown 测试总数: 未知 - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. 此外，还可以使用 /TestAdapterPath 命令指定测试适配器的路径。示例 /TestAdapterPath:<pathToCustomAdapters>。 - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions 即将被弃用。请改为使用 /TestAdapterPath。 - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> 示例: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. --Collect|/如果使用测试设置配置了测试运行，则不支持收集:“{0}”。 - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. 除通过运行设置配置的代码覆盖率和 Microsoft Fakes 之外，嵌入测试设置不支持其他数据收集器。请参阅 https://aka.ms/vstest-configure-datacollector 了解详细信息。运行测试: {0}。 - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ 更改控制台记录器的诊断级别前缀，如下所示 示例: /logger:console;prefix=<Defaults to "false"> 此处为控制台记录器的详细信息: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. 此平台不支持通过 CollectDump for Blame 选项收集故障转储。 - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. 追责时指定的追责参数 {0} 无效。忽略此参数。 - - + Diag file path '{0}' is not valid. 诊断文件路径“{0}”无效。 - - + Blame argument '{0}' is not valid. 追责参数“{0}”无效。 - - + Diag argument '{0}' is not valid. 诊断参数“{0}”无效。 - - + Logger argument '{0}' is not valid. 记录器参数“{0}”无效。 - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". 不支持 Framework35。对于面向 .Net Framework 3.5 的项目，将在 CLR 4.0“兼容性模式”中运行测试。 - - + Test run in progress 正在运行测试 - - + Total tests: {0} 测试总数: {0} - - + Failed: {0} 失败数: {0} - - + Passed: {0} 通过数: {0} - - + Skipped: {0} 跳过数: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. 参数 {0} 无效。请使用 /help 选项检查有效参数的列表。 - - + A total of {0} test files matched the specified pattern. 总共 {0} 个测试文件与指定模式相匹配。 - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") 测试运行参数自变量“{0}”无效。请使用以下格式。 格式: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. 此平台不支持通过 CollectDump with TestTimeout for Blame 选项收集挂起转储。 - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - 失败: {1}，通过: {2}，已跳过: {3}，总计: {4}，持续时间: {5} - - + None 无 - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ 示例: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. 环境变量“{0}”已定义，但它被 -Environment 参数替代。 - - + Test Run Aborted with error {0}. diff --git a/src/vstest.console/Resources/xlf/Resources.zh-Hant.xlf b/src/vstest.console/Resources/xlf/Resources.zh-Hant.xlf index f798fda1e2..a22631d896 100644 --- a/src/vstest.console/Resources/xlf/Resources.zh-Hant.xlf +++ b/src/vstest.console/Resources/xlf/Resources.zh-Hant.xlf @@ -4,20 +4,17 @@ '{0}' not found. - - + 找不到 '{0}'。 The following Test Discovery Add-Ins are available: - - + 可使用下列測試探索增益集: The following Test Execution Add-Ins are available: - - + 可使用下列測試執行增益集: @@ -27,14 +24,12 @@ {0}: {1} - - + {0}: {1} The following Test Logger Add-Ins are available: - - + 可使用下列測試記錄器增益集: @@ -44,8 +39,7 @@ Error: {0} - - + 錯誤: {0} @@ -55,70 +49,59 @@ The parameter "{0}" should be provided only once. - - + 參數 " {0}" 應該僅提供一次。 Exception occurred when instantiating extension '{0}': {1} - - + 產生延伸模組時發生例外狀況 '{0}': {1} The following Tests are available: - - + 可使用下列測試: Unrecognized parameter "{0}". - - + 無法辨識的參數 "{0}"。 The test source file "{0}" provided was not found. - - + 找不到提供的測試來源檔案 "{0}"。 The Test Logger URI '{0}' is not valid. The Test Logger will be ignored. - - + 測試記錄器 URI '{0}' 無效。將忽略測試記錄器。 Information: {0} - - + 資訊: {0} Warning: {0} - - + 警告: {0} -?|--Help|/?|/Help Display this usage message. - - + -?|--Help|/?|/Help 顯示此使用方式訊息。 Copyright (c) Microsoft Corporation. All rights reserved. - - + Copyright (C) Microsoft Corporation. 著作權所有，並保留一切權利。 Microsoft (R) Test Execution Command Line Tool Version {0} - - + Microsoft (R) Test Execution Command Line Tool {0} 版 @@ -134,8 +117,7 @@ Change the diagnostic level prefix for console logger as shown below Example: /logger:console;prefix=<Defaults to "false"> More info on Console Logger here : https://aka.ms/console-logger - - + --logger|/logger:<記錄器 URI/易記名稱> 指定測試結果的記錄器。例如，使用 /logger:trx[;LogFileName=<預設為唯一的檔案名稱>]， 將結果記錄至 Visual Studio 測試結果檔案 (TRX) @@ -151,8 +133,7 @@ Description: Runs tests from the specified files. - - + 描述: 從指定的檔案執行測試。 @@ -162,20 +143,17 @@ Usage: vstest.console.exe [Arguments] [Options] [[--] <RunSettings arguments>...]] - - + 用法: vstest.console.exe [引數] [選項] [[--] <RunSettings 引數>...]] No test source files were specified. - - + 未指定測試來源檔案。 No arguments were specified. - - + 未指定引數。 @@ -185,8 +163,7 @@ Examples: mytestproject.dll mytestproject.dll myothertestproject.exe testproject*.dll my*project.dll - - + [TestFileNames] 從指定的檔案或萬用字元模式執行測試。分隔多個測試檔名稱或模式 由空格分隔。將主控台記錄器詳細程度設定為詳細來檢視符合的測試檔案。 @@ -196,58 +173,49 @@ The following Settings Providers Add-Ins are available: - - + 可使用下列設定提供者增益集: --Settings|/Settings:<Settings File> Settings to use when running tests. - - + --Settings|/Settings:<設定檔> 執行測試時要使用的設定。 The /Settings parameter requires a settings file to be provided. - - + /Settings 參數要求必須提供設定檔。 The Settings file '{0}' could not be found. - - + 找不到設定檔 '{0}'。 Test Run Failed. - - + 測試回合失敗。 Test Run Successful. - - + 測試回合成功。 Argument {0} is not expected in the 'InIsolation' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /InIsolation) and try again. - - + 'InIsolation' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /InIsolation)，並再試一次。 The /UseVsixExtensions parameter requires a value. If 'true', the installed VSIX extensions (if any) will be used in the test run. If false, they will be ignored. Example: /UseVsixExtensions:true - - + /UseVsixExtensions 參數需要一個值。如果為 'true'，已安裝的 VSIX 延伸模組 (如果有的話) 將用於測試回合。如果為 false，則會加以忽略。範例: /UseVsixExtensions:true Argument {0} is not expected in the 'UseVsixExtensions' command. Specify the command indicating whether the vsix extensions should be used or skipped (Example: vstest.console.exe myTests.dll /UseVsixExtensions:true) and try again. - - + 'UseVsixExtensions' 命令中不應該使用引數 {0}。請指定命令指出應該使用或略過 VSIX 延伸模組 (範例: vstest.console.exe myTests.dll /UseVsixExtensions:true) 並再試一次。 @@ -255,8 +223,7 @@ Runs the tests in an isolated process. This makes vstest.console.exe process less likely to be stopped on an error in the tests, but tests may run slower. - - + --InIsolation|/InIsolation 在隔離的處理序中執行測試。這樣會降低 vstest.console.exe 處理序在測試中發生錯誤而停止的可能性，但是測試 @@ -267,8 +234,7 @@ This makes vstest.console.exe process use or skip the VSIX extensions installed(if any) in the test run. Example /UseVsixExtensions:true - - + /UseVsixExtensions 這可讓 vstest.console.exe 處理序使用或略過測試回合中 已安裝的 VSIX 延伸模組 (如果有的話)。 @@ -276,14 +242,12 @@ The /BatchSize argument requires the size of the batch. Example: /BatchSize:10 - - + /BatchSize 引數必須有批次的大小。範例: /BatchSize:10 Invalid batch size {0}. The batch size should be greater than zero. Example: /BatchSize:10 - - + 批次大小無效 {0}。批次大小應該大於零。範例: /BatchSize:10 @@ -291,8 +255,7 @@ >vstest.console.exe tests.dll To run tests with additional settings such as data collectors: >vstest.console.exe tests.dll /Settings:Local.RunSettings - - + 執行測試: >vstest.console.exe tests.dll 執行測試，同時附上像是資料收集器等其他設定: @@ -301,67 +264,58 @@ /ListDiscoverers Lists installed test discoverers. - - + /ListDiscoverers 列出已安裝的測試探索程式。 /ListExecutors Lists installed test executors. - - + /ListExecutors 列出已安裝的測試執行程式。 /ListLoggers Lists installed test loggers. - - + /ListLoggers 列出已安裝的測試記錄器。 /ListSettingsProviders Lists installed test settings providers. - - + /ListSettingsProviders 列出已安裝的測試設定提供者。 -lt|--ListTests|/lt|/ListTests:<File Name> Lists all discovered tests from the given test container. - - + -lt|--ListTests|/lt|/ListTests:<檔案名稱> 列出所有從指定測試容器探索到的測試。 Time elapsed : - - + 經過時間: The /Tests argument requires one or more specific test names or their substrings. Examples: /Tests:TestsMethod1, /Tests:TestMethod1,method2 - - + /Tests 引數必須有一或多個特定的測試名稱或它們的子字串。 範例: /Tests:TestsMethod1, /Tests:TestMethod1,method2 A total of {0} tests were discovered but no test matches the specified selection criteria({1}). Use right value(s) and try again. - - + 已探索到總計 {0} 個測試，但沒有測試符合指定的選取準則 ({1})。請使用正確的值，並再試一次。 , - - + ， @@ -379,96 +333,81 @@ Using Isolation mode to run the tests as diagnostic data adapters were enabled in the runsettings. Use the /inIsolation parameter to suppress this warning. - - + 使用隔離模式執行測試，因為在 runsettings 中已啟用診斷資料配接器。使用 /inIsolation 參數可隱藏這個警告。 Using Isolation mode to run unit tests for Windows Store apps. Use the /InIsolation parameter to suppress this warning. - - + 使用隔離模式執行 Windows 市集應用程式的單元測試。使用 /InIsolation 參數可隱藏這個警告。 Diagnostic data adapters are not supported when running unit tests for Windows Store apps. Remove diagnostic data adapters settings from settings. - - + 執行 Windows 市集應用程式的單元測試時，不支援診斷資料配接器。請從設定中移除診斷資料配接器設定。 FriendlyName: {0} - - + FriendlyName: {0} Uri: {0} - - + URI: {0} SettingName: {0} - - + SettingName: {0} Supported File Types: - - + 支援的檔案類型: {0} - - + {0} {0}, - - + {0}， Default Executor Uri: {0} - - + 預設執行程式 URI: {0} Uri: {0} - - + URI: {0} Invalid platform type:{0}. Valid platform types are x86, x64 and Arm. - - + 平台類型無效: {0}。有效的平台類型為 x86、x64 和 Arm。 The /Platform argument requires the target platform type for the test run to be provided. Example: /Platform:x86 - - + /Platform 引數需要提供測試回合的目標平台類型。範例: /Platform:x86 --Platform|/Platform:<Platform type> Target platform architecture to be used for test execution. Valid values are x86, x64 and ARM. - - + --Platform|/Platform:<平台類型> 用於測試執行的目標平台架構。 有效值為 x86、x64 和 ARM。 Using Isolation mode to run tests as required by effective Platform:{0} and .Net Framework:{1} settings for test run. Use the /inIsolation parameter to suppress this warning. - - + 依照測試回合的有效平台 {0} 和 .Net Framework {1} 設定的要求，使用隔離模式執行測試。使用 /inIsolation 參數可隱藏這個警告。 @@ -476,8 +415,7 @@ Target .Net Framework version to be used for test execution. Valid values are ".NETFramework,Version=v4.5.1", ".NETCoreApp,Version=v1.0" etc. Other supported values are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + --Framework|/Framework:<Framework 版本> 用於測試執行的目標.Net Framework 版本。 有效的值為 ".NETFramework,Version=v4.5.1"、".NETCoreApp,Version=v1.0" 等等。 @@ -485,20 +423,17 @@ The /Framework argument requires the target .Net Framework version for the test run. Example: /Framework:".NETFramework,Version=v4.5.1" - - + /Framework 引數需要測試回合的目標 .NET Framework 版本。 範例: /Framework:".NETFramework,Version=v4.5.1" Invalid .Net Framework version:{0}. Please give the fullname of the TargetFramework(Example: .NETCoreApp,Version=v2.0). Other supported .Net Framework versions are Framework40, Framework45, FrameworkCore10 and FrameworkUap10. - - + .Net Framework 版本無效:{0}。請提供 TargetFramework 的全名 (例如: .NETCoreApp,Version=v2.0)。其他支援的 .Net Framework 版本為 Framework40、Framework45、FrameworkCore10 以及 FrameworkUap10。 Could not start test run for unit tests for Windows Store app: {0}. - - + 無法針對 Windows 市集應用程式的單元測試啟動測試回合: {0}。 @@ -511,8 +446,7 @@ Examples: /TestCaseFilter:"Priority=1" /TestCaseFilter:"(FullyQualifiedName~Nightly |Name=MyTestMethod)" - - + --TestCaseFilter|/TestCaseFilter:<Expression> 執行符合指定運算式的測試。 <Expression> 的格式為 <property>Operator<value>[|&<Expression>] @@ -527,78 +461,66 @@ The /TestCaseFilter argument requires the filter value. Filter value can be <property>=<value> type. Examples: "Priority=1", "TestCategory=Nightly" - - + /TestCaseFilter 引數需要篩選值。 篩選值可以是 <property>=<value> 類型。 範例: "Priority=1", "TestCategory=Nightly" The /TestCaseFilter argument cannot be specified with /Tests. Filtering of test cases is not applicable when tests are specified. - - + /TestCaseFilter 引數無法與 /Tests 一起指定。若已指定測試，則篩選測試案例不適用。 {0} is built for {1}/{2}. The test assemblies specified in a run should have a common target .Net framework and platform. - - + {0} 為針對 {1}/{2} 所建置。回合中指定的測試組件應該具有共同的目標 .Net Framework 和平台。 Only one app package (.appx file) can be specified for running tests. - - + 您只能為執行測試指定一個應用程式套件 (.appx 檔)。 Starting test discovery, please wait... - - + 正在啟動測試探索，請稍候... Starting test execution, please wait... - - + 正在啟動測試執行，請稍候... Reading diagnostic data adapter settings threw an running '{0}'. All diagnostic data adapters will be skipped in this run. - - + 讀取診斷資料配接器設定時擲回執行中的 '{0}'。這個回合中將略過所有診斷資料配接器。 /EnableCodeCoverage Enables data collector 'CodeCoverage' for the test run. - - + /EnableCodeCoverage 為測試回合啟用資料收集器 'CodeCoverage'。 Argument {0} is not expected in the 'EnableCodeCoverage' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /EnableCodeCoverage) and try again. - - + 'EnableCodeCoverage' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /EnableCodeCoverage)，並再試一次。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Store apps, create app package using Windows Store app Unit Test Library project. - - + 應用程式套件 '{0}' 沒有測試執行程式進入點。若要執行 Windows 市集應用程式的單元測試，請使用 Windows 市集應用程式單元測試程式庫專案建立應用程式套件。 Code coverage is not available for Windows Store apps. Code coverage analysis skipped for this test run. - - + Windows 市集應用程式無法使用程式碼涵蓋範圍。將略過這個測試回合的程式碼涵蓋範圍分析。 A total of {0} tests were discovered but some tests do not match the specified selection criteria({1}). Use right value(s) and try again. - - + 已探索到總計 {0} 個測試，但有些測試不符合指定的選取準則 ({1})。請使用正確的值並再試一次。 @@ -606,8 +528,7 @@ This makes vstest.console.exe process use custom test adapters from a given path (if any) in the test run. Example /TestAdapterPath:<pathToCustomAdapters> - - + --TestAdapterPath|/TestAdapterPath 這可讓 vstest.console.exe 處理序在測試回合中， 使用指定路徑 (如有指定) 中的自訂測試配接器。 @@ -615,68 +536,57 @@ The /TestAdapterPath parameter requires a value, which is path of a location containing custom test adapters. Example: /TestAdapterPath:c:\MyCustomAdapters - - + /TestAdapterPath 參數需要一個值，這個值是包含自訂測試配接器之位置的路徑。範例: /TestAdapterPath:c:\MyCustomAdapters The path '{0}' specified in the 'TestAdapterPath' is invalid. Error: {1} - - + 'TestAdapterPath' 中指定的路徑 '{0}' 無效。錯誤: {1} The custom test adapter search path provided was not found, provide a valid path and try again. - - + 找不到提供的自訂測試配接器搜尋路徑。請提供有效的路徑，並再試一次。 The path '{0}' specified in the 'TestAdapterPath' does not contain any test adapters, provide a valid path and try again. - - + 'TestAdapterPath' 中指定的路徑 '{0}' 不包含任何測試配接器。請提供有效的路徑，並再試一次。 Could not start test run for the tests for Windows Phone app: {0}. - - + 無法為 Windows Phone 應用程式的測試啟動測試回合: {0}。 Using Isolation mode to run unit tests for Windows Phone apps. Use the /InIsolation parameter to suppress this warning. - - + 使用隔離模式執行 Windows Phone 應用程式的單元測試。使用 /InIsolation 參數可隱藏這個警告。 Code coverage is not available for Windows Phone apps. Code coverage analysis skipped for this test run. - - + Windows Phone 應用程式無法使用程式碼涵蓋範圍。將略過這個測試回合的程式碼涵蓋範圍分析。 Diagnostic data adapters are not supported when running unit tests for Windows Phone apps. Remove diagnostic data adapters settings from settings. - - + 執行 Windows Phone 應用程式的單元測試時，不支援診斷資料配接器。請從設定中移除診斷資料配接器設定。 App package '{0}' does not has test executor entry point. For running unit tests for Windows Phone apps, create app package using Windows Phone Unit Test App project. - - + 應用程式套件 '{0}' 沒有測試執行程式進入點。若要執行 Windows Phone 應用程式的單元測試，請使用 Windows Phone 單元測試應用程式專案建立應用程式套件。 Using framework {0} to run the tests. Specify /Framework:{1} to suppress this warning. - - + 使用架構 {0} 執行測試。指定 /Framework:{1} 可隱藏這個警告。 No test found in the specified test containers. Additionally, Microsoft Windows Store Unit test adapter does not support .appxbundle files. Create an appx (set Generate App bundle option to Never) when creating App Package and try again. - - + 在指定的測試容器中找不到測試。此外，Microsoft Windows 市集單元測試配接器不支援 .appxbundle 檔案。請在建立應用程式套件時建立 appx (將 [產生應用程式套件組合] 選項設定為 [永不])，並再試一次。 @@ -684,8 +594,7 @@ Specifies that the tests be executed in parallel. By default up to all available cores on the machine may be used. The number of cores to use may be configured using a settings file. - - + --Parallel|/Parallel 指定平行執行測試。根據預設，最多會使用 機器上所有的可用核心。可使用設定檔設定 @@ -693,166 +602,140 @@ Argument {0} is not expected in the 'Parallel' command. Specify the command without the argument (Example: vstest.console.exe myTests.dll /Parallel) and try again. - - + 'Parallel' 命令中不應該使用引數 {0}。請指定不加引數的命令 (範例: vstest.console.exe myTests.dll /Parallel)，並再試一次。 Cannot be null or empty - - + 不可為 null 或空白 --Port|/Port:<Port> The Port for socket connection and receiving the event messages. - - + --Port|/Port:<連接埠> 通訊端連線以及接收事件訊息的連接埠。 The --Port|/Port argument requires the port number which is an integer. Specify the port for socket connection and receiving the event messages. - - + --Port|/Port 引數需要整數的連接埠號碼。指定用於通訊端連線以及接收事件訊息的連接埠。 Unable to find the assembly under test. Please make sure that the project is built. - - + 找不到正在進行測試的組件。請確定已建置專案。 The Path {0} does not exist. - - + 路徑 {0} 不存在。 --BuildBasePath|/BuildBasePath:<BuildBasePath> The directory containing the temporary outputs. - - + --BuildBasePath|/BuildBasePath:<建置基底路徑> 包含暫存輸出的目錄。 -c|--Configuration|/c|/Configuration:<Configuration> The configuration the project is built for i.e. Debug/Release - - + -c|--Configuration|/c|/Configuration:<組態> 建置專案標的組態，例如，偵錯/發行 The given configuration is invalid. - - + 給定的組態無效。 -o|--Output|/o|/Output:<Output> The directory containing the binaries to run. - - + -o|--Output|/o|/Output:<輸出> 包含要執行的二進位檔案的目錄。 The BuildBasePath was not found, provide a valid path and try again. - - + 找不到 BuildBasePath。請提供有效的路徑，並再試一次。 The Output path was not found, provide a valid path and try again. - - + 找不到輸出路徑。請提供有效的路徑，並再試一次。 Additional Information Messages: - - + 其他資訊訊息: Days - - + 日 Error Message: - - + 錯誤訊息: Total time: {0:0.0000} {1} - - + 時間總計: {0:0.0000} {1} Hours - - + 小時 Could not find a test logger with URI or FriendlyName '{0}'. - - + 找不到具有 URI 或 FriendlyName '{0}' 的測試記錄器。 Minutes - - + 分鐘 Seconds - - + 秒 Stack Trace: - - + 堆疊追蹤: Standard Error Messages: - - + 標準錯誤訊息: Standard Output Messages: - - + 標準輸出訊息: Attachments: - - + 附件: {0} - - + {0} No test is available in {0}. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again. - - + {0} 中沒有可供使用的測試。請確定已安裝適當的測試探索程式及執行程式、平台與 Framework 版本設定，並再試一次。 @@ -867,34 +750,29 @@ Skipped - - + 已跳過 Discovery failed for given sources. Exception : {0} - - + 給定來源的探索失敗。例外狀況: {0} --ParentProcessId|/ParentProcessId:<ParentProcessId> Process Id of the Parent Process responsible for launching current process. - - + --ParentProcessId|/ParentProcessId:<父處理序識別碼> 負責啟動目前處理序的父處理序之處理序識別碼。 The --ParentProcessId|/ParentProcessId argument requires the process id which is an integer. Specify the process id of the parent process that launched this process. - - + --ParentProcessId|/ParentProcessId 引數需要整數的處理序識別碼。請為已啟動這個處理序的父處理序指定處理序識別碼。 Arguments: - - + 引數: @@ -905,8 +783,7 @@ Change the trace level for logs as shown below Example: /Diag:<Path to log file>;tracelevel=<Defaults to "verbose"> Allowed values for tracelevel: off, error, warning, info and verbose. - - + --Diag|/Diag:<日誌檔路徑> 啟用測試平台的記錄檔。 記錄會寫入提供的檔案。 @@ -917,21 +794,18 @@ The file {0} provided is read only - - + 提供的檔案 {0} 為唯讀 Timeout to connect or process request for DesignModeClient on port: {0} 連線或處理連接埠 {0} 上對於 DesignModeClient 之要求的逾時時間: - - + Not Run 未執行 - - + RunSettings arguments: @@ -942,14 +816,12 @@ 透過命令列傳遞 runsettings 組態的引數。引數可以接在 "-- " 之後，以 [名稱]=[值] 的格式指定名稱/值配對。請注意 -- 之後的空格。 使用空格以隔開多個 [名稱]=[值]。 RunSettings 引數支援的詳細資訊: https://aka.ms/vstest-runsettings-arguments - - + One or more runsettings provided contain invalid token 提供的一或多個 runsettings 包含無效的語彙基元 - - + --ResultsDirectory|/ResultsDirectory @@ -958,52 +830,44 @@ --ResultsDirectory|/ResultsDirectory 若不存在，將會於指定路徑中建立測試結果目錄。 範例 /ResultsDirectory:<結果目錄路徑> - - + The /ResultsDirectory parameter requires a value, where the test results should be saved. Example: /ResultsDirectory:c:\MyTestResultsDirectory /ResultsDirectory 參數需要值，亦即測試結果的儲存位置。範例: /ResultsDirectory:c:\MyTestResultsDirectory - - + The path '{0}' specified in the 'ResultsDirectory' is invalid. Error: {1} 'ResultsDirectory' 中指定的路徑 '{0}' 無效。錯誤: {1} - - + The /InIsolation flag is deprecated. The tests are always run in a separate process /InIsolation 旗標已標示即將淘汰。測試一律會在個別的處理序中執行 - - + Logging Vstest Diagnostics in file: {0} 在檔案 {0} 中記錄 Vstest 診斷 - - + --Collect|/Collect:<DataCollector FriendlyName> Enables data collector for the test run. More info here : https://aka.ms/vstest-collect --Collect|/Collect:<資料收集器易記名稱> 為測試回合啟用資料收集器。此處有詳細資訊: https://aka.ms/vstest-collect - - + The Data Collector friendly name '{0}' is not valid. The Data Collector will be ignored. 資料收集器的易記名稱 '{0}' 無效。該資料收集器將予忽略。 - - + Debug Traces Messages: 偵錯追蹤訊息: - - + --Blame|/Blame:[CollectDump];[CollectAlways]=[Value];[DumpType]=[Value] @@ -1030,78 +894,66 @@ 範例: /Blame /Blame:CollectDump /Blame:CollectDump;CollectAlways=true;DumpType=full - - + Test Run Aborted. 測試回合已中止。 - - + Test Run Canceled. 測試回合已取消。 - - + Error opening response file '{0}' 開啟回應檔案 '{0}' 時發生錯誤 - - + @<file> Read response file for more options. @<檔案> 讀取回應檔以取得更多選項。 - - + Total tests: Unknown 測試數總計: 未知 - - + {0} {1} {0} {1} - - + Additionally, path to test adapters can be specified using /TestAdapterPath command. Example /TestAdapterPath:<pathToCustomAdapters>. 此外，可使用 /TestAdapterPath 命令，指定要測試配接器的路徑。範例為 /TestAdapterPath:<自訂配接器的路徑>。 - - + /UseVsixExtensions is getting deprecated. Please use /TestAdapterPath instead. /UseVsixExtensions 即將淘汰。請改用 /TestAdapterPath。 - - + --DisableAutoFakes|/DisableAutoFakes:<true/false> Example: /DisableAutoFakes:true --DisableAutoFakes|/DisableAutoFakes:<true/false> 範例: /DisableAutoFakes:true - - + --Collect|/Collect:"{0}" is not supported if test run is configured using testsettings. 若使用測試設定來設定測試回合，則不支援 --Collect|/Collect:"{0}"。 - - + Data collectors other than Code Coverage and Microsoft Fakes configured via run settings are not supported with embedded test settings. Please see https://aka.ms/vstest-configure-datacollector for more information. Run settings: {0}. 除了程式碼涵蓋範圍與 Microsoft Fakes 以外，內嵌測試設定不支援透過回合設定來設定的資料收集器。如需詳細資訊，請參閱 https://aka.ms/vstest-configure-datacollector。回合設定: {0}。 - - + --logger|/logger:<Logger Uri/FriendlyName> @@ -1128,124 +980,104 @@ 變更主控台記錄器的診斷等級前置詞，如下所示 範例: /logger:console;prefix=<預設為 "false"> 主控台記錄器詳細資訊於此: https://aka.ms/console-logger - - + Collecting crash dumps by option CollectDump for Blame is not supported for this platform. 此平台不支援使用 CollectDump for Blame 選項收集損毀傾印。 - - + The blame parameter specified with blame, {0} is invalid. Ignoring this parameter. 以 blame 指定的 blame 參數 {0} 無效，即將忽略此參數。 - - + Diag file path '{0}' is not valid. 診斷檔案路徑 '{0}' 無效。 - - + Blame argument '{0}' is not valid. Blame 引數 '{0}' 無效。 - - + Diag argument '{0}' is not valid. 診斷引數 '{0}' 無效。 - - + Logger argument '{0}' is not valid. 記錄器引數 '{0}' 無效。 - - + Framework35 is not supported. For projects targeting .Net Framework 3.5, test will run in CLR 4.0 "compatibility mode". 不支援 Framework35。若是目標為 .Net Framework 3.5 的專案，就會在 CLR 4.0「相容模式」中執行測試。 - - + Test run in progress 測試回合正在進行中 - - + Total tests: {0} 測試數總計: {0} - - + Failed: {0} 失敗: {0} - - + Passed: {0} 通過: {0} - - + Skipped: {0} 跳過: {0} - - + The argument {0} is invalid. Please use the /help option to check the list of valid arguments. {0} 的引數無效。請使用 /help 選項查看有效引數的清單。 - - + A total of {0} test files matched the specified pattern. 總共有 {0} 個測試檔案與指定的模式相符。 - - + The test run parameter argument '{0}' is invalid. Please use the format below. Format: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") 測試回合參數的引數 '{0}' 無效。請使用下面的格式。 格式: TestRunParameters.Parameter(name=\"<name>\", value=\"<value>\") - - + Collecting hang dumps by option CollectDump with TestTimeout for Blame is not supported for this platform. 此平台不支援使用 Blame 的 CollectDump 及 TestTimeout 選項收集懸置傾印。 - - + {0} - Failed: {1}, Passed: {2}, Skipped: {3}, Total: {4}, Duration: {5} {0} - 失敗: {1}，通過: {2}，略過: {3}，總計: {4}，持續時間: {5} - - + None 無 - - + - {0} {1} - {0} {1} - - + -e|--Environment|/e|/Environment:<NAME>=<VALUE> @@ -1264,14 +1096,12 @@ 範例: -e:VARIABLE1=VALUE1 -e:ANOTHER_VARIABLE="VALUE WITH SPACES" -e:ANOTHER_VARIABLE="VALUE;seperated with;semicolons" - - + Environment variable '{0}' was already defined, but it's overridden by -Environment argument. 已定義環境變數 '{0}'，但其已由 -Environment 引數覆寫。 - - + Test Run Aborted with error {0}.