- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Imported Namespaces
- Coded automations
- Trigger-based Attended Automation
- UI Elements
- Selectors
- Object Repository
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- SetupExtensions tool
- Extension for Citrix
- Extension for Microsoft Remote Desktop and Apps
- Excel Add-in
- Troubleshooting
Working with manual test cases
Once you've established a connection with a Test Manager instance and Studio project, you can navigate to the Test Explorer panel. First, you can transform manual tests within the associated project into low-code or coded test cases. Second, you can create coded test cases using our AI features powered by AutopilotTM. If needed, you can review these manual tests in Test Manager by double-clicking on the test case in the Test Explorer panel before automating them.
You can generate fully automated test cases using Generative AI powered by Autopilot.
Before you begin, visit AI-powered test automation best practices to ensure you effectively generate the coded test cases.
- Connect Studio to a Test Manager project.
- Create elements in the Object repository that mirror the UI elements from
the manual tests.
Note: Autopilot uses object repository elements to automate UI elements in test steps. The elements are employed in the APIs as Strings.
To generate the coded test case:
- In the Test Explorer panel, select 1 Manual Test Cases to display the manual test cases that you can convert into automations.
- Right-click a manual test case
and select Generate coded test case with Generative AI.
The result will be a coded test case that uses UiPath APIs to generate the code for automating the entire manual test. The manual steps are displayed as comments at the beginning of the test case.
You can create a coded test case from a manual test, resulting in Studio generating a coded test case named after the manual test.
Prerequisites:
- Connect to Test Manager:
- In the Studio header, click Test Manager.
- Click Test Manager Settings.
- Input the base URL of your Test Manager instance and click Connect.
- Under Default Project, select the project in which you want to work. This project should include the manual tests you wish to work with.
- Open the Test Explorer panel.
- Right-click a manual test case from the list of test cases in your default project.
- Click Create Coded Test
Case.
Result: A new coded test case is automatically created, having the same name as the manual test. This coded test case displays the manual steps as comments.
You can generate a low-code test case from a manual test with the manual steps displayed as Comment activities.
- Connect Studio to a Test Manager project.
- In the Test Explorer panel, select 1 Manual Test Cases to show the manual test cases that you can convert into low-code test cases.
- Right-click a manual test case
and select Create low-code test case.
The result is a low-code test case that places the manual steps as Comment activities within the XAML file.