Solução de problemas de execuções automatizadas

Problemas comuns com execuções automatizadas de conjuntos de testes no Test Manager, incluindo publicações de pacotes do Orchestrator ausentes e erros de vinculação de casos de teste.

A execução automatizada não pôde começar porque o pacote não foi encontrado no Orchestrator. Apenas casos de teste de pacotes publicados no Orchestrator podem ser executados.

Solução

É preciso publicar o pacote do Studio no Orchestrator. Esse problema ocorre quando um caso de teste é vinculado do Studio para o Test Manager, mas o pacote ainda não foi publicado no Orchestrator.

Casos de teste não podem ser executados porque nenhuma versão executável pôde ser encontrada. Apenas casos de teste publicados com a última versão do pacote no Orchestrator podem ser executados.

Solução

Esse problema ocorre quando os casos de teste em um conjunto de teste não são publicados no pacote mais recente do Studio para o Orchestrator. Você pode obter o mesmo erro quando não nenhum processo/versão é encontrado no Orchestrator para o pacote do Studio.

A execução automatizada não pôde ser iniciada porque nenhum caso de teste automatizado pôde ser encontrado neste conjunto de teste.

Solução

Você precisa ter pelo menos um caso de teste automatizado para usar Executar automatizado. Para obter mais informações, consulte Condições.

Unable to start execution. No executable automated test case found with current package selection on the test set. Please try with a different package selection.

Solução

This error occurs when the test set's execution folder points to a different Orchestrator package feed than the one the test case's automation is linked to. A package published to two different folder feeds is treated as two distinct packages, so Test Manager cannot match them across feeds, even if a copy of the same package exists in the execution folder's feed.

To run test cases whose automations are linked to different feeds within the same test set, publish the relevant packages to a shared feed, such as the tenant-level feed or a dedicated end-to-end (E2E) feed, and link new test cases in Test Manager to the automations published there. For more information, see Selecting automation and Configuring test sets for specific execution folders and robots.

I cannot select test cases from a specific Orchestrator folder in Test Manager.

Solução

Folder visibility in Test Manager mirrors your Orchestrator folder permissions. If you don't have Orchestrator access to a folder, you will not be able to select test cases from that folder in Test Manager either. To make packages visible across multiple folders instead, publish them to a shared tenant-level feed, including the default "Tenant Package Feed" folder, rather than a folder-level feed.

Test Manager shows 0 runtimes available despite an assigned machine template.

Solução

Work through the following checklist:

1. Confirm Testing Runtimes are allocated to the tenant, under Host Tenant > Administration > Licenses.
2. Confirm the machine template has testing runtimes and is assigned to the correct folder.
3. For on-premises deployments, confirm TestAutomation.ModuleEnabled is active in UiPath.Orchestrator.dll.config.
4. Confirm the robot's Assistant is connected to that specific folder's machine template. Runtimes show as unavailable if it isn't, even when the template itself has runtimes assigned.
5. If all of the above check out, allow time for a cache or connection-state refresh before escalating further.

"Run test with Autopilot" fails at "Validating robot connection."

Solução

This is typically a machine or environment setup gap, not a licensing issue. Confirm the following, which mirror the prerequisites for running an automated test case in attended mode:

1. Confirm UiPath Assistant/Robot is installed on the same machine as the browser.
2. Confirm the robot service is running and signed in, connected to the same Orchestrator URL and tenant as the Test Manager service.
3. Confirm the machine and robot are present in the same folder configured in the project's Automation tab.
4. Confirm the UiPath browser extension is enabled.

The test execution is stuck in "Pending" and never starts.

Solução

This can occur for either of the following reasons:

• The machine assigned to the execution folder has only a NonProd robot runtime. NonProd runtimes cannot execute test cases, regardless of the user's roles or permissions. Assign a machine with a runtime type that supports test execution, such as Testing or Prod, and re-run the execution.
• The robot account configured on the machine has an incorrect domain or username. Verify the robot account's credentials in Orchestrator and correct them if needed.

Houve um erro ao executar o conjunto de teste. Tente novamente.

Solução

Se a execução do conjunto de testes falhar por qualquer motivo que não seja o especificado acima, obtenha ajuda dos Serviços de suporte da UiPath.