<?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="pt-BR" 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">A estrutura de teste atual não implementa 'IGracefulStopTestExecutionCapability', que é necessário para o recurso '--maximum-failed-tests'.</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">Extensão usada para dar suporte a '--maximum-failed-tests'. Quando um determinado limite de falhas for atingido, a execução de teste será anulada.</target>
        <note>{Locked="--maximum-failed-tests"}</note>
      </trans-unit>
      <trans-unit id="Aborted">
        <source>Aborted</source>
        <target state="translated">Anulado</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherCommandLineDescription">
        <source>Internal command line for artifact post-processing.</source>
        <target state="translated">Linha de comando interna para pós-processamento de artefato.</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherDescription">
        <source>Dispatches artifact post-processing jobs selected by dotnet test.</source>
        <target state="translated">Executa a expedição de trabalhos de pós-processamento de artefato selecionados pelo 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">Dispatcher de pós-processamento de artefato</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">O artefato processado deve ser um arquivo existente no diretório de saída e não pode substituir um artefato de entrada.</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherManifestNotFound">
        <source>The artifact post-processing manifest does not exist.</source>
        <target state="translated">O manifesto de pós-processamento de artefato não existe.</target>
        <note />
      </trans-unit>
      <trans-unit id="ArtifactPostProcessingDispatcherManifestOptionDescription">
        <source>Path to the artifact post-processing manifest.</source>
        <target state="translated">Caminho para o manifesto de pós-processamento do artefato.</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">Vários pós-processadores de artefato correspondem a ''{0}''. O primeiro processador registrado, ''{1}'', será usado.</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">Falha no pós-processador de artefato ''{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">O dispatcher de pós-processamento de artefato requer um pipe 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">A entrada do manifesto de pós-processamento de artefato {0} não tem um caminho.</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">A propriedade de inputs de manifesto de pós-processamento de artefato deve ser uma matriz.</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">O manifesto de pós-processamento de artefato deve ter schemaVersion 1 e um 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">Não é possível ler o manifesto de pós-processamento de artefato: {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">O pós-processador de artefato ''{0}'' declara a funcionalidade ''{1}'', que não pode conter o separador de ponto e vírgula.</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">O ''{0}'' do pós-processador de artefatos declara a funcionalidade inválida ''{1}''. Os tipos não podem estar em branco, e as extensões de fallback devem estar em minúsculas e começar com um ponto.</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">Cancelamento da sessão de testes...</target>
        <note />
      </trans-unit>
      <trans-unit id="BrowserPlatformNotSupportedOnOlderFrameworks">
        <source>Browser platform is only supported on .NET 7.0 or greater.</source>
        <target state="translated">A plataforma do navegador só tem suporte no .NET 7.0 ou superior.</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">Falha ao criar um filtro de execução de teste</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">Falha ao criar o arquivo de log de diagnóstico ''{0}'' após {1} tentativas. Último erro: {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">Não é possível remover variáveis de ambiente neste estágio</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">A extensão ''{0}'' tentou remover a variável de ambiente ''{1}'', mas foi bloqueada pela extensão '{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">Não é possível definir variáveis de ambiente neste estágio</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">A extensão ''{0}'' tentou definir a variável de ambiente ''{1}'', mas foi bloqueada pela extensão ''{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">Não é possível iniciar o processo ''{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">A opção '--{0}' tem argumentos inválidos: {1}</target>
        <note>{0} is the option name without the leading dashes. {1} is the invalid argument value or validation error.</note>
      </trans-unit>
      <trans-unit id="CommandLineInvalidArityErrorMessage">
        <source>Invalid arity, maximum must be greater than minimum</source>
        <target state="translated">Arity inválido, o máximo deve ser maior que o mínimo</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineInvalidConfiguration">
        <source>Invalid configuration for provider '{0}' (UID: {1}). Error: {2}</source>
        <target state="translated">Configuração inválida para o provedor '{0}' (UID: {1}). Erro: {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">Nome de opção inválido '{0}', ele deve conter apenas letras e '-' (por exemplo, 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">A opção '--{0}' do provedor '{1}' (UID: {2}) espera pelo menos {3} argumentos</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">A opção '--{0}' do provedor '{1}' (UID: {2}) espera no máximo {3} argumentos</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">A opção '--{0}' do provedor '{1}' (UID: {2}) não espera argumentos</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">A opção '--{0}' é declarada por vários provedores: '{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">Você pode corrigir o conflito de opção anterior substituindo o nome da opção usando o arquivo de configuração</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineOptionIsReserved">
        <source>Option '--{0}' is reserved and cannot be used by providers: '{1}'</source>
        <target state="translated">A opção '--{0}' está reservada e não pode ser usada pelos provedores: '{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">A opção '--{0}' do provedor '{1}' (UID: {2}) está usando o prefixo reservado '--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">O ICommandLineOptions ainda não foi criado.</target>
        <note>{Locked="ICommandLineOptions"}</note>
      </trans-unit>
      <trans-unit id="CommandLineParserFailedToReadResponseFile">
        <source>Failed to read response file '{0}'. {1}.</source>
        <target state="translated">Falha ao ler o arquivo de resposta '{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">O arquivo de resposta '{0}' não foi encontrado</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">Aspas não fechada na linha de comando</target>
        <note />
      </trans-unit>
      <trans-unit id="CommandLineParserUnclosedQuoteInResponseFile">
        <source>Unclosed quote in response file at line {0}</source>
        <target state="translated">Aspas não fechada no arquivo de resposta na linha {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">Argumento inesperado {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">Aspas simples inesperadas no argumento: {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">Aspas simples inesperadas no argumento: {0} para a opção '--{1}'</target>
        <note>{0} is the command-line argument containing the unexpected single quote. {1} is the option name without the leading dashes.</note>
      </trans-unit>
      <trans-unit id="CommandLineUnknownOption">
        <source>Unknown option '--{0}'</source>
        <target state="translated">Opção desconhecida '--{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">Linha de comando: {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">Falha ao criar uma instância da extensão composta ''{0}''. Veja a exceção interna para mais detalhes.</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">A fábrica da extensão composta ''{0}'' retornou uma instância nula.</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">A mesma instância de 'CompositeExtensionFactory' já está registrada</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">Um filtro de execução de teste composto não pode conter um filtro filho nulo.</target>
        <note />
      </trans-unit>
      <trans-unit id="CompositeTestExecutionFilterRequiresTwoFilters">
        <source>A composite test execution filter requires at least two child filters.</source>
        <target state="translated">Um filtro de execução de teste composto requer pelo menos dois filtros filho.</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">Não foi possível encontrar o arquivo de configuração '{0}' especificado com '--config-file'.</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">Não foi possível localizar a configuração padrão do json</target>
        <note />
      </trans-unit>
      <trans-unit id="ConnectingToClientHost">
        <source>Connecting to client host '{0}' port '{1}'</source>
        <target state="translated">Conectando-se ao host do cliente “{0}” porta “{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">Cria o filtro de execução de teste correto para o modo console</target>
        <note />
      </trans-unit>
      <trans-unit id="ConsoleTestExecutionFilterFactoryDisplayName">
        <source>Console test execution filter factory</source>
        <target state="translated">Fábrica de filtros de execução de teste de console</target>
        <note />
      </trans-unit>
      <trans-unit id="CouldNotFindDirectoryErrorMessage">
        <source>Could not find directory '{0}'</source>
        <target state="translated">Não foi possível localizar o diretório “{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">Aviso: a variável de ambiente "{0}" foi preterida e será removida em uma versão principal futura. Em vez disso, use "{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">Arquivo de diagnóstico (nível "{0}" com liberação assíncrona): {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">Arquivo de diagnóstico (nível "{0}" com liberação de sincronização): {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">Teste(s) {0} descoberto(s) no assembly</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">Descobrindo testes de</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">O provedor ''{0}'' (UID: {1}) falhou com o erro: {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">Exceção durante o cancelamento da ID da solicitação '{0}'</target>
        <note>{0} is the request id.</note>
      </trans-unit>
      <trans-unit id="ExitCode">
        <source>Exit code</source>
        <target state="translated">Código de saída</target>
        <note />
      </trans-unit>
      <trans-unit id="ExtensionDoesNotImplementGivenInterfaceErrorMessage">
        <source>Extension of type '{0}' is not implementing the required '{1}' interface</source>
        <target state="translated">A extensão do tipo “{0}” não está implementando a interface “{1}” necessária</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">Extensões com o mesmo UID '{0}' já foram registradas. As extensões registradas são dos tipos: {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">Falhou</target>
        <note />
      </trans-unit>
      <trans-unit id="FailedLowercase">
        <source>failed</source>
        <target state="translated">com falha</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">Falha ao gravar o log no canal. Conteúdo de log perdido:
{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">falhou com {0} erros</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">falhou com{0} erros e {1} avisos</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">falhou com {0} aviso(s)</target>
        <note>{0} is the number of warnings.</note>
      </trans-unit>
      <trans-unit id="FinishedTestSession">
        <source>Finished test session.</source>
        <target state="translated">Sessão de teste concluída.</target>
        <note />
      </trans-unit>
      <trans-unit id="FromFile">
        <source>from</source>
        <target state="translated">de</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">Os seguintes provedores ''ITestHostEnvironmentVariableProvider'' rejeitaram a configuração de variáveis de ambiente finais:</target>
        <note>{Locked="ITestHostEnvironmentVariableProvider"}</note>
      </trans-unit>
      <trans-unit id="HelpApplicationUsage">
        <source>Usage {0} [option providers] [extension option providers]</source>
        <target state="translated">Uso {0} [provedores de opções] [provedores de opções de extensão]</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">Execute um aplicativo de teste do .NET.</target>
        <note>{Locked=".NET"}</note>
      </trans-unit>
      <trans-unit id="HelpExtensionOptions">
        <source>Extension options:</source>
        <target state="translated">Opções de extensão:</target>
        <note />
      </trans-unit>
      <trans-unit id="HelpNoExtensionRegistered">
        <source>    No extension registered.</source>
        <target state="translated">    Nenhuma extensão registrada.</target>
        <note />
      </trans-unit>
      <trans-unit id="HelpOptions">
        <source>Options:</source>
        <target state="translated">Opções:</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">O método “{0}” não foi encerrado com êxito</target>
        <note>{0} is the method name.</note>
      </trans-unit>
      <trans-unit id="InvalidCommandLineArguments">
        <source>Invalid command line arguments:</source>
        <target state="translated">Argumentos de linha de comando inválidos:</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">A opção '--{0}' é lida durante a inicialização da plataforma (antes que o arquivo testconfig.json seja carregado) e, portanto, deve ser passada na linha de comando em vez de declarada em 'commandLineOptions' no testconfig.json.</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">A entrada '{0}' na seção '{1}' no arquivo testconfig.json ('{2}') deve ser um valor escalar (cadeia de caracteres, número, booliano) ou uma matriz de valores escalares. Não há suporte para objetos aninhados.</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">No testconfig.json em '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">Uma chave duplicada "{0}"foi encontrada.</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">O elemento JSON de nível superior deve ser um objeto. Em vez disso, "{0}" foi encontrado</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">O token JSON "{0}" sem suporte foi encontrado</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">A entrada '{0}' na seção '{1}' no arquivo testconfig.json ('{2}') deve ser um valor de cadeia de caracteres escalar. Não há suporte para objetos e matrizes aninhados.</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">A seção '{0}' no arquivo testconfig.json ('{1}') deve ser um objeto 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">Implementação do servidor JsonRpc com base na especificação do protocolo da plataforma de teste.</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">Handshake de servidor JsonRpc para cliente, implementação baseada na especificação do protocolo da plataforma de teste.</target>
        <note>{Locked="JsonRpc"}</note>
      </trans-unit>
      <trans-unit id="LoggerFactoryNotReady">
        <source>The ILoggerFactory has not been built yet.</source>
        <target state="translated">O ILoggerFactory ainda não foi criado.</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">A opção '--maximum-failed-tests' deve ser um inteiro positivo. O valor '{0}' é inválido.</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">O barramento de mensagens ainda não foi criado ou não pode mais ser usado nesse estágio.</target>
        <note />
      </trans-unit>
      <trans-unit id="MissingClientPortFoJsonRpc">
        <source>Expected --client-port when jsonRpc protocol is used.</source>
        <target state="translated">Esperado --client-port quando o protocolo jsonRpc é usado.</target>
        <note>{Locked="--client-port"}{Locked="jsonRpc"}</note>
      </trans-unit>
      <trans-unit id="ActiveTestsRunning_MoreTestsCount">
        <source>and {0} more</source>
        <target state="translated">e mais {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} testes em execução</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">O diretório do pipe nomeado '{0}' não existe ou não é gravável: {1}. Defina a variável de ambiente '{2}' para um diretório gravável existente ou remova sua definição para retornar ao diretório temporário padrão.</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">O caminho do pipe nomeado '{0}' tem {1} bytes, o que excede o máximo de {2} bytes permitido para um soquete de domínio Unix. Use um diretório mais curto definindo a variável de ambiente '{3}' ou definindo 'TMPDIR' quando '{3}' não estiver definido.</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">Não disponível</target>
        <note />
      </trans-unit>
      <trans-unit id="NotFound">
        <source>Not found</source>
        <target state="translated">Não encontrado</target>
        <note />
      </trans-unit>
      <trans-unit id="OnlyOneFilterSupported">
        <source>Passing both '--treenode-filter' and '--filter-uid' is unsupported.</source>
        <target state="translated">Não há suporte para a passagem de "--treenode-filter" e "--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">Somente um inicializador de host de teste pode ser registrado.</target>
        <note />
      </trans-unit>
      <trans-unit id="Passed">
        <source>Passed</source>
        <target state="translated">Aprovado</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineClientHostOptionDescription">
        <source>Specify the hostname of the client.</source>
        <target state="translated">Especifique o nome do host do cliente.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineClientPortOptionDescription">
        <source>Specify the port of the client.</source>
        <target state="translated">Especifique a porta do cliente.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineConfigFileOptionDescription">
        <source>Specifies a testconfig.json file.</source>
        <target state="translated">Especifica um arquivo 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">Permite pausar a execução a fim de anexar ao processo para fins de depuração.</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">Forçar o agente de arquivos interno a gravar o log de forma síncrona.
Útil para cenários em que não se deseja perder nenhum registro (ou seja, em caso de falha).
Observe que isso está diminuindo a execução do teste.</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">Habilite o registro de diagnóstico. O nível de log padrão é 'Trace'.
O arquivo será gravado no diretório de saída com o nome 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' espera um argumento de nível único ('Trace', 'Debug', 'Information', 'Warning', 'Error' ou '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}' requer que '--diagnostic' seja fornecido</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">Diretório de saída do log de eventos de diagnóstico 
Se não for especificado, o arquivo será gerado dentro do diretório padrão “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">Prefixo do nome do arquivo de log que substituirá '[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">Defina o nível de detalhamento para o --diagnostic.
Os valores disponíveis são 'Trace', 'Debug', 'Information', 'Warning', 'Error', e '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' recebeu valor inesperado '{0}'. Os valores com suporte são: {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">Listar testes disponíveis.
Opcionalmente, aceita 'text' (a saída legível por humanos padrão) ou 'json' para imprimir os testes descobertos como um documento JSON na saída padrão.</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}'' requer que ''--{1}'' seja especificado.</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' requer '--dotnet-test-pipe' ou '--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' requer uma URL HTTPS absoluta ou uma URL de loopback HTTP, sem informações de usuário, consulta ou fragmento.</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">Especifica o ponto de extremidade HTTP autenticado para o protocolo dotnet test.</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">As opções de ponto de extremidade HTTP e token do dotnet test exigem '--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' requer '--dotnet-test-http-endpoint' e '--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' requer um token de portador válido, não vazio, sem espaços em branco nem caracteres de controle.</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">Especifica o token de portador HTTP por execução para o protocolo dotnet test.</target>
        <note>{Locked="HTTP"}{Locked="dotnet test"}</note>
      </trans-unit>
      <trans-unit id="PlatformCommandLineDotnetTestPipe">
        <source>dotnet test pipe.</source>
        <target state="translated">pipe de 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">Os transportes de pipe nomeado e HTTP do dotnet test não podem ser selecionados juntos.</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' recebeu o valor inesperado '{0}'. Os valores com suporte são: {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">Seleciona o transporte de pré-inicialização para o protocolo de 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 inválido "{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">Não há suporte para a opção '--exit-on-process-exit' em ambientes de navegador.</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">Sair do processo de teste se o processo dependente for encerrado. O PID deve ser fornecido.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineExitOnProcessExitSingleArgument">
        <source>'--{0}' expects a single int PID argument</source>
        <target state="translated">"--{0}" espera um único argumento 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">Fornece uma lista de UIDs de nó de teste para filtrar.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineHelpOptionDescription">
        <source>Show the command line help.</source>
        <target state="translated">Mostrar a ajuda da linha de comando.</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">Exibir informações do aplicativo de teste do .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">Especifica um número máximo de falhas de teste que, quando excedido, anularão a execução de teste.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineMinimumExpectedTestsIncompatibleDiscoverTests">
        <source>'--list-tests' and '--minimum-expected-tests' are incompatible options</source>
        <target state="translated">'--list-tests' e '--minimum-expected-tests' são opções incompatíveis</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">Especifica o número mínimo de testes que devem ser executados.</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' espera um único valor inteiro positivo diferente de zero
(por exemplo, '--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">Não exiba a faixa de inicialização, a mensagem de direitos autorais ou a faixa de telemetria.</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">Não há suporte para o transporte de pipe nomeado de dotnet test no browser-wasm. Use '--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">Não há suporte para o transporte de pipe nomeado de dotnet test no wasi-wasm. Use '--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">Especifique a porta do servidor.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLinePortOptionSingleArgument">
        <source>'--{0}' expects a single valid port as argument</source>
        <target state="translated">'--{0}' espera uma única porta válida como argumento</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">Provedor de linha de comando da Plataforma de Teste da Microsoft</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineProviderDisplayName">
        <source>Platform command line provider</source>
        <target state="translated">Provedor de linha de comando da plataforma</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">O diretório no qual os resultados do teste serão colocados.
Se o diretório especificado não existir, ele será criado.
O padrão é TestResults no diretório que contém o aplicativo de teste.</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'' recebeu o valor inesperado ''{0}''. Os valores com suporte são: {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">Habilite o modo de servidor.</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineSkipBuildersNumberCheckOptionDescription">
        <source>For testing purposes</source>
        <target state="translated">Para fins de teste</target>
        <note />
      </trans-unit>
      <trans-unit id="PlatformCommandLineTestHostControllerPIDOptionDescription">
        <source>Eventual parent test host controller PID.</source>
        <target state="translated">PID do controlador de host de teste pai eventual.</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">A opção 'timeout' deve ter um argumento como valor temporal, com um sufixo de unidade explícito, e um valor numérico positivo dentro do intervalo compatível (até ~49,7 dias). Os sufixos aceitos são 'ms'/'mil(s)'/'millisecond(s)', 's'/'sec(s)'/'second(s)', 'm'/'min(s)'/'minute(s)', 'h'/'hour(s)' e 'd'/'day(s)'. Por exemplo: '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">Um tempo limite global de execução de teste.
Recebe um argumento como valor temporal, com um sufixo de unidade explícito. Os sufixos aceitos são 'ms'/'mil(s)'/'millisecond(s)', 's'/'sec(s)'/'second(s)', 'm'/'min(s)'/'minute(s)', 'h'/'hour(s)' e 'd'/'day(s)'. Por exemplo: '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">Valor inválido "{0}" para "--zero-tests-policy". Os valores válidos são {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">Especifica como uma execução que não executou nenhum teste é tratada.
Os valores válidos são "allow-skipped" (o padrão), que conta os testes ignorados como executados, portanto, apenas uma execução em que nenhum teste foi encontrado falha com o código de saída 8 e "strict", que trata os testes ignorados como não executados, portanto, uma execução em que cada teste foi ignorado (ou nenhum teste foi encontrado) falha com o código de saída 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">Pressione Ctrl+C de novo para forçar a saída.</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">O processo deve ter sido encerrado antes que possamos determinar esse valor</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">A sessão de teste está sendo anulada devido a falhas ('{0}') especificadas pela opção '--maximum-failed-tests'.</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">Falha na repetição após o {0} tempo</target>
        <note>{0} is the retry count.</note>
      </trans-unit>
      <trans-unit id="RunningTestsFrom">
        <source>Running tests from</source>
        <target state="translated">Executando testes de</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerLogMessageDescription">
        <source>This data represents a server log message</source>
        <target state="translated">Esses dados representam uma mensagem de log do servidor</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerLogMessageDisplayName">
        <source>Server log message</source>
        <target state="translated">Mensagem de log do servidor</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestExecutionFilterFactoryDescription">
        <source>Creates the right test execution filter for server mode</source>
        <target state="translated">Cria o filtro de execução de teste correto para o modo servidor</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestExecutionFilterFactoryDisplayName">
        <source>Server test execution filter factory</source>
        <target state="translated">Fábrica de filtros de execução de teste de servidor</target>
        <note />
      </trans-unit>
      <trans-unit id="ServerTestHostDescription">
        <source>The 'ITestHost' implementation used when running server mode.</source>
        <target state="translated">A implementação 'ITestHost' usada ao executar o modo de servidor.</target>
        <note>{Locked="ITestHost"}</note>
      </trans-unit>
      <trans-unit id="ServerTestHostDisplayName">
        <source>Server mode test host</source>
        <target state="translated">Host de teste do modo de servidor</target>
        <note />
      </trans-unit>
      <trans-unit id="ServiceProviderCannotFindServiceErrorMessage">
        <source>Cannot find service of type '{0}'</source>
        <target state="translated">Não é possível localizar o serviço do tipo "{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">A instância do tipo "{0} já está registrada</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">Instâncias do tipo "ITestFramework" não devem ser registradas por meio do provedor de serviços, mas por meio de "ITestApplicationBuilder.RegisterTestFramework"</target>
        <note>{Locked="ITestFramework"}{Locked="ITestApplicationBuilder.RegisterTestFramework"}</note>
      </trans-unit>
      <trans-unit id="ShutdownProgressStillWaitingPrefix">
        <source>Still waiting for: </source>
        <target state="translated">Ainda aguardando: </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">Ignorado</target>
        <note />
      </trans-unit>
      <trans-unit id="SkippedLowercase">
        <source>skipped</source>
        <target state="translated">ignorado</target>
        <note />
      </trans-unit>
      <trans-unit id="StackTrace">
        <source>Stack Trace</source>
        <target state="translated">Rastreamento de Pilha</target>
        <note />
      </trans-unit>
      <trans-unit id="StartingTestSession">
        <source>Starting test session.</source>
        <target state="translated">Iniciando sessão de teste.</target>
        <note />
      </trans-unit>
      <trans-unit id="StartingTestSessionWithLogFilePath">
        <source>Starting test session. The log file path is '{0}'.</source>
        <target state="translated">Iniciando sessão de teste. O caminho do arquivo de log '{0}'.</target>
        <note>{0} is the log file path.</note>
      </trans-unit>
      <trans-unit id="SucceededLowercase">
        <source>succeeded</source>
        <target state="translated">bem-sucedido</target>
        <note />
      </trans-unit>
      <trans-unit id="SyncFlushNotSupportedInBrowserErrorMessage">
        <source>Synchronous flush is not supported in browser environments.</source>
        <target state="translated">Não há suporte para liberação síncrona em ambientes de navegador.</target>
        <note />
      </trans-unit>
      <trans-unit id="TEstExecutionFilterFactoryFactoryAlreadySetErrorMessage">
        <source>An 'ITestExecutionFilterFactory' factory is already set</source>
        <target state="translated">Uma fábrica “ITestExecutionFilterFactory” já está definida</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">Telemetria
---------
A Plataforma de Testes da Microsoft coleta dados de uso para nos ajudar a melhorar sua experiência. Os dados são coletados pela Microsoft e não são compartilhados com ninguém.
Você pode cancelar a telemetria definindo a variável de ambiente TESTINGPLATFORM_TELEMETRY_OPTOUT ou DOTNET_CLI_TELEMETRY_OPTOUT como “1” ou “true” usando seu shell favorito.

Leia mais sobre a telemetria da Plataforma de Testes da 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">O provedor de telemetria já está definido</target>
        <note />
      </trans-unit>
      <trans-unit id="TerminalNoProgressDeprecatedWarning">
        <source>warning: --no-progress is deprecated; use --progress off instead.</source>
        <target state="translated">aviso: --no-progress foi preterido; em vez disso, use --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">Uma fábrica “ITestFrameworkInvoker” já está definida</target>
        <note>{Locked="ITestFrameworkInvoker"}</note>
      </trans-unit>
      <trans-unit id="TestApplicationBuilderApplicationAlreadyRegistered">
        <source>The application has already been built</source>
        <target state="translated">O aplicativo já foi criado</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationBuilderFrameworkAdapterFactoryAlreadyRegisteredErrorMessage">
        <source>The test framework adapter factory has already been registered</source>
        <target state="translated">A fábrica do adaptador de estrutura de teste já foi registrada</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationBuilderTestFrameworkCapabilitiesAlreadyRegistered">
        <source>The test framework capabilities factory has already been registered</source>
        <target state="translated">A fábrica de recursos da estrutura de teste já foi registrada</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">O adaptador da estrutura de teste não foi registrado. Use 'ITestApplicationBuilder.RegisterTestFramework' para registrá-lo</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">Determinar o resultado da execução do aplicativo de teste</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationResultDisplayName">
        <source>Test application result</source>
        <target state="translated">Resultado do aplicativo de teste</target>
        <note />
      </trans-unit>
      <trans-unit id="TestApplicationVSTestModeTooManyBuilders">
        <source>VSTest mode only supports a single TestApplicationBuilder per process</source>
        <target state="translated">O modo VSTest dá suporte apenas a um único TestApplicationBuilder por processo</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">O nome da variável de ambiente '{0}' declarado na seção 'environmentVariables' do arquivo testconfig.json é inválido. Os nomes não devem conter caracteres '=' ou nulos.</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">Nomes de variáveis de ambiente declarados na seção 'environmentVariables' do arquivo testconfig.json não devem estar vazios.</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">Aplica variáveis de ambiente declaradas na seção 'environmentVariables' do arquivo testconfig.json ao processo filho do host de teste.</target>
        <note>{Locked="environmentVariables"}{Locked="testconfig.json"}</note>
      </trans-unit>
      <trans-unit id="TestConfigurationEnvironmentVariableProviderDisplayName">
        <source>testconfig.json environment variables provider</source>
        <target state="translated">Provedor de variáveis de ambiente do 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">Resumo da descoberta de teste: encontrado {0} teste(s) em {1} assemblies.</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">O provedor de filtro de execução de teste "{0}" retornou o tipo de filtro "{1}" para uma solicitação de servidor JSON-RPC. Restrições de provedor não são aplicadas a solicitações de servidor; retornará null quando TestExecutionFilterContext.Origin for Server.</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">O método ''{0}'' não deve ter sido chamado neste objeto proxy</target>
        <note>{0} is the method name.</note>
      </trans-unit>
      <trans-unit id="TestHostAdapterInvokerFailedTestSessionErrorMessage">
        <source>Test adapter test session failure</source>
        <target state="translated">Falha na sessão de teste do adaptador de teste</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">Não há suporte para extensões de controlador de host de teste que exigem reinício do processo em plataformas de navegador/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">O processo de teste do aplicativo não foi encerrado normalmente, o código de saída é ''{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">Falha ao adquirir semáforo antes do tempo limite de '{0}' segundos</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">Falha ao gravar os logs no arquivo de log ''{0}'' antes do tempo limite de ''{1}'' segundos. O arquivo de log pode estar incompleto.</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">Total</target>
        <note />
      </trans-unit>
      <trans-unit id="TreeNodeFilterCannotContainSlashCharacterErrorMessage">
        <source>A filter '{0}' should not contain a '/' character</source>
        <target state="translated">Um filtro “{0}” não deve conter um caractere '/'</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">Usar um filtro de árvore para filtrar os testes a serem executados</target>
        <note />
      </trans-unit>
      <trans-unit id="TreeNodeFilterEscapeCharacterShouldNotBeLastErrorMessage">
        <source>An escape character should not terminate the filter string '{0}'</source>
        <target state="translated">Um caractere de escape não deve encerrar a cadeia de caracteres de filtro “{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">Somente o caminho do filtro final pode conter curinga “**”</target>
        <note>{Locked="**"}</note>
      </trans-unit>
      <trans-unit id="TreeNodeFilterOperatorNotAllowedErrorMessage">
        <source>Unexpected operator '&amp;' or '|' within filter expression '{0}'</source>
        <target state="translated">Operador inesperado “&amp;” ou “|” dentro da expressão de filtro “{0}”</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">Caminho do nó inválido, raiz esperada como primeiro caractere “{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">A expressão de filtro “{0}” contém um número não balanceado de operadores “{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">O filtro contém um operador “/” inesperado dentro de uma expressão entre parênteses</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">O filtro contém um operador '/' inesperado dentro de uma expressão entre parênteses. Filtro: '{0}'. Para combinar alternativas em um único segmento de caminho, use uma sintaxe como '/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">Chamada de telemetria inesperada, a telemetria está desabilitada.</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">Ocorreu uma exceção inesperada no loop de gravação ''FileLogger'' para o arquivo de log ''{0}''. O arquivo de log pode estar incompleto.
{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] exceção sem tratamento: {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">O provedor de filtro de execução de teste "{0}" retornou o tipo de filtro sem suporte "{1}". Os provedores podem retornar apenas NopFilter, TestNodeUidListFilter, TreeNodeFilter ou CompositeTestExecutionFilter And.</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">A solicitação contém o tipo de filtro de execução de teste sem suporte "{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">Há suporte apenas para o operador And do filtro de execução de teste.</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">Não há suporte para o operador de filtro de execução de teste "{0}". Há suporte apenas para 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">Não há suporte para aguardar a anexação do depurador (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1) em ambientes de navegador.</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">Não há suporte no wasi para aguardar a conexão do depurador (TESTINGPLATFORM_WAIT_ATTACH_DEBUGGER=1).</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">Zero testes executados</target>
        <note />
      </trans-unit>
      <trans-unit id="TotalLowercase">
        <source>total</source>
        <target state="translated">total</target>
        <note />
      </trans-unit>
      <trans-unit id="ChatClientProviderAlreadyRegistered">
        <source>A chat client provider has already been registered.</source>
        <target state="translated">Um provedor de cliente de chat já foi registrado.</target>
        <note />
      </trans-unit>
    </body>
  </file>
</xliff>