<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
  <file datatype="xml" source-language="en" target-language="ja" original="../PlatformResources.resx">
    <body>
      <trans-unit id="AbortForMaxFailedTestsCapabilityNotAvailable">
        <source>The current test framework does not implement 'IGracefulStopTestExecutionCapability' which is required for '--maximum-failed-tests' feature.</source>
        <target state="translated">現在のテスト フレームワークは、'--maximum-failed-tests' 機能に必要な 'IGracefulStopTestExecutionCapability' を実装していません。</target>
        <note>{Locked="IGracefulStopTestExecutionCapability"}{Locked="--maximum-failed-tests"}</note>
      </trans-unit>
      <trans-unit id="AbortForMaxFailedTestsDescription">
        <source>Extension used to support '--maximum-failed-tests'. When a given failures threshold is reached, the test run will be aborted.</source>
        <target state="translated">'--maximum-failed-tests' をサポートするために使用される拡張機能。指定されたエラーのしきい値に達すると、テストの実行が中止されます。</target>
        <note>{Locked="--maximum-failed-tests"}</note>
      </trans-unit>
      <trans-unit id="Aborted">
        <source>Aborted</source>
        <target state="translated">中止されました</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherCommandLineDescription">
        <source>Internal command line for artifact post-processing.</source>
        <target state="translated">アーティファクト ポスト プロセスの内部コマンド ライン。</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherDescription">
        <source>Dispatches artifact post-processing jobs selected by dotnet test.</source>
        <target state="translated">dotnet test によって選択されたアーティファクト ポスト プロセス ジョブをディスパッチします。</target>
        <note>Do not localize command name {Locked="dotnet test"}.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherDisplayName">
        <source>Artifact post-processing dispatcher</source>
        <target state="translated">アーティファクト ポスト プロセス ディスパッチャー</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherInvalidProcessorOutput">
        <source>The processed artifact must be an existing file under the output directory and cannot overwrite an input artifact.</source>
        <target state="translated">処理済みのアーティファクトは、出力ディレクトリ内の既存ファイルである必要があり、入力アーティファクトを上書きできません。</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherManifestNotFound">
        <source>The artifact post-processing manifest does not exist.</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストが存在しません。</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherManifestOptionDescription">
        <source>Path to the artifact post-processing manifest.</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストへのパス。</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherProcessorConflict">
        <source>Multiple artifact post-processors match '{0}'. The first registered processor, '{1}', will be used.</source>
        <target state="translated">複数のアーティファクト ポスト プロセッサ が '{0}' と一致します。最初に登録されたプロセッサ '{1}' が使用されます。</target>
        <note>{0} is an artifact kind or file extension. {1} is an extension UID.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherProcessorFailed">
        <source>Artifact post-processor '{0}' failed: {1}</source>
        <target state="translated">アーティファクト ポスト プロセッサ '{0}' が失敗しました: {1}</target>
        <note>{0} is the processor UID. {1} is the exception message.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherRequiresPipe">
        <source>The artifact post-processing dispatcher requires a dotnet test pipe.</source>
        <target state="translated">アーティファクト ポスト プロセス ディスパッチャーには dotnet test パイプが必要です。</target>
        <note>Do not localize command name {Locked="dotnet test"}.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingManifestInputMissingPath">
        <source>Artifact post-processing manifest input {0} does not have a path.</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストの入力 {0} にパスがありません。</target>
        <note>{0} is the zero-based input index.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingManifestInputsMustBeArray">
        <source>The artifact post-processing manifest inputs property must be an array.</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストの inputs プロパティは配列である必要があります。</target>
        <note>Do not localize property name {Locked="inputs"}.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingManifestInvalid">
        <source>The artifact post-processing manifest must have schemaVersion 1 and an outputDirectory.</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストには schemaVersion 1 と outputDirectory が必要です。</target>
        <note>Do not localize property names {Locked="schemaVersion"}{Locked="outputDirectory"}.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingManifestReadError">
        <source>Cannot read the artifact post-processing manifest: {0}</source>
        <target state="translated">アーティファクト ポスト プロセス マニフェストを読み取れません: {0}</target>
        <note>{0} is the exception message.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessorCapabilityContainsSeparator">
        <source>Artifact post-processor '{0}' declares capability '{1}', which cannot contain the semicolon separator.</source>
        <target state="translated">アーティファクト ポスト プロセス プロセッサ '{0}' は機能 '{1}' を宣言していますが、セミコロン区切り記号を含めることはできません。</target>
        <note>{0} is the processor UID. {1} is an artifact kind or file extension.</note>
      </trans-unit>
      <trans-unit id="ArtifactPostProcessorCapabilityInvalid">
        <source>Artifact post-processor '{0}' declares invalid capability '{1}'. Kinds cannot be blank, and fallback extensions must be lowercase and start with a dot.</source>
        <target state="translated">アーティファクト ポスト プロセッサ '{0}' は無効な機能 '{1}' を宣言しています。種類を空白にすることはできません。フォールバック拡張機能は小文字で、ドットで始まる必要があります。</target>
        <note>{0} is the processor UID. {1} is an artifact kind or file extension.</note>
      </trans-unit>
      <trans-unit id="CancellingTestSession">
        <source>Canceling the test session...</source>
        <target state="translated">テスト セッションを取り消しています...</target>
        <note />
      </trans-unit>
      <trans-unit id="BrowserPlatformNotSupportedOnOlderFrameworks">
        <source>Browser platform is only supported on .NET 7.0 or greater.</source>
        <target state="translated">ブラウザー プラットフォームは、.NET 7.0 以降でのみサポートされています。</target>
        <note>{Locked=".NET 7.0"}</note>
      </trans-unit>
      <trans-unit id="CannotCreateTestExecutionFilterErrorMessage">
        <source>Failed to create a test execution filter</source>
        <target state="translated">テスト実行フィルターを作成できませんでした</target>
        <note />
      </trans-unit>
      <trans-unit id="CannotCreateUniqueLogFileErrorMessage">
        <source>Failed to create the diagnostic log file '{0}' after {1} attempts. Last error: {2}</source>
        <target state="translated">診断ログ ファイル '{0}' の作成を {1} 回試行しましたが、失敗しました。最後のエラー: {2}</target>
        <note>{0} is the full path of the last log file that was tried. {1} is the number of attempts that were made. {2} is the error message of the last failed attempt.</note>
      </trans-unit>
      <trans-unit id="CannotRemoveEnvironmentVariableAtThisStageErrorMessage">
        <source>Cannot remove environment variables at this stage</source>
        <target state="translated">この段階では環境変数を削除できません</target>
        <note />
      </trans-unit>
      <trans-unit id="CannotRemoveEnvironmentVariableItIsLockedErrorMessage">
        <source>Extension '{0}' tried to remove environment variable '{1}' but it was locked by extension '{2}'</source>
        <target state="translated">拡張機能 '{0}' は環境変数 '{1}' を削除しようとしましたが、拡張機能 '{2}' によってロックされました</target>
        <note>{0} is the extension display name. {1} is the environment variable name. {2} is the display name of the extension that locked the environment variable.</note>
      </trans-unit>
      <trans-unit id="CannotSetEnvironmentVariableAtThisStageErrorMessage">
        <source>Cannot set environment variables at this stage</source>
        <target state="translated">この段階では環境変数を設定できません</target>
        <note />
      </trans-unit>
      <trans-unit id="CannotSetEnvironmentVariableItIsLockedErrorMessage">
        <source>Extension '{0}' tried to set environment variable '{1}' but it was locked by extension '{2}'</source>
        <target state="translated">拡張機能 '{0}' は環境変数 '{1}' を設定しようとしましたが、拡張機能 '{2}' によってロックされました</target>
        <note>{0} is the extension display name. {1} is the environment variable name. {2} is the display name of the extension that locked the environment variable.</note>
      </trans-unit>
      <trans-unit id="CannotStartProcessErrorMessage">
        <source>Cannot start process '{0}'</source>
        <target state="translated">プロセス '{0}' を開始できません</target>
        <note>{0} is the process file name.</note>
      </trans-unit>
      <trans-unit id="CommandLineInvalidArgumentsForOption">
        <source>Option '--{0}' has invalid arguments: {1}</source>
        <target state="translated">オプション '--{0}' に無効な引数があります: {1}</target>
        <note>{0} is the option name without the leading dashes. {1} is the invalid argument value or validation error.</note>
      </trans-unit>
      <trans-unit id="CommandLineInvalidArityErrorMessage">
        <source>Invalid arity, maximum must be greater than minimum</source>
        <target state="translated">arity が無効です。最大値は最小値より大きくする必要があります</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineInvalidConfiguration">
        <source>Invalid configuration for provider '{0}' (UID: {1}). Error: {2}</source>
        <target state="translated">プロバイダー '{0}' (UID: {1}) の構成が無効です。エラー: {2}</target>
        <note>{0} is the provider display name. {1} is the provider UID. {2} is the configuration error message.</note>
      </trans-unit>
      <trans-unit id="CommandLineInvalidOptionName">
        <source>Invalid option name '{0}', it must contain only letter and '-' (e.g. my-option)</source>
        <target state="translated">オプション名 '{0}' が無効です。文字と '-' のみを含む必要があります (例: my-option)</target>
        <note>{0} is the invalid option name. {Locked="-"}{Locked="my-option"}</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionExpectsAtLeastArguments">
        <source>Option '--{0}' from provider '{1}' (UID: {2}) expects at least {3} arguments</source>
        <target state="translated">プロバイダー '{1}' (UID:{2}) のオプション '-- {0}' には、少なくとも {3} 引数が必要です</target>
        <note>{0} is the option name without the leading dashes. {1} is the provider display name. {2} is the provider UID. {3} is the minimum number of expected arguments.</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionExpectsAtMostArguments">
        <source>Option '--{0}' from provider '{1}' (UID: {2}) expects at most {3} arguments</source>
        <target state="translated">プロバイダー '{1}' (UID:{2}) のオプション '-- {0}' には、最大 {3} 引数が必要です</target>
        <note>{0} is the option name without the leading dashes. {1} is the provider display name. {2} is the provider UID. {3} is the maximum number of expected arguments.</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionExpectsNoArguments">
        <source>Option '--{0}' from provider '{1}' (UID: {2}) expects no arguments</source>
        <target state="translated">プロバイダー '{1}' のオプション '--{0}' (UID:{2}) には引数が必要ありません</target>
        <note>{0} is the option name without the leading dashes. {1} is the provider display name. {2} is the provider UID.</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionIsDeclaredByMultipleProviders">
        <source>Option '--{0}' is declared by multiple providers: '{1}'</source>
        <target state="translated">オプション '--{0}' は複数のプロバイダーによって宣言されています: '{1}'</target>
        <note>{0} is the option name without the leading dashes. {1} is the list of provider display names.</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionIsDeclaredByMultipleProvidersWorkaround">
        <source>You can fix the previous option clash by overriding the option name using the configuration file</source>
        <target state="translated">構成ファイルを使用してオプション名をオーバーライドすることで、前のオプションの競合を修正できます</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineOptionIsReserved">
        <source>Option '--{0}' is reserved and cannot be used by providers: '{1}'</source>
        <target state="translated">オプション '--{0}' は予約されており、プロバイダーでは使用できません: '{1}'</target>
        <note>{0} is the option name without the leading dashes. {1} is the list of provider display names.</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionIsUsingReservedPrefix">
        <source>Option `--{0}` from provider '{1}' (UID: {2}) is using the reserved prefix '--internal'</source>
        <target state="translated">プロバイダー '{1}' のオプション '--{0}' (UID:{2}) は予約済みプレフィックス '--internal' を 使用しています</target>
        <note>{0} is the option name without the leading dashes. {1} is the provider display name. {2} is the provider UID. {Locked="--internal"}</note>
      </trans-unit>
      <trans-unit id="CommandLineOptionsNotReady">
        <source>The ICommandLineOptions has not been built yet.</source>
        <target state="translated">ICommandLineOptions はまだ構築されていません。</target>
        <note>{Locked="ICommandLineOptions"}</note>
      </trans-unit>
      <trans-unit id="CommandLineParserFailedToReadResponseFile">
        <source>Failed to read response file '{0}'. {1}.</source>
        <target state="translated">応答ファイル '{0}' を読み取れませんでした。{1}。</target>
        <note>{0} is the response file path. {1} is the full exception detail (ToString), not just the exception message.</note>
      </trans-unit>
      <trans-unit id="CommandLineParserResponseFileNotFound">
        <source>The response file '{0}' was not found</source>
        <target state="translated">応答ファイル '{0}' が見つかりませんでした</target>
        <note>{0} is the response file path.</note>
      </trans-unit>
      <trans-unit id="CommandLineParserUnclosedQuoteInCommandLine">
        <source>Unclosed quote in command line</source>
        <target state="translated">閉じられていないコマンド ラインの引用符</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineParserUnclosedQuoteInResponseFile">
        <source>Unclosed quote in response file at line {0}</source>
        <target state="translated">応答ファイルの {0} 行で引用符が閉じられていません</target>
        <note>{0} is the line number in the response file.</note>
      </trans-unit>
      <trans-unit id="CommandLineParserUnexpectedArgument">
        <source>Unexpected argument {0}</source>
        <target state="translated">予期しない引数 {0}</target>
        <note>{0} is the unexpected command-line argument.</note>
      </trans-unit>
      <trans-unit id="CommandLineParserUnexpectedSingleQuoteInArgument">
        <source>Unexpected single quote in argument: {0}</source>
        <target state="translated">引数に予期しない単一引用符が含まれています: {0}</target>
        <note>{0} is the command-line argument containing the unexpected single quote.</note>
      </trans-unit>
      <trans-unit id="CommandLineParserUnexpectedSingleQuoteInArgumentForOption">
        <source>Unexpected single quote in argument: {0} for option '--{1}'</source>
        <target state="translated">引数に予期しない単一引用符が含まれています: {0} オプション '--{1}' の場合</target>
        <note>{0} is the command-line argument containing the unexpected single quote. {1} is the option name without the leading dashes.</note>
      </trans-unit>
      <trans-unit id="CommandLineUnknownOption">
        <source>Unknown option '--{0}'</source>
        <target state="translated">不明なオプション: '--{0}'</target>
        <note>{0} is the unknown option name without the leading dashes.</note>
      </trans-unit>
      <trans-unit id="CommandLineValidationCommandLine">
        <source>Command line: {0}</source>
        <target state="translated">コマンド ライン: {0}</target>
        <note>{0} is the command line used to run the application.</note>
      </trans-unit>
      <trans-unit id="CompositeExtensionFactoryInstantiationFailedErrorMessage">
        <source>Failed to create an instance of composite extension '{0}'. See the inner exception for details.</source>
        <target state="translated">複合拡張機能 '{0}' のインスタンスを作成できませんでした。詳細については内部例外を参照してください。</target>
        <note>{0} is the extension type name.</note>
      </trans-unit>
      <trans-unit id="CompositeExtensionFactoryReturnedNullInstanceErrorMessage">
        <source>The factory for composite extension '{0}' returned a null instance.</source>
        <target state="translated">複合拡張機能 '{0}' のファクトリが null インスタンスを返しました。</target>
        <note>{0} is the extension type name.</note>
      </trans-unit>
      <trans-unit id="CompositeServiceFactoryInstanceAlreadyRegistered">
        <source>The same instance of 'CompositeExtensionFactory' is already registered</source>
        <target state="translated">'CompositeExtensionFactory' の同じインスタンスが既に登録されています</target>
        <note>{Locked="CompositeExtensionFactory"}</note>
      </trans-unit>
      <trans-unit id="CompositeTestExecutionFilterCannotContainNull">
        <source>A composite test execution filter cannot contain a null child filter.</source>
        <target state="translated">複合テスト実行フィルターには null の子フィルターを含めることはできません。</target>
        <note />
      </trans-unit>
      <trans-unit id="CompositeTestExecutionFilterRequiresTwoFilters">
        <source>A composite test execution filter requires at least two child filters.</source>
        <target state="translated">複合テスト実行フィルターには、少なくとも 2 つの子フィルターが必要です。</target>
        <note />
      </trans-unit>
      <trans-unit id="ConfigurationFileNotFound">
        <source>The configuration file '{0}' specified with '--config-file' could not be found.</source>
        <target state="translated">'--config-file' で指定された構成ファイル '{0}' が見つかりませんでした。</target>
        <note>{0} is the configuration file path. {Locked="--config-file"}</note>
      </trans-unit>
      <trans-unit id="ConfigurationManagerCannotFindDefaultJsonConfigurationErrorMessage">
        <source>Could not find the default json configuration</source>
        <target state="translated">既定の JSON 構成が見つかりませんでした</target>
        <note />
      </trans-unit>
      <trans-unit id="ConnectingToClientHost">
        <source>Connecting to client host '{0}' port '{1}'</source>
        <target state="translated">クライアント ホスト '{0}' ポート '{1}' に接続しています</target>
        <note>{0} is the client host name. {1} is the client port.</note>
      </trans-unit>
      <trans-unit id="ConsoleTestExecutionFilterFactoryDescription">
        <source>Creates the right test execution filter for console mode</source>
        <target state="translated">コンソール モードに適したテスト実行フィルターを作成します</target>
        <note />
      </trans-unit>
      <trans-unit id="ConsoleTestExecutionFilterFactoryDisplayName">
        <source>Console test execution filter factory</source>
        <target state="translated">コンソール テスト実行フィルター ファクトリ</target>
        <note />
      </trans-unit>
      <trans-unit id="CouldNotFindDirectoryErrorMessage">
        <source>Could not find directory '{0}'</source>
        <target state="translated">ディレクトリ '{0}' が見つかりませんでした。</target>
        <note>{0} is the directory path.</note>
      </trans-unit>
      <trans-unit id="DeprecatedEnvironmentVariableWarning">
        <source>Warning: The environment variable '{0}' is deprecated and will be removed in a future major version. Use '{1}' instead.</source>
        <target state="translated">警告: 環境変数 '{0}' は非推奨であり、今後のメジャー バージョンで削除される予定です。代わりに '{1}' を使用してください。</target>
        <note>{0} is the deprecated environment variable name. {1} is the replacement environment variable name.</note>
      </trans-unit>
      <trans-unit id="DiagnosticFileLevelWithAsyncFlush">
        <source>Diagnostic file (level '{0}' with async flush): {1}</source>
        <target state="translated">診断ファイル (レベル '{0}' で非同期フラッシュ): {1}</target>
        <note>{0} is the diagnostic log level, such as verbose. {1} is the path to the diagnostic log file.</note>
      </trans-unit>
      <trans-unit id="DiagnosticFileLevelWithFlush">
        <source>Diagnostic file (level '{0}' with sync flush): {1}</source>
        <target state="translated">診断ファイル (レベル '{0}' で同期フラッシュ): {1}</target>
        <note>{0} is the diagnostic log level, such as verbose. {1} is the path to the diagnostic log file.</note>
      </trans-unit>
      <trans-unit id="DiscoveredTestsInAssembly">
        <source>Discovered {0} test(s) in assembly</source>
        <target state="translated">アセンブリで {0} 個のテストが検出されました</target>
        <note>{0} is the number of discovered tests. The sentence is followed by the assembly path.</note>
      </trans-unit>
      <trans-unit id="DiscoveringTestsFrom">
        <source>Discovering tests from</source>
        <target state="translated">からテストを検出しています</target>
        <note />
      </trans-unit>
      <trans-unit id="DynamicExtensionAssemblyLoadFailedErrorMessage">
        <source>The assembly '{0}' of the extension '{1}' declared in the extension manifest '{2}' could not be loaded.</source>
        <target state="new">The assembly '{0}' of the extension '{1}' declared in the extension manifest '{2}' could not be loaded.</target>
        <note>{0} is the resolved assembly path. {1} is the extension display name. {2} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionAssemblyNotFoundErrorMessage">
        <source>The assembly '{0}' of the extension '{1}' declared in the extension manifest '{2}' was not found.</source>
        <target state="new">The assembly '{0}' of the extension '{1}' declared in the extension manifest '{2}' was not found.</target>
        <note>{0} is the resolved assembly path. {1} is the extension display name. {2} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionCannotRegisterTestFrameworkErrorMessage">
        <source>The extension '{0}' declared in the extension manifest '{1}' tried to register a test framework. Dynamically loaded extensions must not replace the test framework, because that would silently change which tests run and what results they report.</source>
        <target state="new">The extension '{0}' declared in the extension manifest '{1}' tried to register a test framework. Dynamically loaded extensions must not replace the test framework, because that would silently change which tests run and what results they report.</target>
        <note>{0} is the extension display name. {1} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionDuplicateIdConflictErrorMessage">
        <source>The extension id '{0}' is declared twice with different content: '{1}' in the extension manifest '{2}' and '{3}' in the extension manifest '{4}'. Ids must identify the same extension, otherwise one declaration would silently replace the other.</source>
        <target state="new">The extension id '{0}' is declared twice with different content: '{1}' in the extension manifest '{2}' and '{3}' in the extension manifest '{4}'. Ids must identify the same extension, otherwise one declaration would silently replace the other.</target>
        <note>{0} is the extension id. {1} and {3} are 'assembly path' plus 'type full name' descriptions of the conflicting declarations. {2} and {4} are manifest file paths.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionHookFailedErrorMessage">
        <source>The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' failed.</source>
        <target state="new">The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' failed.</target>
        <note>{0} is the full type name. {1} is the hook method name. {2} is the resolved assembly path. {3} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionHookMustNotBeAsyncVoidErrorMessage">
        <source>The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' is declared 'async void'. The platform invokes the hook synchronously, so it would return at its first await: anything it registers after that point would race the test application's own setup, and any failure would be lost. Make the hook synchronous.</source>
        <target state="new">The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' is declared 'async void'. The platform invokes the hook synchronously, so it would return at its first await: anything it registers after that point would race the test application's own setup, and any failure would be lost. Make the hook synchronous.</target>
        <note>{0} is the full type name. {1} is the hook method name. {2} is the resolved assembly path. {3} is the manifest file path. {Locked="'async void'"}</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionHookMustReturnVoidErrorMessage">
        <source>The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' returns '{4}' but must return 'void'. The platform invokes the hook synchronously, so a return value is never observed; a returned task in particular would never be awaited, and its registrations and failures would be lost.</source>
        <target state="new">The '{0}.{1}' extension hook from the assembly '{2}' declared in the extension manifest '{3}' returns '{4}' but must return 'void'. The platform invokes the hook synchronously, so a return value is never observed; a returned task in particular would never be awaited, and its registrations and failures would be lost.</target>
        <note>{0} is the full type name. {1} is the hook method name. {2} is the resolved assembly path. {3} is the manifest file path. {4} is the actual return type name. {Locked="'void'"}</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionHookNotFoundErrorMessage">
        <source>The type '{0}' in the assembly '{1}' declared in the extension manifest '{2}' does not expose a 'public static void' method named '{3}' taking an 'ITestApplicationBuilder' and a 'string[]'.</source>
        <target state="new">The type '{0}' in the assembly '{1}' declared in the extension manifest '{2}' does not expose a 'public static void' method named '{3}' taking an 'ITestApplicationBuilder' and a 'string[]'.</target>
        <note>{0} is the full type name. {1} is the resolved assembly path. {2} is the manifest file path. {3} is the expected method name. {Locked="'public static void'"}{Locked="'ITestApplicationBuilder'"}{Locked="'string[]'"}</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestDirectoryNotReadableErrorMessage">
        <source>The directory '{0}' could not be searched for extension manifests, so the platform cannot tell whether any extension had to be loaded. Remove '{1}' from the command line to skip extension manifest discovery.</source>
        <target state="new">The directory '{0}' could not be searched for extension manifests, so the platform cannot tell whether any extension had to be loaded. Remove '{1}' from the command line to skip extension manifest discovery.</target>
        <note>{0} is the directory path. {1} is the command line option that enables the feature.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestDuplicatePropertyErrorMessage">
        <source>The extension manifest '{0}' is invalid: the '{1}' property is declared more than once, so one of the declarations would be discarded.</source>
        <target state="new">The extension manifest '{0}' is invalid: the '{1}' property is declared more than once, so one of the declarations would be discarded.</target>
        <note>{0} is the manifest file path. {1} is the name of the duplicated JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryDuplicatePropertyErrorMessage">
        <source>The extension manifest '{0}' is invalid: the extension at index {1} declares the '{2}' property more than once, so one of the declarations would be discarded.</source>
        <target state="new">The extension manifest '{0}' is invalid: the extension at index {1} declares the '{2}' property more than once, so one of the declarations would be discarded.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the extension. {2} is the name of the duplicated JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryInvalidAssemblyPathErrorMessage">
        <source>The extension manifest '{0}' is invalid: the assembly path '{2}' of the extension at index {1} is not a valid path.</source>
        <target state="new">The extension manifest '{0}' is invalid: the assembly path '{2}' of the extension at index {1} is not a valid path.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the extension. {2} is the invalid assembly path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryMissingPropertyErrorMessage">
        <source>The extension manifest '{0}' is invalid: the extension at index {1} is missing the required '{2}' property, or its value is empty.</source>
        <target state="new">The extension manifest '{0}' is invalid: the extension at index {1} is missing the required '{2}' property, or its value is empty.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the extension. {2} is the name of the missing JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryNotObjectErrorMessage">
        <source>The extension manifest '{0}' is invalid: the element at index {1} of '{2}' must be a JSON object.</source>
        <target state="new">The extension manifest '{0}' is invalid: the element at index {1} of '{2}' must be a JSON object.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the element. {2} is the name of the JSON array property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryPropertyNotBooleanErrorMessage">
        <source>The extension manifest '{0}' is invalid: the '{2}' property of the extension at index {1} must be a JSON boolean.</source>
        <target state="new">The extension manifest '{0}' is invalid: the '{2}' property of the extension at index {1} must be a JSON boolean.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the extension. {2} is the name of the JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestEntryPropertyNotStringErrorMessage">
        <source>The extension manifest '{0}' is invalid: the '{2}' property of the extension at index {1} must be a JSON string.</source>
        <target state="new">The extension manifest '{0}' is invalid: the '{2}' property of the extension at index {1} must be a JSON string.</target>
        <note>{0} is the manifest file path. {1} is the zero-based index of the extension. {2} is the name of the JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestExtensionsPropertyNotArrayErrorMessage">
        <source>The extension manifest '{0}' is invalid: the '{1}' property must be a JSON array.</source>
        <target state="new">The extension manifest '{0}' is invalid: the '{1}' property must be a JSON array.</target>
        <note>{0} is the manifest file path. {1} is the name of the JSON property that has the wrong type.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestInvalidJsonErrorMessage">
        <source>The extension manifest '{0}' is not valid JSON. {1}</source>
        <target state="new">The extension manifest '{0}' is not valid JSON. {1}</target>
        <note>{0} is the manifest file path. {1} is the underlying JSON parser error message.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestMissingExtensionsPropertyErrorMessage">
        <source>The extension manifest '{0}' is invalid: the required '{1}' property is missing.</source>
        <target state="new">The extension manifest '{0}' is invalid: the required '{1}' property is missing.</target>
        <note>{0} is the manifest file path. {1} is the name of the missing JSON property.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestReadFailedErrorMessage">
        <source>The extension manifest '{0}' could not be read.</source>
        <target state="new">The extension manifest '{0}' could not be read.</target>
        <note>{0} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestRootNotObjectErrorMessage">
        <source>The extension manifest '{0}' is invalid: the top-level JSON element must be an object but '{1}' was found.</source>
        <target state="new">The extension manifest '{0}' is invalid: the top-level JSON element must be an object but '{1}' was found.</target>
        <note>{0} is the manifest file path. {1} is the JSON value kind that was found.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionManifestTrailingContentErrorMessage">
        <source>Unexpected content after the top-level JSON object.</source>
        <target state="new">Unexpected content after the top-level JSON object.</target>
        <note>Used as the parser-error detail when a manifest contains text after its closing brace.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionTypeNotFoundErrorMessage">
        <source>The type '{0}' was not found in the assembly '{1}' declared in the extension manifest '{2}'.</source>
        <target state="new">The type '{0}' was not found in the assembly '{1}' declared in the extension manifest '{2}'.</target>
        <note>{0} is the full type name. {1} is the resolved assembly path. {2} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionsLoadedEntry">
        <source>  {0} -&gt; {1} ({2}), declared in {3}</source>
        <target state="new">  {0} -&gt; {1} ({2}), declared in {3}</target>
        <note>{0} is the extension display name. {1} is the resolved assembly path. {2} is the full type name of the hook. {3} is the manifest file path.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionsLoadedHeader">
        <source>Dynamically loaded test platform extensions ({0}):</source>
        <target state="new">Dynamically loaded test platform extensions ({0}):</target>
        <note>{0} is the number of extensions that were loaded.</note>
      </trans-unit>
      <trans-unit id="DynamicExtensionsNotSupportedOnCurrentRuntimeErrorMessage">
        <source>The extension manifest '{0}' declares extensions to load, but the current runtime does not support loading assemblies dynamically (for example when published with native AOT). Set the '{1}' property of each extension to 'false', remove the manifest, or remove '{2}' from the command line.</source>
        <target state="new">The extension manifest '{0}' declares extensions to load, but the current runtime does not support loading assemblies dynamically (for example when published with native AOT). Set the '{1}' property of each extension to 'false', remove the manifest, or remove '{2}' from the command line.</target>
        <note>{0} is the manifest file path. {1} is the name of the JSON property that disables an extension. {2} is the command line option that enables the feature. {Locked="'false'"}</note>
      </trans-unit>
      <trans-unit id="EnvironmentVariableProviderFailedWithError">
        <source>Provider '{0}' (UID: {1}) failed with error: {2}</source>
        <target state="translated">プロバイダー '{0}' (UID: {1}) が次のエラーで失敗しました: {2}</target>
        <note>{0} is the provider display name. {1} is the provider UID. {2} is the error message.</note>
      </trans-unit>
      <trans-unit id="ExceptionDuringCancellationWarningMessage">
        <source>Exception during the cancellation of request id '{0}'</source>
        <target state="translated">要求 ID '{0}' の取り消し中に例外が発生しました</target>
        <note>{0} is the request id.</note>
      </trans-unit>
      <trans-unit id="ExitCode">
        <source>Exit code</source>
        <target state="translated">終了コード</target>
        <note />
      </trans-unit>
      <trans-unit id="ExtensionDoesNotImplementGivenInterfaceErrorMessage">
        <source>Extension of type '{0}' is not implementing the required '{1}' interface</source>
        <target state="translated">型 '{0}' の拡張機能は、必要な '{1}' インターフェイスを実装していません</target>
        <note>{0} is the extension type name. {1} is the required interface type name.</note>
      </trans-unit>
      <trans-unit id="ExtensionWithSameUidAlreadyRegisteredErrorMessage">
        <source>Extensions with the same UID '{0}' have already been registered. Registered extensions are of types: {1}</source>
        <target state="translated">同じ UID '{0}' の拡張機能は既に登録されています。登録済みの拡張機能の種類: {1}</target>
        <note>{0} is the duplicate extension UID. {1} is the list of registered extension type names.</note>
      </trans-unit>
      <trans-unit id="Failed">
        <source>Failed</source>
        <target state="translated">失敗</target>
        <note />
      </trans-unit>
      <trans-unit id="FailedLowercase">
        <source>failed</source>
        <target state="translated">失敗</target>
        <note />
      </trans-unit>
      <trans-unit id="FailedToWriteLogToChannelErrorMessage">
        <source>Failed to write the log to the channel. Missed log content:
{0}</source>
        <target state="translated">ログをチャネルに書き込めませんでした。ログの内容が見つかりません:
{0}</target>
        <note>{0} is the log content that could not be written.</note>
      </trans-unit>
      <trans-unit id="FailedWithErrors">
        <source>failed with {0} error(s)</source>
        <target state="translated">{0} 件のエラーで失敗しました</target>
        <note>{0} is the number of errors.</note>
      </trans-unit>
      <trans-unit id="FailedWithErrorsAndWarnings">
        <source>failed with {0} error(s) and {1} warning(s)</source>
        <target state="translated">{0} 件のエラーと {1} 件の警告で失敗しました</target>
        <note>{0} is the number of errors. {1} is the number of warnings.</note>
      </trans-unit>
      <trans-unit id="FailedWithWarnings">
        <source>failed with {0} warning(s)</source>
        <target state="translated">{0} 件の警告付きで失敗しました</target>
        <note>{0} is the number of warnings.</note>
      </trans-unit>
      <trans-unit id="FinishedTestSession">
        <source>Finished test session.</source>
        <target state="translated">テスト セッションを終了しました。</target>
        <note />
      </trans-unit>
      <trans-unit id="FromFile">
        <source>from</source>
        <target state="translated">参照元:</target>
        <note>from followed by a file name to point to the file from which test is originating</note>
      </trans-unit>
      <trans-unit id="GlobalValidationOfTestHostEnvironmentVariablesFailedErrorMessage">
        <source>The following 'ITestHostEnvironmentVariableProvider' providers rejected the final environment variables setup:</source>
        <target state="translated">次の 'ITestHostEnvironmentVariableProvider' プロバイダーは、最終的な環境変数のセットアップを拒否しました:</target>
        <note>{Locked="ITestHostEnvironmentVariableProvider"}</note>
      </trans-unit>
      <trans-unit id="HelpApplicationUsage">
        <source>Usage {0} [option providers] [extension option providers]</source>
        <target state="translated">使用法 {0} [オプション プロバイダー] [拡張オプション プロバイダー]</target>
        <note>{0} is the application name used in the usage line.</note>
      </trans-unit>
      <trans-unit id="HelpExecuteTestApplication">
        <source>Execute a .NET Test Application.</source>
        <target state="translated">.NET テスト アプリケーションを実行します。</target>
        <note>{Locked=".NET"}</note>
      </trans-unit>
      <trans-unit id="HelpExtensionOptions">
        <source>Extension options:</source>
        <target state="translated">拡張機能オプション:</target>
        <note />
      </trans-unit>
      <trans-unit id="HelpNoExtensionRegistered">
        <source>    No extension registered.</source>
        <target state="translated">    拡張機能が登録されていません。</target>
        <note />
      </trans-unit>
      <trans-unit id="HelpOptions">
        <source>Options:</source>
        <target state="translated">オプション:</target>
        <note />
      </trans-unit>
      <trans-unit id="HelpTestApplicationRunner">
        <source>&lt;test application runner&gt;</source>
        <target state="translated">&lt;test application runner&gt;</target>
        <note>{Locked="&lt;test application runner&gt;"}</note>
      </trans-unit>
      <trans-unit id="InternalLoopAsyncDidNotExitSuccessfullyErrorMessage">
        <source>Method '{0}' did not exit successfully</source>
        <target state="translated">メソッド '{0}' が正常に終了しませんでした</target>
        <note>{0} is the method name.</note>
      </trans-unit>
      <trans-unit id="InvalidCommandLineArguments">
        <source>Invalid command line arguments:</source>
        <target state="translated">コマンド ラインの引数が無効です:</target>
        <note />
      </trans-unit>
      <trans-unit id="JsonCommandLineOptionIsBootstrapOnlyErrorMessage">
        <source>The option '--{0}' is read during platform bootstrap (before the testconfig.json file is loaded) and must therefore be passed on the command line rather than declared under 'commandLineOptions' in testconfig.json.</source>
        <target state="translated">オプション '--{0}' はプラットフォームのブートストラップ中 (testconfig.json ファイルの読み込み前) に読み取られるため、testconfig.json の 'commandLineOptions' ではなく、コマンド ラインで指定する必要があります。</target>
        <note>{0} is the bare bootstrap-only option name without the leading "--" (e.g. config-file, diagnostic, diagnostic-verbosity); the "--" prefix is already in the format string. {Locked="--"}{Locked="commandLineOptions"}{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="JsonCommandLineOptionsEntryMustBeScalarOrArrayErrorMessage">
        <source>The entry '{0}' under section '{1}' in the testconfig.json file ('{2}') must be either a scalar value (string, number, boolean) or an array of scalar values. Nested objects are not supported.</source>
        <target state="translated">testconfig.json ファイル ('{0}') のセクション '{1}' にあるエントリ '{2}' は、スカラー値 (文字列、数値、ブール値) またはスカラー値の配列のいずれかである必要があります。入れ子になったオブジェクトはサポートされていません。</target>
        <note>{0} is the entry name relative to the section (e.g. an option name like 'timeout' or an indexed key like 'timeout:0'). {1} is the section name (commandLineOptions). {2} is the path to the testconfig.json file. {Locked="testconfig.json"}{Locked="commandLineOptions"}{Locked="timeout"}{Locked="timeout:0"}</note>
      </trans-unit>
      <trans-unit id="JsonCommandLineOptionsValidationErrorPrefix">
        <source>In testconfig.json under 'commandLineOptions': {0}</source>
        <target state="translated">In testconfig.json under 'commandLineOptions': {0}</target>
        <note>{0} is the underlying validation error message (unknown option, arity mismatch, invalid arguments...). {Locked="testconfig.json"}{Locked="commandLineOptions"}</note>
      </trans-unit>
      <trans-unit id="JsonConfigurationFileParserDuplicateKeyErrorMessage">
        <source>A duplicate key '{0}' was found</source>
        <target state="translated">重複したキー '{0}' が見つかりました</target>
        <note>{0} is the duplicate JSON key.</note>
      </trans-unit>
      <trans-unit id="JsonConfigurationFileParserTopLevelElementIsNotAnObjectErrorMessage">
        <source>Top-level JSON element must be an object. Instead, '{0}' was found</source>
        <target state="translated">最上位の JSON 要素はオブジェクトである必要があります。代わりに、'{0}' が見つかりました</target>
        <note>{0} is the JSON value kind that was found.</note>
      </trans-unit>
      <trans-unit id="JsonConfigurationFileParserUnsupportedTokenErrorMessage">
        <source>Unsupported JSON token '{0}' was found</source>
        <target state="translated">サポートされていない JSON トークン '{0}' が見つかりました</target>
        <note>{0} is the unsupported JSON token type.</note>
      </trans-unit>
      <trans-unit id="JsonConfigurationSectionEntryMustBeScalarErrorMessage">
        <source>The entry '{0}' under section '{1}' in the testconfig.json file ('{2}') must be a scalar string value. Nested objects and arrays are not supported.</source>
        <target state="translated">testconfig.json ファイル ('{0}') の '{1}' セクション内のエントリ '{2}' は、スカラー文字列値である必要があります。入れ子になったオブジェクトと配列はサポートされていません。</target>
        <note>{0} is the full dotted/colon-separated key. {1} is the section name. {2} is the path to the testconfig.json file. {Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="JsonConfigurationSectionMustBeAnObjectErrorMessage">
        <source>The '{0}' section in the testconfig.json file ('{1}') must be a JSON object.</source>
        <target state="translated">testconfig.json ファイル ('{0}') の '{1}' セクションは JSON オブジェクトである必要があります。</target>
        <note>{0} is the section name (e.g. environmentVariables). {1} is the path to the testconfig.json file. {Locked="testconfig.json"}{Locked="environmentVariables"}</note>
      </trans-unit>
      <trans-unit id="JsonRpcTcpServerDescription">
        <source>JsonRpc server implementation based on the test platform protocol specification.</source>
        <target state="translated">テスト プラットフォーム プロトコル仕様に基づく JsonRpc サーバー実装。</target>
        <note>{Locked="JsonRpc"}</note>
      </trans-unit>
      <trans-unit id="JsonRpcTcpServerToSingleClientDescription">
        <source>JsonRpc server to client handshake, implementation based on the test platform protocol specification.</source>
        <target state="translated">テスト プラットフォーム プロトコル仕様に基づく JsonRpc サーバーからクライアント ハンドシェイクへの実装。</target>
        <note>{Locked="JsonRpc"}</note>
      </trans-unit>
      <trans-unit id="LoggerFactoryNotReady">
        <source>The ILoggerFactory has not been built yet.</source>
        <target state="translated">ILoggerFactory はまだ構築されていません。</target>
        <note>{Locked="ILoggerFactory"}</note>
      </trans-unit>
      <trans-unit id="MaxFailedTestsMustBePositive">
        <source>The option '--maximum-failed-tests' must be a positive integer. The value '{0}' is not valid.</source>
        <target state="translated">オプション '--maximum-failed-tests' は正の整数である必要があります。'{0}' 値が無効です。</target>
        <note>{0} is the invalid option value. {Locked="--maximum-failed-tests"}</note>
      </trans-unit>
      <trans-unit id="MessageBusNotReady">
        <source>The message bus has not been built yet or is no more usable at this stage.</source>
        <target state="translated">メッセージ バスはまだ構築されていないか、この段階ではこれ以上使用できません。</target>
        <note />
      </trans-unit>
      <trans-unit id="MissingClientPortFoJsonRpc">
        <source>Expected --client-port when jsonRpc protocol is used.</source>
        <target state="translated">jsonRpc プロトコルを使用する場合、--client-port が必要です。</target>
        <note>{Locked="--client-port"}{Locked="jsonRpc"}</note>
      </trans-unit>
      <trans-unit id="ActiveTestsRunning_MoreTestsCount">
        <source>and {0} more</source>
        <target state="translated">その他 {0} 件</target>
        <note>{0} is the number of additional active tests.</note>
      </trans-unit>
      <trans-unit id="ActiveTestsRunning_FullTestsCount">
        <source>{0} tests running</source>
        <target state="translated">{0} テストを実行しています</target>
        <note>{0} is the number of currently running tests.</note>
      </trans-unit>
      <trans-unit id="NamedPipeDirectoryNotWritableErrorMessage">
        <source>The named pipe directory '{0}' does not exist or is not writable: {1}. Set the '{2}' environment variable to an existing writable directory, or unset it to fall back to the default temporary directory.</source>
        <target state="translated">名前付きパイプ ディレクトリ '{0}' が存在しないか、書き込み可能ではありません: {1}。'{2}' 環境変数を既存の書き込み可能なディレクトリに設定するか、設定を解除して既定の一時ディレクトリにフォールバックします。</target>
        <note>{0} is the directory path, {1} is the underlying error message, {2} is the environment variable name. Do not translate the environment variable name.</note>
      </trans-unit>
      <trans-unit id="NamedPipePathTooLongErrorMessage">
        <source>The named pipe path '{0}' is {1} bytes long, which exceeds the maximum of {2} bytes allowed for a Unix domain socket. Use a shorter directory by setting the '{3}' environment variable, or by setting 'TMPDIR' when '{3}' is not set.</source>
        <target state="translated">名前付きパイプ パス '{0}' の長さは {1} バイトで、UNIX ドメイン ソケットで許可されている最大 {2} バイトを超えています。'{3}' 環境変数を設定してより短いディレクトリを使用するか、'{3}' が設定されていない場合は 'TMPDIR' を設定します。</target>
        <note>{0} is the full pipe path, {1} is its length in bytes, {2} is the maximum allowed length in bytes, {3} is the environment variable name. Do not translate 'TMPDIR' or the environment variable name.</note>
      </trans-unit>
      <trans-unit id="NotAvailable">
        <source>Not available</source>
        <target state="translated">利用できません</target>
        <note />
      </trans-unit>
      <trans-unit id="NotFound">
        <source>Not found</source>
        <target state="translated">見つかりません</target>
        <note />
      </trans-unit>
      <trans-unit id="OnlyOneFilterSupported">
        <source>Passing both '--treenode-filter' and '--filter-uid' is unsupported.</source>
        <target state="translated">'--treenode-filter' と '--filter-uid' の両方を渡すことはサポートされていません。</target>
        <note>{Locked="--treenode-filter"}{Locked="--filter-uid"}</note>
      </trans-unit>
      <trans-unit id="OnlyOneTestHostLauncherSupported">
        <source>Only one test host launcher can be registered.</source>
        <target state="translated">登録できるテスト ホスト起動ツールは 1 つだけです。</target>
        <note />
      </trans-unit>
      <trans-unit id="Passed">
        <source>Passed</source>
        <target state="translated">成功</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineClientHostOptionDescription">
        <source>Specify the hostname of the client.</source>
        <target state="translated">クライアントのホスト名を指定します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineClientPortOptionDescription">
        <source>Specify the port of the client.</source>
        <target state="translated">クライアントのポートを指定します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineConfigFileOptionDescription">
        <source>Specifies a testconfig.json file.</source>
        <target state="translated">testconfig.json ファイルを指定します。</target>
        <note>{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDebugAttachOptionDescription">
        <source>Allows to pause execution in order to attach to the process for debug purposes.</source>
        <target state="translated">デバッグ目的でプロセスにアタッチするために、実行を一時停止することができます。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticFileLoggerSynchronousWriteOptionDescription">
        <source>Force the built-in file logger to write the log synchronously.
Useful for scenario where you don't want to lose any log (i.e. in case of crash).
Note that this is slowing down the test execution.</source>
        <target state="translated">組み込みのファイル ロガーでログを同期的に書き込むことを強制します。
ログを失わないシナリオ (クラッシュした場合など) に役立ちます。
これにより、テストの実行速度が低下していることに注意してください。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticOptionDescription">
        <source>Enable the diagnostic logging. The default log level is 'Trace'.
The file will be written in the output directory with the name log_[yyMMddHHmmssfff].diag</source>
        <target state="translated">診断ログを有効にします。既定のログ レベルは 'Trace' です。
ファイルは、出力ディレクトリに log_[yyMMddHHmmssfff].diag という名前で書き込まれます。</target>
        <note>{Locked="Trace"}{Locked="log_[yyMMddHHmmssfff].diag"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticOptionExpectsSingleArgumentErrorMessage">
        <source>'--diagnostic-verbosity' expects a single level argument ('Trace', 'Debug', 'Information', 'Warning', 'Error', or 'Critical')</source>
        <target state="translated">'--diagnostic-verbosity' には単一レベルの引数 ('Trace'、'Debug'、'Information'、'Warning'、'Error'、'Critical') が必要です</target>
        <note>{Locked="--diagnostic-verbosity"}{Locked="Trace"}{Locked="Debug"}{Locked="Information"}{Locked="Warning"}{Locked="Error"}{Locked="Critical"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticOptionIsMissing">
        <source>'--{0}' requires '--diagnostic' to be provided</source>
        <target state="translated">'--{0}' には '--diagnostic' を指定する必要があります</target>
        <note>{0} is the option name without the leading dashes. {Locked="--diagnostic"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticOutputDirectoryOptionDescription">
        <source>Output directory of the diagnostic logging.
If not specified the file will be generated inside the default 'TestResults' directory.</source>
        <target state="translated">診断ログの出力ディレクトリ。
指定しない場合、ファイルは既定の 'TestResults' ディレクトリ内に生成されます。</target>
        <note>{Locked="TestResults"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticOutputFilePrefixOptionDescription">
        <source>Prefix for the log file name that will replace '[log]_.'</source>
        <target state="translated">'[log]_.' を置き換えるログ ファイル名のプレフィックス。</target>
        <note>{Locked="[log]_."}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiagnosticVerbosityOptionDescription">
        <source>Define the level of the verbosity for the --diagnostic.
The available values are 'Trace', 'Debug', 'Information', 'Warning', 'Error', and 'Critical'.</source>
        <target state="translated">--diagnostic の詳細レベルを定義します。
使用可能な値は、'Trace'、'Debug'、'Information'、'Warning'、'Error'、'Critical' です。</target>
        <note>{Locked="--diagnostic"}{Locked="Trace"}{Locked="Debug"}{Locked="Information"}{Locked="Warning"}{Locked="Error"}{Locked="Critical"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiscoverTestsInvalidArgument">
        <source>'--list-tests' received unexpected value '{0}'. Supported values are: {1}.</source>
        <target state="translated">'--list-tests' が予期しない値 '{0}' を受け取りました。サポートされている値: {1}。</target>
        <note>{0} is the unexpected option value. {1} is the comma-separated list of supported values. {Locked="--list-tests"}{Locked="text"}{Locked="json"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDiscoverTestsOptionDescription">
        <source>List available tests.
Optionally accepts 'text' (the default human-readable output) or 'json' to print the discovered tests as a JSON document on standard output.</source>
        <target state="translated">使用可能なテストを一覧します。
必要に応じて、'text' (既定の人間が判読できる出力) または 'json' を指定すると、検出されたテストを標準出力に JSON ドキュメントとして印刷します。</target>
        <note>{Locked="text"}{Locked="json"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestCliRequiresPipe">
        <source>'--server {0}' requires '--{1}' to be specified.</source>
        <target state="translated">'--server {0}' には '--{1}' を指定する必要があります。</target>
        <note>{0} is the server protocol value. {1} is the required option name without the leading dashes. {Locked="--server"}{Locked="dotnettestcli"}{Locked="dotnet-test-pipe"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestCliRequiresTransport">
        <source>'--server dotnettestcli' requires either '--dotnet-test-pipe' or '--dotnet-test-transport http'.</source>
        <target state="translated">'--server dotnettestcli' には '--dotnet-test-pipe' または '--dotnet-test-transport http' が必要です。</target>
        <note>{Locked="--server dotnettestcli"}{Locked="--dotnet-test-pipe"}{Locked="--dotnet-test-transport http"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpEndpointInvalid">
        <source>'--dotnet-test-http-endpoint' requires an absolute HTTPS URL, or an HTTP loopback URL, without user information, query, or fragment.</source>
        <target state="translated">'--dotnet-test-http-endpoint' には、ユーザー情報、クエリ、またはフラグメントを含まない絶対 HTTPS URL、または HTTP ループバック URL が必要です。</target>
        <note>{Locked="--dotnet-test-http-endpoint"}{Locked="HTTP"}{Locked="HTTPS"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpEndpointOptionDescription">
        <source>Specifies the authenticated HTTP endpoint for the dotnet test protocol.</source>
        <target state="translated">dotnet test プロトコルの認証済み HTTP エンドポイントを指定します。</target>
        <note>{Locked="HTTP"}{Locked="dotnet test"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpOptionsRequireTransport">
        <source>The dotnet test HTTP endpoint and token options require '--dotnet-test-transport http'.</source>
        <target state="translated">dotnet test HTTP エンドポイントおよびトークン オプションには '--dotnet-test-transport http' が必要です。</target>
        <note>{Locked="dotnet test"}{Locked="HTTP"}{Locked="--dotnet-test-transport http"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpRequiresEndpointAndToken">
        <source>'--dotnet-test-transport http' requires both '--dotnet-test-http-endpoint' and '--dotnet-test-http-token'.</source>
        <target state="translated">'--dotnet-test-transport http' には '--dotnet-test-http-endpoint' と '--dotnet-test-http-token' の両方が必要です。</target>
        <note>{Locked="--dotnet-test-transport http"}{Locked="--dotnet-test-http-endpoint"}{Locked="--dotnet-test-http-token"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpTokenInvalid">
        <source>'--dotnet-test-http-token' requires a non-empty valid bearer token without whitespace or control characters.</source>
        <target state="translated">'--dotnet-test-http-token' には、空ではなく、空白文字や制御文字を含まない有効なベアラー トークンを指定する必要があります。</target>
        <note>{Locked="--dotnet-test-http-token"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestHttpTokenOptionDescription">
        <source>Specifies the per-run HTTP bearer token for the dotnet test protocol.</source>
        <target state="translated">dotnet test プロトコルで実行ごとに使用する HTTP ベアラー トークンを指定します。</target>
        <note>{Locked="HTTP"}{Locked="dotnet test"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestPipe">
        <source>dotnet test pipe.</source>
        <target state="translated">dotnet test パイプ。</target>
        <note>{Locked="dotnet test"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestTransportConflict">
        <source>The dotnet test named-pipe and HTTP transports cannot be selected together.</source>
        <target state="translated">dotnet test の名前付きパイプと HTTP の両方のトランスポートを同時に選択することはできません。</target>
        <note>{Locked="dotnet test"}{Locked="HTTP"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestTransportInvalid">
        <source>'--dotnet-test-transport' received unexpected value '{0}'. Supported values are: {1}.</source>
        <target state="translated">'--dotnet-test-transport' に予期しない値 '{0}' が指定されました。サポートされている値: {1}。</target>
        <note>{0} is the unexpected transport value. {1} is the comma-separated list of supported transport values. {Locked="--dotnet-test-transport"}{Locked="pipe"}{Locked="http"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestTransportOptionDescription">
        <source>Selects the pre-launch transport for the dotnet test protocol.</source>
        <target state="translated">dotnet test プロトコルの起動前トランスポートを選択します。</target>
        <note>{Locked="dotnet test"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineEnableDynamicExtensionsOptionDescription">
        <source>Enable loading test platform extensions declared by '*.testingplatformextensions.json' manifests found next to the test application. Disabled by default.</source>
        <target state="new">Enable loading test platform extensions declared by '*.testingplatformextensions.json' manifests found next to the test application. Disabled by default.</target>
        <note>{Locked="'*.testingplatformextensions.json'"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineExitOnProcessExitInvalidDependentProcess">
        <source>Invalid PID '{0}'
{1}</source>
        <target state="translated">PID '{0}'
 が無効です
{1}</target>
        <note>{0} is the invalid process ID. {1} is the exception message.</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineExitOnProcessExitNotSupportedInBrowser">
        <source>The '--exit-on-process-exit' option is not supported in browser environments.</source>
        <target state="translated">'--exit-on-process-exit' オプションは、ブラウザー環境ではサポートされていません。</target>
        <note>{Locked="--exit-on-process-exit"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineExitOnProcessExitOptionDescription">
        <source>Exit the test process if dependent process exits. PID must be provided.</source>
        <target state="translated">依存プロセスが終了した場合は、テスト プロセスを終了します。PID を指定する必要があります。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineExitOnProcessExitSingleArgument">
        <source>'--{0}' expects a single int PID argument</source>
        <target state="translated">'--{0}' には 1 つの int PID 引数が必要です</target>
        <note>{0} is the option name without the leading dashes.</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineFilterUidOptionDescription">
        <source>Provides a list of test node UIDs to filter by.</source>
        <target state="translated">フィルター対象のテスト ノード UID のリストを提供します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineHelpOptionDescription">
        <source>Show the command line help.</source>
        <target state="translated">コマンド ラインヘルプを表示します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineIgnoreExitCodeOptionDescription">
        <source>Do not report a non-successful exit value for the specified exit codes.
For example, '--ignore-exit-code 8;9' ignores exit codes 8 and 9 and returns 0 in those cases.
For more information about exit codes, see https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-troubleshooting#exit-codes.</source>
        <target state="new">Do not report a non-successful exit value for the specified exit codes.
For example, '--ignore-exit-code 8;9' ignores exit codes 8 and 9 and returns 0 in those cases.
For more information about exit codes, see https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-troubleshooting#exit-codes.</target>
        <note>{Locked="'--ignore-exit-code 8;9'"} {Locked="https://learn.microsoft.com/dotnet/core/testing/microsoft-testing-platform-troubleshooting#exit-codes"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineInfoOptionDescription">
        <source>Display .NET test application information.</source>
        <target state="translated">.NET テスト アプリケーション情報を表示します。</target>
        <note>{Locked=".NET"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineMaxFailedTestsOptionDescription">
        <source>Specifies a maximum number of test failures that, when exceeded, will abort the test run.</source>
        <target state="translated">テストの実行を中止するテスト エラーの最大数を指定します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineMinimumExpectedTestsIncompatibleDiscoverTests">
        <source>'--list-tests' and '--minimum-expected-tests' are incompatible options</source>
        <target state="translated">'--list-tests' と '--minimum-expected-tests' は互換性のないオプションです</target>
        <note>{Locked="--list-tests"}{Locked="--minimum-expected-tests"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineMinimumExpectedTestsOptionDescription">
        <source>Specifies the minimum number of tests that are expected to run.</source>
        <target state="translated">実行する必要があるテストの最小数を指定します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineMinimumExpectedTestsOptionSingleArgument">
        <source>'--minimum-expected-tests' expects a single non-zero positive integer value
(e.g. '--minimum-expected-tests 10')</source>
        <target state="translated">'--minimum-expected-tests' には、0 以外の正の整数値が 1 つ必要です
(例: '--minimum-expected-tests 10')</target>
        <note>{Locked="--minimum-expected-tests"}{Locked="--minimum-expected-tests 10"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineNoBannerOptionDescription">
        <source>Do not display the startup banner, the copyright message or the telemetry banner.</source>
        <target state="translated">スタートアップ バナー、著作権メッセージ、テレメトリ バナーは表示しないでください。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLinePipeTransportNotSupportedOnBrowser">
        <source>The dotnet test named-pipe transport is not supported on browser-wasm. Use '--dotnet-test-transport http'.</source>
        <target state="translated">dotnet test の名前付きパイプ トランスポートは browser-wasm ではサポートされていません。'--dotnet-test-transport http' を使用してください。</target>
        <note>{Locked="dotnet test"}{Locked="browser-wasm"}{Locked="--dotnet-test-transport http"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLinePipeTransportNotSupportedOnWasi">
        <source>The dotnet test named-pipe transport is not supported on wasi-wasm. Use '--dotnet-test-transport http'.</source>
        <target state="translated">dotnet test 名前付きパイプ トランスポートは wasi-wasm ではサポートされていません。'--dotnet-test-transport http' を使用してください。</target>
        <note>{Locked="dotnet test"}{Locked="wasi-wasm"}{Locked="--dotnet-test-transport http"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLinePortOptionDescription">
        <source>Specify the port of the server.</source>
        <target state="translated">サーバーのポートを指定します。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLinePortOptionSingleArgument">
        <source>'--{0}' expects a single valid port as argument</source>
        <target state="translated">'--{0}' には、引数として有効なポートが 1 つ必要です</target>
        <note>{0} is the option name without the leading dashes.</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineProviderDescription">
        <source>Microsoft Testing Platform command line provider</source>
        <target state="translated">Microsoft テスト プラットフォーム コマンド ライン プロバイダー</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineProviderDisplayName">
        <source>Platform command line provider</source>
        <target state="translated">プラットフォーム コマンド ライン プロバイダー</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineResultDirectoryOptionDescription">
        <source>The directory where the test results are going to be placed.
If the specified directory doesn't exist, it's created.
The default is TestResults in the directory that contains the test application.</source>
        <target state="translated">テスト結果を配置するディレクトリ。
指定したディレクトリが存在しない場合は、作成されます。
既定値は、テスト アプリケーションを含むディレクトリ内の TestResults です。</target>
        <note>{Locked="TestResults"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineServerInvalidArgument">
        <source>'--server' received unexpected value '{0}'. Supported values are: {1}.</source>
        <target state="translated">'--server' は予期しない値 '{0}'を受け取りました。サポートされている値: {1}。</target>
        <note>{0} is the unexpected protocol value. {1} is the comma-separated list of supported protocol values. {Locked="--server"}{Locked="jsonrpc"}{Locked="dotnettestcli"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineServerOptionDescription">
        <source>Enable the server mode.</source>
        <target state="translated">サーバー モードを有効にします。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineSkipBuildersNumberCheckOptionDescription">
        <source>For testing purposes</source>
        <target state="translated">テスト目的</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineTestHostControllerPIDOptionDescription">
        <source>Eventual parent test host controller PID.</source>
        <target state="translated">最終的な親テスト ホスト コントローラー PID。</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineTimeoutArgumentErrorMessage">
        <source>'timeout' option should have one argument as a time value with an explicit unit suffix and a positive numeric value within the supported range (up to ~49.7 days). Accepted suffixes are 'ms'/'mil(s)'/'millisecond(s)', 's'/'sec(s)'/'second(s)', 'm'/'min(s)'/'minute(s)', 'h'/'hour(s)', and 'd'/'day(s)', e.g. '500ms', '5400s', '90m', '1.5h', '1d'.</source>
        <target state="translated">'timeout' オプションには、引数として明示的な単位サフィックスと、サポートされている範囲内 (最大約 49.7 日) の正の数値を持つ時間値を 1 つ指定する必要があります。使用可能なサフィックスは、'ms'/'mil(s)'/'millisecond(s)'、's'/'sec(s)'/'second(s)'、'm'/'min(s)'/'minute(s)'、'h'/'hour(s)'、'd'/'day(s)' です (例: '500ms'、'5400s'、'90m'、'1.5h'、'1d')。</target>
        <note>{Locked="'timeout'"}{Locked="'ms'"}{Locked="'mil(s)'"}{Locked="'millisecond(s)'"}{Locked="'s'"}{Locked="'sec(s)'"}{Locked="'second(s)'"}{Locked="'m'"}{Locked="'min(s)'"}{Locked="'minute(s)'"}{Locked="'h'"}{Locked="'hour(s)'"}{Locked="'d'"}{Locked="'day(s)'"}{Locked="'500ms'"}{Locked="'5400s'"}{Locked="'90m'"}{Locked="'1.5h'"}{Locked="'1d'"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineTimeoutOptionDescription">
        <source>A global test execution timeout.
Takes one argument as a time value with an explicit unit suffix. Accepted suffixes are 'ms'/'mil(s)'/'millisecond(s)', 's'/'sec(s)'/'second(s)', 'm'/'min(s)'/'minute(s)', 'h'/'hour(s)', and 'd'/'day(s)', e.g. '500ms', '5400s', '90m', '1.5h', '1d'.</source>
        <target state="translated">グローバル テスト実行のタイムアウト。
明示的な単位サフィックスを持つ時間値を 1 つ、引数として指定します。使用可能なサフィックスは、'ms'/'mil(s)'/'millisecond(s)'、's'/'sec(s)'/'second(s)'、'm'/'min(s)'/'minute(s)'、'h'/'hour(s)'、'd'/'day(s)' です (例: '500ms'、'5400s'、'90m'、'1.5h'、'1d')。</target>
        <note>{Locked="'ms'"}{Locked="'mil(s)'"}{Locked="'millisecond(s)'"}{Locked="'s'"}{Locked="'sec(s)'"}{Locked="'second(s)'"}{Locked="'m'"}{Locked="'min(s)'"}{Locked="'minute(s)'"}{Locked="'h'"}{Locked="'hour(s)'"}{Locked="'d'"}{Locked="'day(s)'"}{Locked="'500ms'"}{Locked="'5400s'"}{Locked="'90m'"}{Locked="'1.5h'"}{Locked="'1d'"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineZeroTestsPolicyInvalidArgument">
        <source>Invalid value '{0}' for '--zero-tests-policy'. Valid values are {1}.</source>
        <target state="translated">'--zero-tests-policy' の値 '{0}' は無効です。有効な値は {1} です。</target>
        <note>{Locked="--zero-tests-policy"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineZeroTestsPolicyOptionDescription">
        <source>Specifies how a run that executed no tests is treated.
Valid values are 'allow-skipped' (the default) which counts skipped tests as run, so only a run where no test was found at all fails with exit code 8, and 'strict' which treats skipped tests as not run, so a run where every test was skipped (or no test was found) fails with exit code 8.</source>
        <target state="translated">テストを実行しなかった実行の処理方法を指定します。
有効な値は 'allow-skipped' (既定) と 'strict' です。'allow-skipped' はスキップされたテストを実行済みとして扱うため、テストが1つも見つからなかった実行のみが終了コード 8 で失敗します。'strict' はスキップされたテストを未実行として扱うため、すべてのテストがスキップされた場合、またはテストが 1 つも見つからなかった場合に終了コード 8 で失敗します。</target>
        <note>{Locked="strict"}{Locked="allow-skipped"}</note>
      </trans-unit>
      <trans-unit id="PressCtrlCAgainToForceExit">
        <source>Press Ctrl+C again to force exit.</source>
        <target state="translated">強制終了するには、Ctrl+C キーをもう一度押してください。</target>
        <note>{Locked="Ctrl+C"}</note>
      </trans-unit>
      <trans-unit id="ProcessHasNotYetExitedErrorMessage">
        <source>Process should have exited before we can determine this value</source>
        <target state="translated">この値を決定する前にプロセスを終了する必要があります</target>
        <note />
      </trans-unit>
      <trans-unit id="ReachedMaxFailedTestsMessage">
        <source>Test session is aborting due to reaching failures ('{0}') specified by the '--maximum-failed-tests' option.</source>
        <target state="translated">'--maximum-failed-tests' オプションで指定されたエラー ('{0}') に達したため、テスト セッションを中止しています。</target>
        <note>{0} is the number of max failed tests. {Locked="--maximum-failed-tests"}</note>
      </trans-unit>
      <trans-unit id="RetryFailedAfterTriesErrorMessage">
        <source>Retry failed after {0} times</source>
        <target state="translated">再試行が {0} 回後に失敗しました</target>
        <note>{0} is the retry count.</note>
      </trans-unit>
      <trans-unit id="RunningTestsFrom">
        <source>Running tests from</source>
        <target state="translated">次からテストを実行しています:</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerLogMessageDescription">
        <source>This data represents a server log message</source>
        <target state="translated">このデータはサーバー ログ メッセージを表します</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerLogMessageDisplayName">
        <source>Server log message</source>
        <target state="translated">サーバー ログ メッセージ</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestExecutionFilterFactoryDescription">
        <source>Creates the right test execution filter for server mode</source>
        <target state="translated">サーバー モードに適したテスト実行フィルターを作成します</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestExecutionFilterFactoryDisplayName">
        <source>Server test execution filter factory</source>
        <target state="translated">サーバー テスト実行フィルター ファクトリ</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestHostDescription">
        <source>The 'ITestHost' implementation used when running server mode.</source>
        <target state="translated">サーバー モードの実行時に使用される 'ITestHost' 実装。</target>
        <note>{Locked="ITestHost"}</note>
      </trans-unit>
      <trans-unit id="ServerTestHostDisplayName">
        <source>Server mode test host</source>
        <target state="translated">サーバー モード テスト ホスト</target>
        <note />
      </trans-unit>
      <trans-unit id="ServiceProviderCannotFindServiceErrorMessage">
        <source>Cannot find service of type '{0}'</source>
        <target state="translated">'{0}' 型のサービスが見つかりません</target>
        <note>{0} is the requested service type name.</note>
      </trans-unit>
      <trans-unit id="ServiceProviderServiceAlreadyRegistered">
        <source>Instance of type '{0}' is already registered</source>
        <target state="translated">'{0}' 型のインスタンスは既に登録されています</target>
        <note>{0} is the already registered service type name.</note>
      </trans-unit>
      <trans-unit id="ServiceProviderShouldNotRegisterTestFramework">
        <source>Instances of type 'ITestFramework' should not be registered through the service provider but through 'ITestApplicationBuilder.RegisterTestFramework'</source>
        <target state="translated">'ITestFramework' 型のインスタンスは、サービス プロバイダーを介して登録することはできません。'ITestApplicationBuilder.RegisterTestFramework' を介して登録する必要があります</target>
        <note>{Locked="ITestFramework"}{Locked="ITestApplicationBuilder.RegisterTestFramework"}</note>
      </trans-unit>
      <trans-unit id="ShutdownProgressStillWaitingPrefix">
        <source>Still waiting for: </source>
        <target state="translated">まだ次の完了を待機中:</target>
        <note>Prefix for the message that lists extensions that have not yet completed their shutdown work. Each entry is formatted as "{DisplayName} ({Phase}, {Seconds}s)" and entries are separated by "; ". {Locked="{DisplayName} ({Phase}, {Seconds}s)"}{Locked="; "}</note>
      </trans-unit>
      <trans-unit id="Skipped">
        <source>Skipped</source>
        <target state="translated">スキップ</target>
        <note />
      </trans-unit>
      <trans-unit id="SkippedLowercase">
        <source>skipped</source>
        <target state="translated">スキップされました</target>
        <note />
      </trans-unit>
      <trans-unit id="StackTrace">
        <source>Stack Trace</source>
        <target state="translated">スタック トレース</target>
        <note />
      </trans-unit>
      <trans-unit id="StartingTestSession">
        <source>Starting test session.</source>
        <target state="translated">テスト セッションを開始しています。</target>
        <note />
      </trans-unit>
      <trans-unit id="StartingTestSessionWithLogFilePath">
        <source>Starting test session. The log file path is '{0}'.</source>
        <target state="translated">テスト セッションを開始しています。ログ ファイルのパスが '{0}' です。</target>
        <note>{0} is the log file path.</note>
      </trans-unit>
      <trans-unit id="SucceededLowercase">
        <source>succeeded</source>
        <target state="translated">成功</target>
        <note />
      </trans-unit>
      <trans-unit id="SyncFlushNotSupportedInBrowserErrorMessage">
        <source>Synchronous flush is not supported in browser environments.</source>
        <target state="translated">同期フラッシュは、ブラウザー環境ではサポートされていません。</target>
        <note />
      </trans-unit>
      <trans-unit id="TEstExecutionFilterFactoryFactoryAlreadySetErrorMessage">
        <source>An 'ITestExecutionFilterFactory' factory is already set</source>
        <target state="translated">'ITestExecutionFilterFactory' ファクトリは既に設定されています</target>
        <note>{Locked="ITestExecutionFilterFactory"}</note>
      </trans-unit>
      <trans-unit id="TelemetryNotice">
        <source>Telemetry
---------
Microsoft Testing Platform collects usage data in order to help us improve your experience. The data is collected by Microsoft and are not shared with anyone.
You can opt-out of telemetry by setting the TESTINGPLATFORM_TELEMETRY_OPTOUT or DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about Microsoft Testing Platform telemetry: https://aka.ms/testingplatform/telemetry</source>
        <target state="translated">テレメトリ 
---------
Microsoft Testing Platform は、お客様のエクスペリエンスの向上に役立てるために使用状況データを収集します。データは Microsoft によって収集され、誰とも共有されません。
テレメトリをオプトアウトするには、お気に入りのシェルを使用して、TESTINGPLATFORM_TELEMETRY_OPTOUT または DOTNET_CLI_TELEMETRY_OPTOUT 環境変数を '1' または 'true' に設定します。

Microsoft Testing Platform テレメトリの詳細: https://aka.ms/testingplatform/telemetry</target>
        <note>{Locked="TESTINGPLATFORM_TELEMETRY_OPTOUT"}{Locked="DOTNET_CLI_TELEMETRY_OPTOUT"}{Locked="1"}{Locked="true"}{Locked="https://aka.ms/testingplatform/telemetry"}</note>
      </trans-unit>
      <trans-unit id="TelemetryProviderAlreadySetErrorMessage">
        <source>Telemetry provider is already set</source>
        <target state="translated">テレメトリ プロバイダーは既に設定されています</target>
        <note />
      </trans-unit>
      <trans-unit id="TerminalNoProgressDeprecatedWarning">
        <source>warning: --no-progress is deprecated; use --progress off instead.</source>
        <target state="translated">警告: --no-progress は非推奨です。代わりに --progress off を使用してください。</target>
        <note>{Locked="--no-progress"}{Locked="--progress off"}</note>
      </trans-unit>
      <trans-unit id="TestAdapterInvokerFactoryAlreadySetErrorMessage">
        <source>An 'ITestFrameworkInvoker' factory is already set</source>
        <target state="translated">'ITestFrameworkInvoker' ファクトリは既に設定されています</target>
        <note>{Locked="ITestFrameworkInvoker"}</note>
      </trans-unit>
      <trans-unit id="TestApplicationBuilderApplicationAlreadyRegistered">
        <source>The application has already been built</source>
        <target state="translated">アプリケーションは既にビルドされています</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationBuilderFrameworkAdapterFactoryAlreadyRegisteredErrorMessage">
        <source>The test framework adapter factory has already been registered</source>
        <target state="translated">テスト フレームワーク アダプター ファクトリは既に登録されています</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationBuilderTestFrameworkCapabilitiesAlreadyRegistered">
        <source>The test framework capabilities factory has already been registered</source>
        <target state="translated">テスト フレームワーク機能ファクトリは既に登録されています</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationBuilderTestFrameworkNotRegistered">
        <source>The test framework adapter has not been registered. Use 'ITestApplicationBuilder.RegisterTestFramework' to register it</source>
        <target state="translated">テスト フレームワーク アダプターが登録されていません。'ITestApplicationBuilder.RegisterTestFramework' を使用して登録してください</target>
        <note>{Locked="ITestApplicationBuilder.RegisterTestFramework"}</note>
      </trans-unit>
      <trans-unit id="TestApplicationResultDescription">
        <source>Determine the result of the test application execution</source>
        <target state="translated">テスト アプリケーションの実行結果を判断します</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationResultDisplayName">
        <source>Test application result</source>
        <target state="translated">テスト アプリケーションの結果</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationVSTestModeTooManyBuilders">
        <source>VSTest mode only supports a single TestApplicationBuilder per process</source>
        <target state="translated">VSTest モードは、プロセスごとに 1 つの TestApplicationBuilder のみをサポートします</target>
        <note>{Locked="VSTest"}{Locked="TestApplicationBuilder"}</note>
      </trans-unit>
      <trans-unit id="TestConfigurationEnvironmentVariableInvalidNameErrorMessage">
        <source>Environment variable name '{0}' declared in the 'environmentVariables' section of the testconfig.json file is invalid. Names must not contain '=' or null characters.</source>
        <target state="translated">testconfig.json ファイルの 'environmentVariables' セクションで宣言された環境変数名 '{0}' は無効です。名前に '=' または null 文字を含めることはできません。</target>
        <note>{0} is the invalid environment variable name. {Locked="environmentVariables"}{Locked="testconfig.json"}{Locked="="}</note>
      </trans-unit>
      <trans-unit id="TestConfigurationEnvironmentVariableNameCannotBeEmptyErrorMessage">
        <source>Environment variable names declared in the 'environmentVariables' section of the testconfig.json file must not be empty.</source>
        <target state="translated">testconfig.json ファイルの 'environmentVariables' セクションで宣言された環境変数名を空にすることはできません。</target>
        <note>{Locked="environmentVariables"}{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="TestConfigurationEnvironmentVariableProviderDescription">
        <source>Applies environment variables declared in the 'environmentVariables' section of the testconfig.json file to the test host child process.</source>
        <target state="translated">testconfig.json ファイルの 'environmentVariables' セクションで宣言された環境変数をテスト ホストの子プロセスに適用します。</target>
        <note>{Locked="environmentVariables"}{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="TestConfigurationEnvironmentVariableProviderDisplayName">
        <source>testconfig.json environment variables provider</source>
        <target state="translated">testconfig.json の環境変数プロバイダー</target>
        <note>{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="TestDiscoverySummary">
        <source>Test discovery summary: found {0} test(s) in {1} assemblies.</source>
        <target state="translated">テスト検出の要約: {1} 個のアセンブリで {0} 個のテストが見つかりました。</target>
        <note>{0} is the number of discovered tests. {1} is the count of assemblies.</note>
      </trans-unit>
      <trans-unit id="TestExecutionFilterProviderNotSupportedForServer">
        <source>Test execution filter provider '{0}' returned filter type '{1}' for a JSON-RPC server request. Provider constraints are not applied to server requests; return null when TestExecutionFilterContext.Origin is Server.</source>
        <target state="translated">テスト実行フィルター プロバイダー '{0}' は、JSON-RPC サーバー要求に対してフィルターの種類 '{1}' を返しました。プロバイダーの制約はサーバー要求には適用されません。TestExecutionFilterContext.Origin が Server の場合は null を返します。</target>
        <note>{0} is the provider UID. {1} is the filter type. {Locked="JSON-RPC"}{Locked="null"}{Locked="TestExecutionFilterContext.Origin"}{Locked="Server"}</note>
      </trans-unit>
      <trans-unit id="TestFrameworkProxyApiShouldNotBeCalled">
        <source>Method '{0}' should not have been called on this proxy object</source>
        <target state="translated">このプロキシ オブジェクトでメソッド '{0}' を呼び出すべきではありませんでした</target>
        <note>{0} is the method name.</note>
      </trans-unit>
      <trans-unit id="TestHostAdapterInvokerFailedTestSessionErrorMessage">
        <source>Test adapter test session failure</source>
        <target state="translated">テスト アダプターのテスト セッション エラー</target>
        <note />
      </trans-unit>
      <trans-unit id="TestHostControllerConnectionInvalidAuthorizedSecurityIdentityErrorMessage">
        <source>The test host launcher '{0}' (UID: {1}) asked to authorize the security identity '{2}' on the test host controller connection, but only the identity of a single sandboxed application (on Windows, a security identifier of the form 'S-1-15-2-...') can be authorized. Users, groups and the catch-all '{3}' security identifier are never granted access.</source>
        <target state="new">The test host launcher '{0}' (UID: {1}) asked to authorize the security identity '{2}' on the test host controller connection, but only the identity of a single sandboxed application (on Windows, a security identifier of the form 'S-1-15-2-...') can be authorized. Users, groups and the catch-all '{3}' security identifier are never granted access.</target>
        <note>{0} is the launcher display name, {1} is the launcher unique identifier, {2} is the rejected security identity, {3} is the well-known 'ALL APPLICATION PACKAGES' security identifier. {Locked="'S-1-15-2-...'"}</note>
      </trans-unit>
      <trans-unit id="TestHostControllerProcessRestartNotSupportedOnWebAssembly">
        <source>Test host controller extensions that require process restart are not supported on browser/WebAssembly platforms.</source>
        <target state="translated">プロセスの再起動を必要とするテスト ホスト コントローラー拡張機能は、ブラウザー/WebAssembly プラットフォームではサポートされていません。</target>
        <note>{Locked="WebAssembly"}</note>
      </trans-unit>
      <trans-unit id="TestProcessDidNotExitGracefullyErrorMessage">
        <source>Test application process didn't exit gracefully, exit code is '{0}'</source>
        <target state="translated">テスト アプリケーション プロセスが正常に終了しませんでした。終了コードは '{0}' です</target>
        <note>{0} is the process exit code.</note>
      </trans-unit>
      <trans-unit id="TimeoutAcquiringSemaphoreErrorMessage">
        <source>Failed to acquire semaphore before timeout of '{0}' seconds</source>
        <target state="translated">タイムアウト '{0}' 秒前にセマフォを取得できませんでした</target>
        <note>{0} is the timeout in seconds.</note>
      </trans-unit>
      <trans-unit id="TimeoutFlushingLogsErrorMessage">
        <source>Failed to flush logs to log file '{0}' before the timeout of '{1}' seconds. The log file may be incomplete.</source>
        <target state="translated">'{1}' 秒のタイムアウト前にログをログ ファイル '{0}' にフラッシュできませんでした。ログ ファイルが不完全である可能性があります。</target>
        <note>{0} is the log file path. {1} is the timeout in seconds.</note>
      </trans-unit>
      <trans-unit id="Total">
        <source>Total</source>
        <target state="translated">合計</target>
        <note />
      </trans-unit>
      <trans-unit id="TreeNodeFilterCannotContainSlashCharacterErrorMessage">
        <source>A filter '{0}' should not contain a '/' character</source>
        <target state="translated">フィルター '{0}' に '/' 文字を含めることはできません</target>
        <note>{0} is the filter expression string. {Locked="/"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterDescription">
        <source>Use a tree filter to filter down the tests to execute</source>
        <target state="translated">ツリー フィルターを使用して実行するテストをフィルター処理する</target>
        <note />
      </trans-unit>
      <trans-unit id="TreeNodeFilterEscapeCharacterShouldNotBeLastErrorMessage">
        <source>An escape character should not terminate the filter string '{0}'</source>
        <target state="translated">エスケープ文字はフィルター文字列 '{0}' を終了できません</target>
        <note>{0} is the filter expression string.</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterOnlyLastLevelCanContainMutiLevelWildcardErrorMessage">
        <source>Only the final filter path can contain '**' wildcard</source>
        <target state="translated">'**' ワイルドカードを含めることができるのは、最後のフィルター パスのみです</target>
        <note>{Locked="**"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterOperatorNotAllowedErrorMessage">
        <source>Unexpected operator '&amp;' or '|' within filter expression '{0}'</source>
        <target state="translated">フィルター式 '{0}' 内で予期しない演算子 '&amp;' または '|' が発生しました</target>
        <note>{0} is the filter expression string. {Locked="&amp;"}{Locked="|"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterPathShouldStartWithSlashErrorMessage">
        <source>Invalid node path, expected root as first character '{0}'</source>
        <target state="translated">ノード パスが無効です。最初の文字 '{0}' としてルートが必要です</target>
        <note>{0} is the first character found in the invalid node path.</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterUnbalancedFilterErrorMessage">
        <source>Filter expression '{0}' contains an unbalanced number of '{1}' '{2}' operators</source>
        <target state="translated">フィルター式 '{0}' に '{1}' '{2}' 演算子の不均衡な数が含まれています</target>
        <note>{0} is the filter expression string. {1} and {2} are () or [] operator pairs. {Locked="()"}{Locked="[]"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterUnexpectedSlashOperatorErrorMessage">
        <source>Filter contains an unexpected '/' operator inside a parenthesized expression</source>
        <target state="translated">かっこで囲まれた式内に、予期しない '/' 演算子がフィルターに含まれています</target>
        <note>{Locked="/"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterUnexpectedSlashOperatorInPathSegmentErrorMessage">
        <source>Filter contains an unexpected '/' operator inside a parenthesized expression. Filter: '{0}'. To combine alternatives for one path segment, use syntax like '/A/B/C/(X|Y)'.</source>
        <target state="translated">フィルターのかっこで囲まれた式内に、予期しない '/' 演算子が含まれています。フィルター: '{0}'。1 つのパス セグメントの代替候補を組み合わせるには、'/A/B/C/(X|Y)' のような構文を使用します。</target>
        <note>{0} is the filter expression string. Diagnostic thrown by the TreeNodeFilter parser when a '/' is encountered inside a parenthesized alternative such as '/A/(B/C)'. {Locked="/"}{Locked="/A/B/C/(X|Y)"}{Locked="/A/(B/C)"}</note>
      </trans-unit>
      <trans-unit id="UnexpectedCallTelemetryIsDisabledErrorMessage">
        <source>Unexpected telemetry call, the telemetry is disabled.</source>
        <target state="translated">予期しないテレメトリ呼び出しです。テレメトリは無効になっています。</target>
        <note />
      </trans-unit>
      <trans-unit id="UnexpectedExceptionInFileLoggerErrorMessage">
        <source>An unexpected exception occurred in the 'FileLogger' write loop for log file '{0}'. The log file may be incomplete.
{1}</source>
        <target state="translated">ログ ファイル '{0}' の 'FileLogger' 書き込みループで予期しない例外が発生しました。ログ ファイルが不完全である可能性があります。
{1}</target>
        <note>{0} is the log file path. {1} is the exception ToString output. {Locked="FileLogger"}</note>
      </trans-unit>
      <trans-unit id="UnobservedTaskExceptionWarningMessage">
        <source>[ServerTestHost.OnTaskSchedulerUnobservedTaskException] Unhandled exception: {0}</source>
        <target state="translated">ハンドルされない例外 [ServerTestHost.OnTaskSchedulerUnobservedTaskException]: {0}</target>
        <note>{0} is the exception that was unhandled/unobserved. {Locked="ServerTestHost.OnTaskSchedulerUnobservedTaskException"}</note>
      </trans-unit>
      <trans-unit id="UnsupportedProviderTestExecutionFilter">
        <source>Test execution filter provider '{0}' returned unsupported filter type '{1}'. Providers can return only NopFilter, TestNodeUidListFilter, TreeNodeFilter, or an And CompositeTestExecutionFilter.</source>
        <target state="translated">テスト実行フィルター プロバイダー '{0}' は、サポートされていないフィルターの種類 '{1}' を返しました。プロバイダーは、NopFilter、TestNodeUidListFilter、TreeNodeFilter、または And CompositeTestExecutionFilter のみを返すことができます。</target>
        <note>{0} is the provider UID. {1} is the unsupported filter type. {Locked="NopFilter"}{Locked="TestNodeUidListFilter"}{Locked="TreeNodeFilter"}{Locked="And"}{Locked="CompositeTestExecutionFilter"}</note>
      </trans-unit>
      <trans-unit id="UnsupportedRequestTestExecutionFilter">
        <source>The request contains unsupported test execution filter type '{0}'.</source>
        <target state="translated">要求には、サポートされていないテスト実行フィルターの種類 '{0}' が含まれています。</target>
        <note>{0} is the unsupported filter type.</note>
      </trans-unit>
      <trans-unit id="UnsupportedTestExecutionFilterOperator">
        <source>Only the And test execution filter operator is supported.</source>
        <target state="translated">サポートされているテスト実行フィルター演算子は And のみです。</target>
        <note>{Locked="And"}</note>
      </trans-unit>
      <trans-unit id="UnsupportedTestExecutionFilterOperatorValue">
        <source>Test execution filter operator '{0}' is not supported. Only And is supported.</source>
        <target state="translated">テスト実行フィルター演算子 '{0}' はサポートされていません。And のみがサポートされています。</target>
        <note>{0} is the unsupported operator value. {Locked="And"}</note>
      </trans-unit>
      <trans-unit id="WaitDebuggerAttachNotSupportedInBrowserErrorMessage">
        <source>Waiting for debugger to attach (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1) is not supported in browser environments.</source>
        <target state="translated">デバッガーのアタッチの待機 (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1) は、ブラウザー環境ではサポートされていません。</target>
        <note>{Locked="TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1"}</note>
      </trans-unit>
      <trans-unit id="WaitDebuggerAttachNotSupportedInWasiErrorMessage">
        <source>Waiting for debugger to attach (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1) is not supported on wasi.</source>
        <target state="translated">デバッガーのアタッチの待機 (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1) は、wasi ではサポートされていません。</target>
        <note>{Locked="TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1"}{Locked="wasi"}</note>
      </trans-unit>
      <trans-unit id="ZeroTestsRan">
        <source>Zero tests ran</source>
        <target state="translated">0 件のテストが実行されました</target>
        <note />
      </trans-unit>
      <trans-unit id="TotalLowercase">
        <source>total</source>
        <target state="translated">合計</target>
        <note />
      </trans-unit>
      <trans-unit id="ChatClientProviderAlreadyRegistered">
        <source>A chat client provider has already been registered.</source>
        <target state="translated">チャット クライアント プロバイダーは既に登録されています。</target>
        <note />
      </trans-unit>
    </body>
  </file>
</xliff>