<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.2" xsi:schemaLocation="urn:oasis:names:tc:xliff:document:1.2 xliff-core-1.2-transitional.xsd">
  <file datatype="xml" source-language="en" original="../Resource.resx" target-language="ko">
    <body>
      <trans-unit id="AssemblyCleanupTimedOut">
        <source>Assembly cleanup method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 어셈블리 정리 메서드 '{0}.{1}'이(가) 시간 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the assembly cleanup method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="AssemblyCleanupWasCancelled">
        <source>Assembly cleanup method '{0}.{1}' was canceled</source>
        <target state="translated">어셈블리 정리 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the assembly cleanup method name.</note>
      </trans-unit>
      <trans-unit id="AssemblyInitializeTimedOut">
        <source>Assembly initialize method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 '{0}.{1}' 어셈블리 초기화 메서드의 시간이 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the assembly initialize method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="AssemblyInitializeWasCancelled">
        <source>Assembly initialize method '{0}.{1}' was canceled</source>
        <target state="translated">어셈블리 초기화 메서드 '{0}.{1}'(이)가 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the assembly initialize method name.</note>
      </trans-unit>
      <trans-unit id="AttachmentSetDisplayName">
        <source>MSTestAdapterV2</source>
        <target state="translated">MSTestAdapterV2</target>
        <note>{Locked="MSTestAdapterV2"}</note>
      </trans-unit>
      <trans-unit id="CannotEnumerateIDataSourceAttribute">
        <source>Exception occurred while enumerating IDataSource attribute on "{0}.{1}": {2}</source>
        <target state="translated">"{0}.{1}"에서 IDataSource 특성을 열거하는 동안 예외가 발생했습니다. {2}</target>
        <note>{0} is the type name with namespace. {1} is the method name. {2} is the exception details. {Locked="IDataSource"}</note>
      </trans-unit>
      <trans-unit id="CannotExpandIDataSourceAttribute">
        <source>Exception occurred while expanding IDataSource rows from attribute on "{0}.{1}": {2}</source>
        <target state="translated">"{0}.{1}"의 특성에서 IDataSource 행을 확장하는 동안 예외가 발생했습니다. {2}</target>
        <note>{0} is the type name with namespace. {1} is the method name. {2} is the row expansion warning. {Locked="IDataSource"}{Locked="CannotExpandIDataSourceAttribute_DuplicateDisplayName"}{Locked="CannotExpandIDataSourceAttribute_CannotSerialize"}</note>
      </trans-unit>
      <trans-unit id="CannotExpandIDataSourceAttribute_CannotSerialize">
        <source>Data on index {0} for "{1}" cannot be serialized. All data provided through "IDataSource" should be serializable. If you need to test non-serializable data sources, please make sure you add "TestDataSourceDiscovery" attribute on your test assembly and set the discovery option to "DuringExecution".</source>
        <target state="translated">"{1}"에 대한 {0} 인덱스의 데이터를 직렬화할 수 없습니다. "IDataSource"를 통해 제공된 모든 데이터를 직렬화할 수 있어야 합니다. 직렬화할 수 없는 데이터 원본을 테스트해야 하는 경우 테스트 어셈블리에 "TestDataSourceDiscovery" 특성을 추가하고 검색 옵션을 "DuringExecution"으로 설정하세요.</target>
        <note>{0} is the zero-based data row index. {1} is the test name. {Locked="IDataSource"}{Locked="TestDataSourceDiscovery"}{Locked="DuringExecution"}</note>
      </trans-unit>
      <trans-unit id="CannotFindFile">
        <source>Could not find file '{0}'.</source>
        <target state="translated">'{0}' 파일을 찾을 수 없습니다.</target>
        <note>{0} is the file path.</note>
      </trans-unit>
      <trans-unit id="CannotRunTestArgumentsMismatchError">
        <source>Cannot run test method '{0}.{1}': Test data doesn't match method parameters. Either the count or types are different.
Test expected {2} parameter(s), with types '{3}',
but received {4} argument(s), with types '{5}'.</source>
        <target state="translated">테스트 메서드 '{0}{1}'을(를) 실행할 수 없음: 테스트 데이터가 메서드 매개 변수와 일치하지 않습니다. 개수 또는 형식이 다릅니다.
