<?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="ko" 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">잘못된 인자입니다. 최대값은 최소값보다 커야 합니다.</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}'(UID: {2})의 옵션 '--{0}'에 인수가 필요하지 않습니다.</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}'(UID: {2})의 옵션 '-- {0}'이 예약된 접두사 '--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">'-- {1} ' 옵션의 인수 {0}에 예기치 않은 작은따옴표가 있습니다.</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">복합 테스트 실행 필터에는 두 개 이상의 자식 필터가 필요합니다.</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 파일의 '{1}' 섹션 아래에 있는 항목 '{0}'('{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">testconfig.json의 '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 파일('{2}')의 '{1}' 섹션 아래에 있는 '{0}' 항목은 스칼라 문자열 값이어야 합니다. 중첩된 개체와 배열은 지원되지 않습니다.</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 파일('{1}')의 '{0}' 섹션은 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">테스트 호스트 시작 관리자는 하나만 등록할 수 있습니다.</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}'에는 단일 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이 아닌 단일 양의 정수 값이 필요합니다.
(예: '--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}'에는 단일 유효한 포트가 인수로 필요합니다.</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일) 내의 양수 값을 하나의 인수로 입력해야 합니다. 허용되는 접미사는 '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">전역 테스트 실행 시간 제한입니다.
명시적 단위 접미사가 포함된 시간 값을 하나의 인수로 입력해야 합니다. 허용되는 접미사는 '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'는 건너뛴 테스트를 실행된 것으로 계산하므로, 테스트를 하나도 찾지 못한 실행만 종료 코드 8로 실패합니다. 'strict'는 건너뛴 테스트를 실행되지 않은 것으로 처리하므로, 모든 테스트를 건너뛴 실행 또는 테스트를 찾지 못한 실행은 종료 코드 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 테스트 플랫폼은 사용자 환경 개선을 위해 사용량 데이터를 수집합니다. 데이터는 Microsoft에서 수집하며 누구와도 공유되지 않습니다.
즐겨 찾는 셸을 사용하여 TESTINGPLATFORM_TELEMETRY_OPTOUT 또는 DOTNET_CLI_TELEMETRY_OPTOUT 환경 변수를 '1' 또는 'true'로 설정하여 원격 분석을 옵트아웃할 수 있습니다.

Microsoft 테스트 플랫폼 원격 분석에 대해 자세히 알아보기: 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 모드는 프로세스당 단일 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">JSON-RPC 서버 요청에 대해 테스트 실행 필터 공급자 '{0}'이(가) 필터 유형 '{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}'. 하나의 경로 세그먼트에 대한 여러 대안을 결합하려면 '/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>