- Introdução
- Gerenciamento do projeto
- Documentos
- Trabalhando com análise de impacto de alterações
- Criar casos de teste
- Atribuição de casos de teste a requisitos
- Casos de teste de clonagem
- Exportação de casos de teste
- Vinculação de casos de teste no Studio ao Test Manager
- Delete test cases
- Casos de teste manuais
- Documentar casos de teste com o Task Capture
- Parâmetros
- Habilitação de governança no nível do projeto
- Desabilitação da governança no nível do projeto
- Habilitação de governança no nível do caso de teste
- Como desabilitar a governança no nível do caso de teste
- Gerenciamento de aprovadores para casos de teste controlados
- Gerenciamento de casos de teste governados no estado Em andamento
- Gerenciamento de casos de teste governados no estado Em Revisão
- Gerenciamento de objetos governados no estado Assinado
- Gerenciamento de comentários para casos de teste governados
- Aplicação de filtros e visualizações
- Importando conjuntos de testes do Orchestrator
- Creating test sets
- Adição de casos de teste a um conjunto de testes
- Atribuição de usuários padrão na execução do conjunto de testes
- Habilitando a cobertura de atividade
- Habilitação do Healing Agent
- Configuração de conjuntos de testes para pastas e robôs de execução específicos
- Substituindo parâmetros
- Clonagem de conjuntos de teste
- Exportação de conjuntos de testes
- Aplicação de filtros e visualizações
- Perguntas frequentes - Paridade de funcionalidades - Test Manager versus Orchestrator
- Execução de testes manuais
- Execução de testes automatizados
- Execução de casos de teste sem um conjunto de testes
- Execução de testes mistos
- Criação de execuções pendentes
- Aplicação de uma ordem de execução
- Reexecutando execuções de teste
- Agendamento de execuções
- Solução de problemas de execuções automatizadas
- Testes de acessibilidade para o Test Cloud
- Operações e utilitários do projeto
- Configurações Test Manager
- Integração da ferramentas ALM
- Integração do API
- Codificação de agentes para testes
- Solução de problemas
Test types Test Manager supports across Automation Cloud and Test Cloud, from RPA and application testing to performance, accessibility, and autonomous testing.
Test Manager is the hub for requirements, test cases, test sets, and results, regardless of what kind of testing you're doing. This page gives you an overview of every test type you can run, and points you to where to learn more about each one.
| Test type | What it validates | Mais adequado para |
|---|---|---|
| Teste RPA | UiPath Studio automations and workflow logic | Confirming automations keep working as the underlying workflow changes |
| Teste de Aplicativo | Web, desktop, SAP, and mobile applications, independent of a specific automation | UI, API, data-driven, and cross-platform validation of the systems your automations interact with |
| Teste de desempenho | Automated functional test cases under concurrent virtual users | Load testing and catching performance regressions before they reach production |
| Teste de acessibilidade | Whether your application meets accessibility standards | Compliance checks managed and reported on from within Test Manager |
| Autonomous Test Execution | Pre-written manual test cases, executed unattended by Autopilot | Regression testing, credential-dependent testing, and one-time or ad hoc tests |
| Autonomous Exploration | Undefined application behavior, explored in real time with no pre-written script | Discovery-driven testing: finding unknown issues and edge cases a scripted test wouldn't catch |
Teste RPA
RPA testing validates the automations you build in UiPath Studio, so you can confirm they keep working as expected while the underlying workflow changes. It's built around:
- Data-driven testing — exercising a workflow against varied input using test data files, auto-generated data, Data Service entities, or queues. See Data-driven testing.
- Mock testing — substituting inputs or dependencies during design, so parts of a process can be validated before every dependency is ready. See Mock testing.
- Activity and descriptor coverage — tracking how much of a workflow has actually been exercised by your test cases, and surfacing redundant coverage. See Activity coverage and Descriptor coverage.
- Profile execution — measuring the performance of each module in a test to catch regressions early. See Profile Execution.
Test cases are designed in Studio, published to Orchestrator as packages, then linked to Test Manager for traceability, execution management, and reporting.
Teste de Aplicativo
Application testing validates the systems your automations interact with — web, desktop, SAP, or mobile applications — independent of a specific automation project. It supports both low-code (drag-and-drop) and fully coded test automations.
UI Testing
Built on the UI Automation activities pack and the Object Repository, to interact with and assert against interface elements reliably.
API Testing
Uses the Testing activities pack to validate HTTP/API responses directly, without driving the UI.
Testes baseados em dados
The same data-driven approach used in RPA testing (test data files, auto-generated data, entities, queues) applied to application-level test cases.
Cross-platform and mobile testing
The Mobile Automation activities pack connects to device farms and emulators, so tests can run against real or virtual mobile devices without manual device handling.
Cross-browser testing isn't a distinct feature. It's handled through how UI Automation targets a given browser, not a dedicated cross-browser test grid.
Teste de desempenho
Load-tests your automated functional test cases under concurrent virtual users. You configure load groups, ramp-up times, and thresholds in Test Manager, run a dry run to validate, then execute at scale and monitor results, including dedicated API performance result views. See Performance testing - overview.
Teste de acessibilidade
Evaluates whether your application meets accessibility standards, managed and reported on from within Test Manager. See Accessibility testing for Test Cloud.
Autonomous Test Execution
Runs pre-written manual test cases automatically using Autopilot. A human tester has already written the steps, and Autopilot executes them unattended, replacing the effort of converting a manual test into a fully scripted Studio automation. It's scoped to web-based test cases, and supports:
- Credentials via Orchestrator assets
- A choice of underlying AI models
- Live streaming, remote control, and cancellation of a run in progress
Best suited to:
- Regression testing of stable features
- Credential-dependent testing
- One-time or ad hoc tests
- Testing by business users who don't want to build or maintain scripts
Learn more:
- Autonomous Test Execution for Test Cloud
- Running Autonomous Test Execution
- Reviewing Autonomous Test Execution results
Autonomous Exploration
An agent simultaneously learns about the application, designs tests, and executes them in real time, with no pre-defined test script. Guided by a charter, requirement, or user story, it explores the application like a curious user within a time-boxed session, with optional Human-in-the-Loop controls (pause, guide, skip, resume) and a structured findings report at the end.
Best suited to discovery-driven testing, for example finding unknown issues, edge cases, and unexpected behavior that a scripted test wouldn't catch.
Learn more:
- Autonomous Exploration for Test Cloud
- Running Autonomous Exploration
- Reviewing Autonomous Exploration results