테스트에 {2} 매개 변수로 ‘{3}’ 형식이 필요하지만,
{4} 인수의 ‘{5}’ 형식을 받았습니다.</target>
        <note>{0} is the declaring type full name. {1} is the method name. {2} is the expected parameter count. {3} is the expected parameter type list. {4} is the received argument count. {5} is the received argument type list.</note>
      </trans-unit>
      <trans-unit id="CannotRunTestMethodNoDataError">
        <source>Cannot run test method '{0}.{1}': Method has parameters, but does not define any test source. Use '[DataRow]', '[DynamicData]', or a custom 'ITestDataSource' data source to provide test data.</source>
        <target state="translated">테스트 메서드 '{0}{1}'을(를) 실행할 수 없음: 메서드에 매개 변수가 있지만 테스트 원본을 정의하지 않습니다. '[DataRow]', '[DynamicData]' 또는 사용자 지정 'ITestDataSource' 데이터 원본을 사용하여 테스트 데이터를 제공합니다.</target>
        <note>{0} is the declaring type full name. {1} is the method name. {Locked="[DataRow]"}{Locked="[DynamicData]"}{Locked="ITestDataSource"}</note>
      </trans-unit>
      <trans-unit id="ClassCleanupTimedOut">
        <source>Class cleanup method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 클래스 정리 메서드 '{0}.{1}'이(가) 시간 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the class cleanup method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="ClassCleanupWasCancelled">
        <source>Class cleanup method '{0}.{1}' was canceled</source>
        <target state="translated">클래스 정리 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the class cleanup method name.</note>
      </trans-unit>
      <trans-unit id="ClassInitializeTimedOut">
        <source>Class initialize method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 '{0}.{1}' 클래스 초기화 메서드의 시간이 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the class initialize method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="ClassInitializeWasCancelled">
        <source>Class initialize method '{0}.{1}' was canceled</source>
        <target state="translated">'클래스 초기화 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the class initialize method name.</note>
      </trans-unit>
      <trans-unit id="Common_CannotBeNullOrEmpty">
        <source>The parameter should not be null or empty.</source>
        <target state="translated">매개 변수는 null이거나 비워 둘 수 없습니다.</target>
        <note>{Locked="null"}</note>
      </trans-unit>
      <trans-unit id="CouldNotInspectTypeDuringDiscovery">
        <source>MSTestAdapter failed to discover tests in class '{0}' of assembly '{1}' because {2}.</source>
        <target state="translated">MSTestAdapter가 {2} 때문에 어셈블리 '{1}'의 클래스 '{0}'에서 테스트를 검색하지 못했습니다.</target>
        <note>{0} is the class name. {1} is the assembly path. {2} is the failure reason. {Locked="MSTestAdapter"}</note>
      </trans-unit>
      <trans-unit id="DataDrivenResultDisplayName">
        <source>{0} (Data Row {1})</source>
        <target state="translated">{0}(데이터 행 {1})</target>
        <note>{0} is the test display name. {1} is the data row index.</note>
      </trans-unit>
      <trans-unit id="DebugTraceBanner">
        <source>Debug Trace:</source>
        <target state="translated">디버그 추적:</target>
        <note />
      </trans-unit>
      <trans-unit id="DependencyConfigurationDependentNotFound">
        <source>The 'mstest:execution:dependencies' configuration section declares dependencies for '{0}', which matches no test in this run. They are ignored.</source>
        <target state="translated">'mstest:execution:dependencies' 구성 섹션은 이번 실행에서 어떤 테스트와도 일치하지 않는 '{0}'에 대한 종속성을 선언합니다. 이 참조는 무시됩니다.</target>
        <note>{0} is the declared test reference. {Locked="mstest:execution:dependencies"}</note>
      </trans-unit>
      <trans-unit id="DependencyConfigurationEmptyChain">
        <source>The chain at index {0} of the 'mstest:execution:dependencies:chains' configuration section is empty and declares no dependency. Remove it: a chain needs at least two tests to express an order.</source>
        <target state="translated">'mstest:execution:dependencies:chains' 구성 섹션의 인덱스 {0}에 있는 체인은 비어 있고 종속성을 선언하지 않습니다. 제거하세요. 체인으로 순서를 표현하려면 최소 두 개의 테스트가 필요합니다.</target>
        <note>{0} is the zero-based index of the empty chain. {Locked="mstest:execution:dependencies:chains"}</note>
      </trans-unit>
      <trans-unit id="DependencyConfigurationInvalidReference">
        <source>The test reference '{0}' in the 'mstest:execution:dependencies' configuration section is not valid. Use 'Namespace.Class.Method', or 'Namespace.Class.*' for every test of a class.</source>
        <target state="translated">'mstest:execution:dependencies' 구성 섹션의 테스트 참조 '{0}'은(는) 잘못되었습니다. 모든 클래스 테스트에는 'Namespace.Class.Method' 또는 'Namespace.Class.*'를 사용하세요.</target>
        <note>{0} is the invalid reference. {Locked="mstest:execution:dependencies"}</note>
      </trans-unit>
      <trans-unit id="DependencyConfigurationNodeWithoutPrerequisites">
        <source>The 'mstest:execution:dependencies' configuration section declares a node for '{0}' with no 'dependsOn' entries, which has no effect.</source>
        <target state="translated">'mstest:execution:dependencies' 구성 섹션은 'dependsOn' 항목이 없는 '{0}'에 대한 노드를 선언합니다. 이 설정은 아무 영향도 없습니다.</target>
        <note>{0} is the declared test reference. {Locked="mstest:execution:dependencies"}{Locked="dependsOn"}</note>
      </trans-unit>
      <trans-unit id="DependencyConfigurationNodeWithoutTest">
        <source>The dependency node at index {0} of the 'mstest:execution:dependencies:nodes' configuration section has no 'test' value and is ignored.</source>
        <target state="translated">'mstest:execution:dependencies:nodes' 구성 섹션의 인덱스 {0}에 있는 종속성 노드에 'test' 값이 없으므로 무시됩니다.</target>
        <note>{0} is the zero-based index of the node. {Locked="mstest:execution:dependencies:nodes"}{Locked="test"}</note>
      </trans-unit>
      <trans-unit id="DependsOnClassLevelCycle">
        <source>Dependencies between the following test classes cannot be scheduled with class-level parallelization because the classes depend on each other: {0}. Their tests are run sequentially, in dependency order, so the declared order is still honored. Use &lt;Scope&gt;MethodLevel&lt;/Scope&gt; (or [Parallelize(Scope = ExecutionScope.MethodLevel)]) to schedule each test individually and run them in parallel again.</source>
        <target state="translated">다음 테스트 클래스는 서로 종속되어 있으므로 클래스 수준 병렬 처리로는 예약할 수 없습니다. {0}. 테스트는 종속성 순서에 따라 순차적으로 실행되므로 선언된 순서는 그대로 유지됩니다. 각 테스트를 개별적으로 예약하고 다시 병렬로 실행하려면 &lt;Scope&gt;MethodLevel&lt;/Scope&gt; 또는 [Parallelize(Scope = ExecutionScope.MethodLevel)]를 사용하세요.</target>
        <note>{0} is a comma-separated list of test class names. {Locked="MethodLevel"}{Locked="[Parallelize(Scope = ExecutionScope.MethodLevel)]"}{Locked="Scope"}</note>
      </trans-unit>
      <trans-unit id="DependsOnCycle">
        <source>Dependency cycle detected between tests: {0}. The tests in the cycle cannot be ordered and are reported as failed. Remove one of the dependency declarations to break the cycle.</source>
        <target state="translated">테스트 간에 종속성 순환이 감지되었습니다. {0}. 순환에 있는 테스트는 순서를 정할 수 없으므로 실패한 것으로 보고됩니다. 종속성 선언 중 하나를 제거하여 순환을 끊으세요.</target>
        <note>{0} is the cycle rendered as a path, for example 'A &gt; B &gt; A'.</note>
      </trans-unit>
      <trans-unit id="DependsOnPrerequisiteNotPassed">
        <source>Test skipped because it depends on '{0}', which did not pass.</source>
        <target state="translated">'{0}'에 종속되어 있지만 해당 테스트를 통과하지 못했기 때문에 테스트를 건너뜁니다.</target>
        <note>{0} is the fully qualified name of the test that did not pass.</note>
      </trans-unit>
      <trans-unit id="DependsOnTargetNotFound">
        <source>Test '{0}' declares a dependency on '{1}', which matches no test in this test source. Dependencies are resolved within a single source, so a target in another test assembly is not supported. The dependency is ignored.</source>
        <target state="translated">테스트 '{0}'이(가) '{1}'에 대한 종속성을 선언하지만, 이는 이 테스트 소스의 어떤 테스트와도 일치하지 않습니다. 종속성은 단일 소스 내에서만 해결되므로 다른 테스트 어셈블리의 대상을 지원하지 않습니다. 이 종속성은 무시됩니다.</target>
        <note>{0} is the fully qualified name of the test declaring the dependency. {1} is the declared target.</note>
      </trans-unit>
      <trans-unit id="DeploymentDependencyLoadFailed">
        <source>Test Run deployment issue: Failed to load the assembly or module '{0}'. Reason: {1}</source>
        <target state="translated">테스트 실행 배포 문제: 어셈블리 또는 모듈 '{0}'을(를) 로드하지 못했습니다. 이유: {1}</target>
        <note>{0} is the assembly or module path or assembly identity. {1} is the reason the assembly or module could not be loaded.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorBadDeploymentItem">
        <source>Test Run deployment issue: Bad deployment item: '{0}': output directory '{1}' specifies the item to be deployed outside deployment root directory which is not allowed.</source>
        <target state="translated">테스트 실행 배포 문제: 잘못된 배포 항목: '{0}': 출력 디렉터리 '{1}'에서 항목을 배포 루트 디렉터리 외부에 배포하도록 지정하며 이는 허용되지 않습니다.</target>
        <note>{0} is the deployment item path. {1} is the output directory.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorFailedToAccesOutputDirectory">
        <source>Test Run deployment issue: Failed to access output directory '{1}' specified by deployment item '{0}', the item will not be deployed: {2}: {3}</source>
        <target state="translated">테스트 실행 배포 문제: 배포 항목 '{0}'에 의해 지정된 출력 디렉터리 '{1}'에 액세스하지 못했습니다. 항목이 배포되지 않음: {2}: {3}</target>
        <note>{0} is the deployment item path. {1} is the output directory. {2} is the exception type. {3} is the exception message.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorFailedToAccessFile">
        <source>Test Run deployment issue: Failed to access the file '{0}': {1}: {2}</source>
        <target state="translated">테스트 실행 배포 문제: '{0}' 파일에 액세스하지 못함: {1}: {2}</target>
        <note>{0} is the file path. {1} is the exception type. {2} is the exception message.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorFailedToCopyWithOverwrite">
        <source>Test Run deployment issue: Failed to copy file '{0}' to '{1}': {2}: {3} (HResult: 0x{4:X8})</source>
        <target state="translated">테스트 실행 배포 문제: '{0}' 파일을 '{1}'에 복사하지 못함: {2}: {3} (HResult: 0x{4:X8})</target>
        <note>{0} is the source file path. {1} is the destination file path. {2} is the exception type. {3} is the exception message. {4} is the exception HResult.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorFailedToDeployDependencies">
        <source>Test Run deployment issue: Failed to deploy dependencies for test storage '{0}': {1}</source>
        <target state="translated">테스트 실행 배포 문제: 테스트 스토리지 '{0}'에 대한 종속성을 배포하지 못함: {1}</target>
        <note>{0} is the test storage or source path. {1} is the exception details.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorFailedToGetFileForDeploymentItem">
        <source>Test Run deployment issue: Failed to get the file for {0}: {1}: {2}</source>
        <target state="translated">테스트 실행 배포 문제: {0}에 대한 파일을 가져오지 못함: {1}: {2}</target>
        <note>{0} is the deployment item description. {1} is the exception type. {2} is the exception message.</note>
      </trans-unit>
      <trans-unit id="DeploymentErrorGettingSatellite">
        <source>Test Run deployment issue: an error occurred while getting satellite assemblies for {0}: {1}: {2}</source>
        <target state="translated">테스트 실행 배포 문제: {0}에 대한 위성 어셈블리를 가져오는 동안 오류 발생: {1}: {2}</target>
        <note>{0} is the deployment item. {1} is the exception type. {2} is the exception message.</note>
      </trans-unit>
      <trans-unit id="DeploymentItem">
        <source>deployment item '{0}'</source>
        <target state="translated">배포 항목 '{0}'</target>
        <note>{0} is the deployment item path.</note>
      </trans-unit>
      <trans-unit id="DeploymentItemContainsInvalidCharacters">
        <source>Invalid deployment item: the specified path '{0}' or output directory '{1}' contains illegal characters.</source>
        <target state="translated">잘못된 배포 항목: 지정된 경로 '{0}' 또는 출력 디렉터리 '{1}'에 잘못된 문자가 들어 있습니다.</target>
        <note>{0} is the deployment item path. {1} is the output directory.</note>
      </trans-unit>
      <trans-unit id="DeploymentItemOutputDirectoryCannotBeNull">
        <source>Invalid deployment item: the output directory cannot be null.</source>
        <target state="translated">잘못된 배포 항목: 출력 디렉터리는 null일 수 없습니다.</target>
        <note>{Locked="null"}</note>
      </trans-unit>
      <trans-unit id="DeploymentItemOutputDirectoryMustBeRelative">
        <source>Invalid deployment item: the specified output directory '{0}' is not relative.</source>
        <target state="translated">잘못된 배포 항목: 지정된 출력 디렉터리 '{0}'이(가) 상대 디렉터리가 아닙니다.</target>
        <note>{0} is the output directory.</note>
      </trans-unit>
      <trans-unit id="DeploymentItemPathCannotBeNullOrEmpty">
        <source>Invalid deployment item: the path must contain at least one character.</source>
        <target state="translated">잘못된 배포 항목: 경로에는 하나 이상의 문자가 포함되어 있어야 합니다.</target>
        <note></note>
      </trans-unit>
      <trans-unit id="DeploymentItemWithOutputDirectory">
        <source>deployment item '{0}' (output directory '{1}')</source>
        <target state="translated">배포 항목 '{0}'(출력 디렉터리 '{1}')</target>
        <note>{0} is the deployment item path. {1} is the output directory.</note>
      </trans-unit>
      <trans-unit id="DeprecatedFlatOrderTestsByNameInClassKey">
        <source>The 'mstest:orderTestsByNameInClass' configuration key is deprecated and will be removed in a future version. Use 'mstest:execution:orderTestsByNameInClass' instead.</source>
        <target state="translated">'mstest:orderTestsByNameInClass' 구성 키는 더 이상 사용되지 않으며 향후 버전에서 제거됩니다. 대신 'mstest:execution:orderTestsByNameInClass'를 사용하세요.</target>
        <note>{Locked="mstest:orderTestsByNameInClass"}{Locked="mstest:execution:orderTestsByNameInClass"}</note>
      </trans-unit>
      <trans-unit id="DiscoveryErrors">
        <source>Discovery failed for source '{0}' with {1} errors:
{2}</source>
        <target state="translated">{1} 오류로 인해 원본 '{0}' 검색에 실패했습니다. 
{2}</target>
        <note>{0} is the source path. {1} is the error count. {2} is the error details.</note>
      </trans-unit>
      <trans-unit id="DiscoveryWarning">
        <source>[MSTest][Discovery][{0}] {1}</source>
        <target state="translated">[MSTest][Discovery][{0}] {1}</target>
        <note>{0} is the source path. {1} is the discovery warning message. {Locked="[MSTest][Discovery]"}</note>
      </trans-unit>
      <trans-unit id="DuplicateAttributeError">
        <source>Only one attribute of type '{0}' is allowed, but multiple were found.</source>
        <target state="translated">'{0}' 형식의 특성은 하나만 허용되지만 여러 개가 발견되었습니다.</target>
        <note>{0} is the attribute type name.</note>
      </trans-unit>
      <trans-unit id="DuplicateConfigurationError">
        <source>Both '.runsettings' and '.testconfig.json' files have been detected. Please select only one of these test configuration files.</source>
        <target state="translated">'.runsettings' 및 '.testconfig.json' 파일이 모두 검색되었습니다. 이러한 테스트 구성 파일 중 하나만 선택하세요.</target>
        <note>{Locked=".runsettings"}{Locked=".testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="ExceptionOccuredWhileGettingTheExceptionDescription">
        <source>"{0}": (Failed to get exception description due to an exception of type "{1}".</source>
        <target state="translated">"{0}": ("{1}" 형식의 예외로 인해 예외 설명을 가져오지 못했습니다.</target>
        <note>{0} is the type of the original exception. {1} is the thrown exception type.</note>
      </trans-unit>
      <trans-unit id="Execution_Test_Cancelled">
        <source>Test '{0}' was canceled</source>
        <target state="translated">테스트 '{0}'이(가) 취소되었습니다.</target>
        <note>{0} is the test name.</note>
      </trans-unit>
      <trans-unit id="Execution_Test_Timeout">
        <source>Test '{0}' timed out after {1}ms</source>
        <target state="translated">테스트 '{0}'이(가) {1}밀리초 후에 시간 초과되었습니다.</target>
        <note>{0} is the test name. {1} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="FailedToGetCustomAttribute">
        <source>Getting custom attributes for type {0} threw exception (will ignore and use the reflection way): {1}</source>
        <target state="translated">{0} 형식에 대한 사용자 지정 특성을 가져오는 데 예외가 발생했습니다(무시하고 리플렉션 방법 사용). {1}</target>
        <note>{0} is the attribute full type name. {1} is the exception description.</note>
      </trans-unit>
      <trans-unit id="GenericParameterCantBeInferred">
        <source>The type of the generic parameter '{0}' could not be inferred.</source>
        <target state="translated">제네릭 매개 변수 '{0}'의 형식을 유추할 수 없습니다.</target>
        <note>{0} is the generic parameter name.</note>
      </trans-unit>
      <trans-unit id="GenericParameterCantBeInferredBecauseNoArguments">
        <source>The generic test method '{0}' doesn't have arguments, so the generic parameter cannot be inferred.</source>
        <target state="translated">제네릭 테스트 메서드 '{0}'에 인수가 없으므로 제네릭 매개 변수를 유추할 수 없습니다.</target>
        <note>{0} is the generic test method name.</note>
      </trans-unit>
      <trans-unit id="GenericParameterConflict">
        <source>Found two conflicting types for generic parameter '{0}'. The conflicting types are '{1}' and '{2}'.</source>
        <target state="translated">제네릭 매개 변수 '{0}'에 대해 충돌하는 두 가지 형식을 찾았습니다. 충돌하는 형식은 '{1}' 및 ''{2}입니다.</target>
        <note>{0} is the generic parameter name. {1} is the first conflicting type. {2} is the second conflicting type.</note>
      </trans-unit>
      <trans-unit id="GlobalTestCleanupTimedOut">
        <source>Global test cleanup method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 전역 테스트 정리 메서드 '{0}.{1}'이(가) 시간 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the global test cleanup method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="GlobalTestCleanupWasCancelled">
        <source>Global test cleanup method '{0}.{1}' was canceled</source>
        <target state="translated">전역 테스트 정리 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the global test cleanup method name.</note>
      </trans-unit>
      <trans-unit id="GlobalTestInitializeTimedOut">
        <source>Global test initialize method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 '{0}.{1}' 전역 테스트 초기화 메서드의 시간이 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the global test initialize method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="GlobalTestInitializeWasCancelled">
        <source>Global test initialize method '{0}.{1}' was canceled</source>
        <target state="translated">전역 테스트 초기화 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the global test initialize method name.</note>
      </trans-unit>
      <trans-unit id="InvalidParallelScopeValue">
        <source>Invalid value '{0}' specified for 'Scope'. Supported scopes are {1}.</source>
        <target state="translated">'Scope'에 대해 잘못된 값 '{0}'이(가) 지정되었습니다. 지원되는 범위는 {1}입니다.</target>
        <note>{0} is the invalid scope value. {1} is the supported scope list. {Locked="Scope"}</note>
      </trans-unit>
      <trans-unit id="InvalidParallelWorkersValue">
        <source>Invalid value '{0}' specified for 'Workers'. The value should be a non-negative integer.</source>
        <target state="translated">'Workers'에 대해 잘못된 값 '{0}'이(가) 지정되었습니다. 이 값은 음수가 아닌 정수여야 합니다.</target>
        <note>{0} is the invalid worker count. {Locked="Workers"}</note>
      </trans-unit>
      <trans-unit id="InvalidSettingsXml">
        <source>MSTestAdapter failed to parse the runsettings XML.</source>
        <target state="translated">MSTestAdapter가 runsettings XML을 구문 분석하지 못했습니다.</target>
        <note>{Locked="MSTestAdapter"}{Locked="runsettings"}</note>
      </trans-unit>
      <trans-unit id="InvalidSettingsXmlAttribute">
        <source>Invalid settings '{0}'. Unexpected XmlAttribute: '{1}'.</source>
        <target state="translated">'{0}' 설정이 잘못되었습니다. 예기치 않은 XmlAttribute '{1}'이(가) 있습니다.</target>
        <note>{0} is the settings element name. {1} is the unexpected XML attribute name. {Locked="XmlAttribute"}</note>
      </trans-unit>
      <trans-unit id="InvalidSettingsXmlElement">
        <source>MSTestAdapter encountered an unexpected element '{0}' in its settings '{1}'. Remove this element and try again.</source>
        <target state="translated">MSTestAdapter의 '{1}' 설정에서 예기치 않은 요소 '{0}'이(가) 발견되었습니다. 이 요소를 제거하고 다시 시도하세요.</target>
        <note>{0} is the unexpected XML element name. {1} is the settings section name. {Locked="MSTestAdapter"}</note>
      </trans-unit>
      <trans-unit id="InvalidTimeoutValue">
        <source>Invalid value '{0}' for runsettings entry '{1}'. The timeout must be a strictly positive integer (in milliseconds); a value of 0 or less is not allowed. Omit the entry to use the default (no timeout). The setting will be ignored.</source>
        <target state="translated">runsettings 항목 '{1}'의 값 '{0}'이(가) 잘못되었습니다. 시간 제한은 0보다 큰 정수(밀리초)여야 하며, 0 이하의 값은 허용되지 않습니다. 기본값(시간 제한 없음)을 사용하려면 항목을 생략하세요. 이 설정은 무시됩니다.</target>
        <note>{0} is the invalid value. {1} is the runsettings entry name. {Locked="runsettings"}</note>
      </trans-unit>
      <trans-unit id="InvalidValue">
        <source>Invalid value '{0}' for runsettings entry '{1}', setting will be ignored.</source>
        <target state="translated">runsettings 항목 '{1}'에 대해 '{0}' 값이 잘못되었습니다. 설정은 무시됩니다.</target>
        <note>{0} is the invalid value. {1} is the runsettings entry name. {Locked="runsettings"}</note>
      </trans-unit>
      <trans-unit id="MissingDeploymentDependency">
        <source>Test Run deployment issue: The assembly or module '{0}' was not found. Reason: {1}</source>
        <target state="translated">테스트 실행 배포 문제: 어셈블리 또는 모듈 '{0}'을(를) 찾을 수 없습니다. 이유: {1}</target>
        <note>{0} is the assembly or module name. {1} is the reason the dependency was not found.</note>
      </trans-unit>
      <trans-unit id="MissingDeploymentDependencyWithoutReason">
        <source>Test Run deployment issue: The assembly or module '{0}' was not found.</source>
        <target state="translated">테스트 실행 배포 문제: 어셈블리 또는 모듈 '{0}'을(를) 찾을 수 없습니다.</target>
        <note>{0} is the assembly or module name.</note>
      </trans-unit>
      <trans-unit id="OlderTFMVersionFound">
        <source>An older version of MSTestV2 package is loaded in assembly, test discovery might fail to discover all data tests if they depend on `.runsettings` file.</source>
        <target state="translated">이전 버전 MSTestV2 패키지가 어셈블리에 로드되어 테스트 검색이 '.runsettings' 파일에 종속된 경우 모든 데이터 테스트를 검색하지 못할 수 있습니다.</target>
        <note>{Locked="MSTestV2"}{Locked=".runsettings"}</note>
      </trans-unit>
      <trans-unit id="RandomTestOrderAndOrderTestsByNameInClassConflict">
        <source>Both 'RandomizeTestOrder' and 'OrderTestsByNameInClass' are set. 'OrderTestsByNameInClass' will be ignored.</source>
        <target state="translated">'RandomizeTestOrder'와 'OrderTestsByNameInClass'가 모두 설정되어 있습니다. 'OrderTestsByNameInClass'는 무시됩니다.</target>
        <note>{Locked="RandomizeTestOrder"}{Locked="OrderTestsByNameInClass"}</note>
      </trans-unit>
      <trans-unit id="RandomTestOrderBanner">
        <source>Random test order enabled (Seed: {0}). Set 'RandomTestOrderSeed' to reproduce this order.</source>
        <target state="translated">임의 테스트 순서가 활성화되었습니다(Seed: {0}). 이 순서를 재현하려면 'RandomTestOrderSeed'를 설정하세요.</target>
        <note>{0} is the random test order seed. {Locked="Seed"}{Locked="RandomTestOrderSeed"}</note>
      </trans-unit>
      <trans-unit id="STAIsOnlySupportedOnWindowsWarning">
        <source>Runsettings entry '&lt;ExecutionApartmentState&gt;STA&lt;/ExecutionApartmentState&gt;' is not supported on non-Windows OSes.</source>
        <target state="translated">Runsettings 항목 '&lt;ExecutionApartmentState&gt;STA&lt;/ExecutionApartmentState&gt;'는 Windows 이외의 OS에서는 지원되지 않습니다.</target>
        <note>{Locked="Runsettings"}{Locked="&lt;ExecutionApartmentState&gt;STA&lt;/ExecutionApartmentState&gt;"}{Locked="STA"}</note>
      </trans-unit>
      <trans-unit id="SourcesNotSupported">
        <source>Running tests in any of the provided sources is not supported for the selected platform</source>
        <target state="translated">선택된 플랫폼의 경우 제공된 소스에서 테스트를 실행할 수 없습니다.</target>
        <note />
      </trans-unit>
      <trans-unit id="TestAssembly_FileDoesNotExist">
        <source>File does not exist: {0}</source>
        <target state="translated">파일이 없습니다. {0}</target>
        <note>{0} is the file path.</note>
      </trans-unit>
      <trans-unit id="TestCleanupTimedOut">
        <source>Test cleanup method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 테스트 정리 메서드 '{0}.{1}'이(가) 시간 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the test cleanup method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="TestCleanupWasCancelled">
        <source>Test cleanup method '{0}.{1}' was canceled</source>
        <target state="translated">테스트 정리 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the test cleanup method name.</note>
      </trans-unit>
      <trans-unit id="TestContextMessageBanner">
        <source>TestContext Messages:</source>
        <target state="translated">TestContext 메시지:</target>
        <note>{Locked="TestContext"}</note>
      </trans-unit>
      <trans-unit id="TestInitializeTimedOut">
        <source>Test initialize method '{0}.{1}' timed out after {2}ms</source>
        <target state="translated">{2}밀리초 후 '{0}.{1}' 테스트 초기화 메서드의 시간이 초과되었습니다.</target>
        <note>{0} is the type name. {1} is the test initialize method name. {2} is the timeout in milliseconds.</note>
      </trans-unit>
      <trans-unit id="TestInitializeWasCancelled">
        <source>Test initialize method '{0}.{1}' was canceled</source>
        <target state="translated">테스트 초기화 메서드 '{0}.{1}'이(가) 취소되었습니다.</target>
        <note>{0} is the type name. {1} is the test initialize method name.</note>
      </trans-unit>
      <trans-unit id="TestNotFound">
        <source>Test method {0} was not found.</source>
        <target state="translated">{0} 테스트 메서드를 찾을 수 없습니다.</target>
        <note>{0} is the test method name.</note>
      </trans-unit>
      <trans-unit id="TestParallelizationBanner">
        <source>Test Parallelization enabled for {0} (Workers: {1}, Scope: {2})</source>
        <target state="translated">{0}에 대해 테스트 병렬 처리를 사용합니다(Workers: {1}, Scope: {2}).</target>
        <note>{0} is the test source path. {1} is the worker count. {2} is the parallelization scope. {Locked="Workers"}{Locked="Scope"}</note>
      </trans-unit>
      <trans-unit id="TestRunName">
        <source>{0}_{1} {2}</source>
        <target state="translated">{0}_{1} {2}</target>
        <note>{0} is the deployment folder prefix. {1} is the user name. {2} is the date/time and process id suffix.</note>
      </trans-unit>
      <trans-unit id="UTA_AssemblyCleanupMethodWasUnsuccesful">
        <source>Assembly Cleanup method {0}.{1} failed. Error Message: {2}. StackTrace: {3}</source>
        <target state="translated">어셈블리 정리 메서드 {0}.{1}이(가) 실패했습니다. 오류 메시지: {2}. StackTrace: {3}</target>
        <note>{0} is the declaring type name. {1} is the assembly cleanup method name. {2} is the error message. {3} is the stack trace.</note>
      </trans-unit>
      <trans-unit id="UTA_AssemblyFixtureProviderTypeIsGeneric">
        <source>UTA070: Type '{0}' referenced by [AssemblyFixtureProvider] must not be generic.</source>
        <target state="translated">UTA070: [AssemblyFixtureProvider]에서 참조하는 형식 '{0}'은 제네릭이 아니어야 합니다.</target>
        <note>{0} is the fixture provider type name. {Locked="UTA070"}{Locked="[AssemblyFixtureProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_AssemblyFixtureProviderTypeReflectionFailed">
        <source>UTA071: Failed to enumerate methods on type '{0}' referenced by [AssemblyFixtureProvider]. {1}</source>
        <target state="translated">UTA071: [AssemblyFixtureProvider]에서 참조하는 형식 '{0}'의 메서드를 열거하지 못했습니다. {1}</target>
        <note>{0} is the fixture provider type name. {1} is the exception details. {Locked="UTA071"}{Locked="[AssemblyFixtureProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_AssemblyFixtureProviderLoadFailed">
        <source>UTA072: Failed to load [AssemblyFixtureProvider] marker from assembly '{0}'. {1}</source>
        <target state="translated">UTA072: 어셈블리 '{0}'에서 [AssemblyFixtureProvider] 마커를 로드하지 못했습니다. {1}</target>
        <note>{0} is the assembly path. {1} is the exception details. {Locked="UTA072"}{Locked="[AssemblyFixtureProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_AssemblyInitMethodThrows">
        <source>Assembly Initialization method {0}.{1} threw exception. {2}: {3}. Aborting test execution.</source>
        <target state="translated">어셈블리 초기화 메서드 {0}.{1}에서 예외를 throw했습니다. {2}: {3}. 테스트 실행을 중단합니다.</target>
        <note>{0} is the declaring type name. {1} is the assembly initialization method name. {2} is the exception type. {3} is the exception message.</note>
      </trans-unit>
      <trans-unit id="UTA_ClassCleanupMethodWasUnsuccesful">
        <source>Class Cleanup method {0}.{1} failed. Error Message: {2}. Stack Trace: {3}</source>
        <target state="translated">클래스 정리 메서드 {0}.{1}이(가) 실패했습니다. 오류 메시지: {2}. 스택 추적: {3}</target>
        <note>{0} is the declaring type name. {1} is the class cleanup method name. {2} is the error message. {3} is the stack trace.</note>
      </trans-unit>
      <trans-unit id="UTA_ClassInitMethodThrows">
        <source>Class Initialization method {0}.{1} threw exception. {2}: {3}.</source>
        <target state="translated">클래스 초기화 메서드 {0}.{1}에서 예외를 throw했습니다. {2}: {3}</target>
        <note>{0} is the declaring type name. {1} is the class initialization method name. {2} is the exception type. {3} is the exception message.</note>
      </trans-unit>
      <trans-unit id="UTA_ClassOrAssemblyCleanupMethodHasWrongSignature">
        <source>Method {0}.{1} has wrong signature. The method must be static, public, does not return a value and should not take any parameter. Additionally, if you are using async-await in method then return-type must be 'Task' or 'ValueTask'.</source>
        <target state="translated">{0}.{1} 메서드의 서명이 잘못되었습니다. 메서드는 static, public이어야 하고, 값을 반환하거나 매개 변수를 사용할 수 없습니다. 또한 메서드에서 async-await를 사용하는 경우 반환 형식은 'Task' 또는 'ValueTask'여야 합니다.</target>
        <note>{0} is the declaring type name. {1} is the method name. {Locked="static"}{Locked="public"}{Locked="Task"}{Locked="ValueTask"}{Locked="async-await"}</note>
      </trans-unit>
      <trans-unit id="UTA_ClassOrAssemblyInitializeMethodHasWrongSignature">
        <source>Method {0}.{1} has wrong signature. The method must be static, public, does not return a value and should take a single parameter of type TestContext. Additionally, if you are using async-await in method then return-type must be 'Task' or 'ValueTask'.</source>
        <target state="translated">{0}.{1} 메서드의 서명이 잘못되었습니다. 메서드는 static, public이어야 하고, 값을 반환하지 않으며, TestContext 형식의 단일 매개 변수를 사용해야 합니다. 또한 메서드에서 async-await를 사용하는 경우 반환 형식은 'Task' 또는 'ValueTask'여야 합니다.</target>
        <note>{0} is the declaring type name. {1} is the method name. {Locked="static"}{Locked="public"}{Locked="TestContext"}{Locked="Task"}{Locked="ValueTask"}{Locked="async-await"}</note>
      </trans-unit>
      <trans-unit id="UTA_CleanupMethodThrows">
        <source>TestCleanup method {0}.{1} threw exception. {2}.</source>
        <target state="translated">TestCleanup 메서드 {0}.{1}에서 예외가 발생했습니다. {2}.</target>
        <note>{0} is the declaring type name. {1} is the test cleanup method name. {2} is the exception details. {Locked="TestCleanup"}</note>
      </trans-unit>
      <trans-unit id="UTA_CleanupMethodThrowsGeneralError">
        <source>Error calling Test Cleanup method for test class {0}: {1}</source>
        <target state="translated">테스트 클래스 {0}에 대한 테스트 정리 메서드를 호출하는 오류: {1}</target>
        <note>{0} is the test class name. {1} is the exception message.</note>
      </trans-unit>
      <trans-unit id="UTA_DataSourceConfigurationSectionMissing">
        <source>Data source '{0}' cannot be found in the test configuration settings</source>
        <target state="translated">테스트 구성 설정에서 데이터 원본 '{0}'을(를) 찾을 수 없습니다.</target>
        <note>{0} is the data source name.</note>
      </trans-unit>
      <trans-unit id="UTA_EndOfInnerExceptionTrace">
        <source>--- End of inner exception stack trace ---</source>
        <target state="translated">--- 내부 예외 스택 추적의 끝 ---</target>
        <note />
      </trans-unit>
      <trans-unit id="UTA_ErrorDataConnectionFailed">
        <source>The unit test adapter failed to connect to the data source or to read the data. For more information on troubleshooting this error, see "Troubleshooting Data-Driven Unit Tests" (http://go.microsoft.com/fwlink/?LinkId=62412) in the MSDN Library. Error details: {0}</source>
        <target state="translated">단위 테스트 어댑터가 데이터 원본에 연결하거나 데이터를 읽지 못했습니다. 이 오류를 해결하는 방법에 대한 자세한 내용은 MSDN 라이브러리에서 "데이터 기반 단위 테스트 문제 해결"(http://go.microsoft.com/fwlink/?LinkId=62412)을 참조하십시오. 오류 세부 정보: {0}</target>
        <note>{0} is the error details. {Locked="http://go.microsoft.com/fwlink/?LinkId=62412"}{Locked="MSDN"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorGenericValueTaskReturnType">
        <source>UTA007: Method {1} defined in class {0} does not have correct signature. 'ValueTask&lt;T&gt;' is not a valid test method return type; use the non-generic 'ValueTask' instead. Example: public async ValueTask Test.Class1.Test()</source>
        <target state="translated">UTA007: 클래스 {0}에 정의된 메서드 {1}에 올바른 서명이 없습니다. 'ValueTask&lt;T&gt;'는 유효한 테스트 메서드 반환 형식이 아닙니다. 대신 제네릭이 아닌 'ValueTask'를 사용하세요. 예: public async ValueTask Test.Class1.Test()</target>
        <note>{0} is the test class full name. {1} is the test method name. {Locked="UTA007"}{Locked="ValueTask&lt;T&gt;"}{Locked="ValueTask"}{Locked="public async ValueTask Test.Class1.Test()"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorInValidTestContextSignature">
        <source>UTA031: class {0} does not have valid TestContext property. TestContext must be of type TestContext, must be non-static, and must be public. For example: public TestContext TestContext.</source>
        <target state="translated">UTA031: {0} 클래스에 유효한 TestContext 속성이 없습니다. TestContext는 TestContext 유형이어야 하고, non-static, public이어야 합니다. 예: public TestContext TestContext.</target>
        <note>{0} is the test class name. {Locked="UTA031"}{Locked="TestContext"}{Locked="non-static"}{Locked="public"}{Locked="public TestContext TestContext"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorIncorrectTestMethodSignature">
        <source>UTA007: Method {1} defined in class {0} does not have correct signature. Test method marked with the [TestMethod] attribute must be non-static, public, return-type as void  and should not take any parameter. Example: public void Test.Class1.Test(). Additionally, if you are using async-await in test method then return-type must be 'Task' or 'ValueTask'. Example: public async Task Test.Class1.Test2()</source>
        <target state="translated">UTA007: 클래스 {0}에 정의된 메서드 {1}에 올바른 서명이 없습니다. [TestMethod] 특성으로 표시된 테스트 메서드는 non-static, public, return-type이 void여야 하며 매개 변수를 사용하지 않아야 합니다. 예: public void Test.Class1.Test(). 또한 테스트 메서드에서 async-await를 사용하는 경우 반환 형식은 Task 또는 'ValueTask’여야 합니다. 예: public async Task Test.Class1.Test2()</target>
        <note>{0} is the test class full name. {1} is the test method name. {Locked="UTA007"}{Locked="[TestMethod]"}{Locked="non-static"}{Locked="public"}{Locked="void"}{Locked="async-await"}{Locked="Task"}{Locked="public void Test.Class1.Test()"}{Locked="public async Task Test.Class1.Test2()"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorInvalidTimeout">
        <source>UTA054: {0}.{1} has invalid Timeout attribute. The timeout must be an integer value greater than 0.</source>
        <target state="translated">UTA054: {0}.{1}에 잘못된 Timeout 특성이 있습니다. 시간 제한 값은 0보다 큰 정수여야 합니다.</target>
        <note>{0} is the declaring type name. {1} is the method name. {Locked="UTA054"}{Locked="Timeout"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiAssemblyClean">
        <source>UTA014: {0}: Cannot define more than one method with the AssemblyCleanup attribute inside an assembly.</source>
        <target state="translated">UTA014: {0}: 어셈블리 내부에서 AssemblyCleanup 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the declaring type full name. {Locked="UTA014"}{Locked="AssemblyCleanup"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiAssemblyInit">
        <source>UTA013: {0}: Cannot define more than one method with the AssemblyInitialize attribute inside an assembly.</source>
        <target state="translated">UTA013: {0}: 어셈블리 내부에서 AssemblyInitialize 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the declaring type full name. {Locked="UTA013"}{Locked="AssemblyInitialize"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiClassClean">
        <source>UTA026: {0}: Cannot define more than one method with the ClassCleanup attribute inside a class.</source>
        <target state="translated">UTA026: {0}: 클래스 내부에서 ClassCleanup 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the test class full name. {Locked="UTA026"}{Locked="ClassCleanup"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiClassInit">
        <source>UTA025: {0}: Cannot define more than one method with the ClassInitialize attribute inside a class.</source>
        <target state="translated">UTA025: {0}: 클래스 내부에서 ClassInitialize 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the test class full name. {Locked="UTA025"}{Locked="ClassInitialize"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiClean">
        <source>UTA024: {0}: Cannot define more than one method with the TestCleanup attribute.</source>
        <target state="translated">UTA024: {0}: TestCleanup 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the test class full name. {Locked="UTA024"}{Locked="TestCleanup"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorMultiInit">
        <source>UTA018: {0}: Cannot define more than one method with the TestInitialize attribute.</source>
        <target state="translated">UTA018: {0}: TestInitialize 특성을 사용하는 메서드를 여러 개 정의할 수 없습니다.</target>
        <note>{0} is the test class full name. {Locked="UTA018"}{Locked="TestInitialize"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorNonPublicTestClass">
        <source>UTA001: TestClass attribute defined on non-public class {0}</source>
        <target state="translated">UTA001: public이 아닌 클래스 {0}에서 TestClass 특성을 정의했습니다.</target>
        <note>{0} is the test class full name. {Locked="UTA001"}{Locked="TestClass"}</note>
      </trans-unit>
      <trans-unit id="UTA_ErrorTestClassIsGenericNonAbstract">
        <source>TestClass attribute defined on generic non-abstract class {0}</source>
        <target state="translated">일반 비추상 클래스 {0}에 정의된 TestClass 속성</target>
        <note>{0} is the test class full name. {Locked="TestClass"}</note>
      </trans-unit>
      <trans-unit id="UTA_ExecuteThrewException">
        <source>An unhandled exception was thrown by the 'Execute' method. Please report this error to the author of the attribute '{0}'.
{1}</source>
        <target state="translated">'Execute' 메서드에서 처리되지 않은 예외가 발생했습니다. '{0}' 특성의 작성자에게 이 오류를 보고하세요.
{1}</target>
        <note>{0} is the attribute type name. {1} is the exception details. {Locked="Execute"}</note>
      </trans-unit>
      <trans-unit id="UTA_FailedToGetTestMethodException">
        <source>Failed to obtain the exception thrown by test method {0}.{1}.</source>
        <target state="translated">테스트 메서드 {0}.{1}에서 throw한 예외를 가져오지 못했습니다.</target>
        <note>{0} is the declaring type name. {1} is the test method name.</note>
      </trans-unit>
      <trans-unit id="UTA_InitMethodThrows">
        <source>Initialization method {0}.{1} threw exception. {2}.</source>
        <target state="translated">초기화 메서드 {0}.{1}에서 예외를 throw했습니다. {2}.</target>
        <note>{0} is the declaring type name. {1} is the initialization method name. {2} is the exception details.</note>
      </trans-unit>
      <trans-unit id="UTA_InstanceCreationError">
        <source>Unable to create instance of class {0}. Error: {1}.</source>
        <target state="translated">{0} 클래스의 인스턴스를 만들 수 없습니다. 오류: {1}</target>
        <note>{0} is the test class name. {1} is the error message.</note>
      </trans-unit>
      <trans-unit id="UTA_MethodDoesNotExists">
        <source>Method {0}.{1} does not exist.</source>
        <target state="translated">{0}.{1} 메서드가 없습니다.</target>
        <note>{0} is the declaring type name. {1} is the method name.</note>
      </trans-unit>
      <trans-unit id="UTA_MultipleAttributesOnTestClass">
        <source>The test class '{0}' has multiple attributes derived from '{1}' defined on it. Only one such attribute is allowed.</source>
        <target state="translated">테스트 클래스 '{0}'에 '{1}'에서 파생된 여러 특성이 정의되어 있습니다. 이러한 특성은 하나만 허용됩니다.</target>
        <note>{0} is the test class name. {1} is the attribute base type name.</note>
      </trans-unit>
      <trans-unit id="UTA_MultipleAttributesOnTestMethod">
        <source>The test method '{0}.{1}' has multiple attributes derived from '{2}' defined on it. Only one such attribute is allowed.</source>
        <target state="translated">테스트 메서드 '{0}.{1}'에 {2}에서 파생된 여러 특성이 정의되어 있습니다. 이러한 특성은 하나만 허용됩니다.</target>
        <note>{0} is the declaring type name. {1} is the test method name. {2} is the attribute base type name.</note>
      </trans-unit>
      <trans-unit id="UTA_NoTestResult">
        <source>Error in executing test. No result returned by extension. If using extension of TestMethodAttribute then please contact vendor.</source>
        <target state="translated">테스트를 실행하는 중에 오류가 발생했습니다. 확장에서 결과가 반환되지 않았습니다. TestMethodAttribute 확장을 사용하는 경우 공급업체에 문의하세요.</target>
        <note>{Locked="TestMethodAttribute"}</note>
      </trans-unit>
      <trans-unit id="UTA_NoValidConstructor">
        <source>Cannot find a valid constructor for test class '{0}'. Valid constructors are 'public' and either parameterless or with one parameter of type 'TestContext'.</source>
        <target state="translated">테스트 클래스 '{0}'에 대한 유효한 생성자를 찾을 수 없습니다. 유효한 생성자는 'public'이며 매개 변수가 없거나 'TestContext' 유형의 매개 변수가 하나 있습니다.</target>
        <note>{0} is the test class name. {Locked="public"}{Locked="TestContext"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestContextLoadError">
        <source>Unable to find property {0}.TestContext. Error:{1}.</source>
        <target state="translated">{0}.TestContext 속성을 찾을 수 없습니다. 오류: {1}</target>
        <note>{0} is the test class name. {1} is the error message. {Locked="TestContext"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestContextSetError">
        <source>Unable to set TestContext property for the class {0}. Error: {1}.</source>
        <target state="translated">{0} 클래스에 대해 TestContext 속성을 설정할 수 없습니다. 오류: {1}</target>
        <note>{0} is the test class name. {1} is the error message. {Locked="TestContext"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestContextTypeMismatchLoadError">
        <source>The {0}.TestContext has incorrect type.</source>
        <target state="translated">{0}.TestContext의 형식이 잘못되었습니다.</target>
        <note>{0} is the test class name. {Locked="TestContext"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderInstantiationFailed">
        <source>UTA077: Failed to instantiate type '{0}' referenced by [TestFilterProvider]. The type must declare a public parameterless constructor. {1}</source>
        <target state="translated">UTA077: [TestFilterProvider]에서 참조하는 형식 '{0}'을(를) 인스턴스화하지 못했습니다. 형식은 매개 변수 없는 일반 생성자를 선언해야 합니다. {1}</target>
        <note>{0} is the type name. {1} is the exception details. {Locked="UTA077"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderLoadFailed">
        <source>UTA073: Failed to load [TestFilterProvider] marker from assembly '{0}'. {1}</source>
        <target state="translated">UTA073: 어셈블리 '{0}'에서 [TestFilterProvider] 마커를 로드하지 못했습니다. {1}</target>
        <note>{0} is the assembly path. {1} is the exception details. {Locked="UTA073"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderMultipleDeclared">
        <source>UTA079: Assembly '{0}' declares more than one [TestFilterProvider] attribute. At most one is allowed per test assembly; compose multiple filtering strategies inside a single ITestFilter implementation.</source>
        <target state="translated">UTA079: 어셈블리 '{0}'에서 [TestFilterProvider] 특성을 두 개 이상 선언합니다. 테스트 어셈블리당 하나만 허용됩니다. 여러 필터링 전략을 하나의 ITestFilter 구현에 작성하세요.</target>
        <note>{0} is the assembly path. {Locked="UTA079"}{Locked="[TestFilterProvider]"}{Locked="ITestFilter"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderThrew">
        <source>UTA078: The [TestFilterProvider] filter '{0}' threw an exception while evaluating test '{1}'. {2}</source>
        <target state="translated">UTA078: [TestFilterProvider] 필터 '{0}'에서 테스트 '{1}'을(를) 평가하는 동안 예외가 발생했습니다. {2}</target>
        <note>{0} is the filter type name. {1} is the test name. {2} is the exception details. {Locked="UTA078"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderTypeDoesNotImplementInterface">
        <source>UTA076: Type '{0}' referenced by [TestFilterProvider] must implement '{1}'.</source>
        <target state="translated">UTA076: [TestFilterProvider]에서 참조하는 형식 '{0}'은(는) '{1}'을(를) 구현해야 합니다.</target>
        <note>{0} is the type name. {1} is the required interface name. {Locked="UTA076"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderTypeIsGeneric">
        <source>UTA074: Type '{0}' referenced by [TestFilterProvider] must not be generic.</source>
        <target state="translated">UTA074: [TestFilterProvider]에서 참조하는 형식 '{0}'은(는) 제네릭이 아니어야 합니다.</target>
        <note>{0} is the type name. {Locked="UTA074"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestFilterProviderTypeIsNotInstantiable">
        <source>UTA075: Type '{0}' referenced by [TestFilterProvider] must be a concrete class, not an interface or abstract class.</source>
        <target state="translated">UTA075: [TestFilterProvider]에서 참조하는 형식 '{0}'은(는) 인터페이스나 추상 클래스가 아닌 구체적 클래스여야 합니다.</target>
        <note>{0} is the type name. {Locked="UTA075"}{Locked="[TestFilterProvider]"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestInitializeAndCleanupMethodHasWrongSignature">
        <source>Method {0}.{1} has wrong signature. The method must be non-static, public, does not return a value and should not take any parameter. Additionally, if you are using async-await in method then return-type must be 'Task' or 'ValueTask'.</source>
        <target state="translated">{0}.{1} 메서드의 서명이 잘못되었습니다. 메서드는 non-static, public이어야 하고, 값을 반환하거나 매개 변수를 사용할 수 없습니다. 또한 메서드에서 async-await를 사용하는 경우 반환 형식은 'Task' 또는 'ValueTask'여야 합니다.</target>
        <note>{0} is the declaring type name. {1} is the method name. {Locked="non-static"}{Locked="public"}{Locked="Task"}{Locked="ValueTask"}{Locked="async-await"}</note>
      </trans-unit>
      <trans-unit id="UTA_TestMethodThrows">
        <source>Test method {0}.{1} threw exception:
{2}</source>
        <target state="translated">테스트 메서드 {0}.{1}에서 예외를 throw했습니다. 
{2}</target>
        <note>{0} is the declaring type name. {1} is the test method name. {2} is the exception details.</note>
      </trans-unit>
      <trans-unit id="UTA_TypeLoadError">
        <source>Unable to get type {0}. Error: {1}.</source>
        <target state="translated">{0} 형식을 가져올 수 없습니다. 오류: {1}</target>
        <note>{0} is the type name. {1} is the error message.</note>
      </trans-unit>
      <trans-unit id="UTA_UserCodeThrewNullValueException">
        <source>The called code threw an exception that was caught, but the exception value was null</source>
        <target state="translated">호출된 코드에서 확인된 예외가 발생했지만 예외 값이 null입니다.</target>
        <note>{Locked="null"}</note>
      </trans-unit>
      <trans-unit id="UTA_WrongThread">
        <source>{0} For UWP projects, if you are using UI objects in test consider using [UITestMethod] attribute instead of [TestMethod] to execute test in UI thread.</source>
        <target state="translated">{0} UWP 프로젝트의 경우 테스트에서 UI 개체를 사용 중이면 [TestMethod] 대신 [UITestMethod] 특성을 사용하여 UI 스레드에서 테스트를 실행하세요.</target>
        <note>{0} is the original error message. {Locked="UWP"}{Locked="[UITestMethod]"}{Locked="[TestMethod]"}</note>
      </trans-unit>
      <trans-unit id="UTF_FailedToGetExceptionMessage">
        <source>(Failed to get the message for an exception of type {0} due to an exception.)</source>
        <target state="translated">(예외로 인해 {0} 형식의 예외에 대한 메시지를 가져오지 못했습니다.)</target>
        <note>{0} is the exception type name.</note>
      </trans-unit>
      <trans-unit id="VersionMismatchBetweenAdapterAndFramework">
        <source>'MSTest.TestAdapter' and 'MSTest.TestFramework' must have the same version. Found 'MSTest.TestAdapter' version '{0}' and 'MSTest.TestFramework' version '{1}'. Please make sure that the versions of  'MSTest.TestAdapter' and 'MSTest.TestFramework' NuGet packages have the same version.</source>
        <target state="translated">'MSTest.TestAdapter'와 'MSTest.TestFramework'의 버전이 같아야 합니다. 'MSTest.TestAdapter'의 버전은 '{0}'이고, 'MSTest.TestFramework'의 버전은 '{1}'입니다. 'MSTest.TestAdapter'와 'MSTest.TestFramework' NuGet 패키지의 버전이 동일한지 확인하세요.</target>
        <note>{0} is the MSTest.TestAdapter version. {1} is the MSTest.TestFramework version. {Locked="MSTest.TestAdapter"}{Locked="MSTest.TestFramework"}{Locked="NuGet"}</note>
      </trans-unit>
      <trans-unit id="WrongNumberOfObjects">
        <source>Wrong number of objects for permutation. Should be greater than zero.</source>
        <target state="translated">순열의 개체 수가 잘못되었습니다. 개체 수는 0보다 커야 합니다.</target>
        <note></note>
      </trans-unit>
      <trans-unit id="UTA_OutRefParametersNotSupported">
        <source>Warning: Test method '{0}.{1}' has 'out' or 'ref' parameters which are not supported and may be disallowed in a future version of MSTest.</source>
        <target state="translated">경고: 테스트 메서드 '{0}.{1}'에는 지원되지 않으며 이후 버전의 MSTest에서 허용되지 않을 수 있는 'out' 또는 'ref' 매개 변수가 있습니다.</target>
        <note>{0} is the declaring type name. {1} is the test method name. {Locked="out"}{Locked="ref"}{Locked="MSTest"}</note>
      </trans-unit>
    </body>
  </file>
</xliff>