test-manager

latest

false

Getting started
- About Test Manager
  - About Autopilot
  - About Autopilot Chat
    - Prerequisites for Autopilot Chat
    - Functionalities in Autopilot Chat
    - MCP servers and settings
- Getting started
  - Conditions
- Unified Pricing: Licensing Test Manager
- Flex: Licensing Test Manager
- Quickstart guide
Project management
- Documents
- Heatmap
  - Prerequisites
    - Step 1: Installing the UiPath SAP Add-On in your SAP system
    - Step 2: Configuring your SAP system
    - Step 3: Configuring your network components
    - Step 4: Configuring UiPath Test Manager
      - Web service - basic connection
      - Web service - OAuth connection
      - RFC connection
      - CSV file connection
  - Working with Heatmap
- Working with Change Impact Analysis
- Requirements
  - Creating requirements
  - Cloning requirements
  - Exporting requirements
  - Quality-check requirements
  - Generate tests for requirements
  - Finding obsolete tests based on requirements
  - Jira Requirements
  - Applying filters and views
- Test cases
  - Create test cases
  - Assigning test cases to requirements
  - Cloning test cases
  - Exporting test cases
  - Automate test cases
    - Selecting automation
      - Unlinking automation
    - Automating test cases in Studio Web
  - Linking test cases in Studio to Test Manager
  - Delete test cases
  - Manual test cases
  - Importing manual test cases
  - Document test cases with Task Capture
  - Parameters
  - Applying filters and views
- Test sets
  - Importing Orchestrator test sets
  - Creating test sets
  - Adding test cases to a test set
  - Assigning default users in test set execution
  - Enabling activity coverage
  - Enabling Healing Agent
  - Configuring test sets for specific execution folders and robots
  - Overriding parameters
  - Cloning test sets
  - Exporting test sets
  - Applying filters and views
- Executing tests
  - Executing manual tests
  - Executing automated tests
  - Executing test cases without a test set
  - Executing mixed tests
  - Creating pending executions
  - Enforcing an execution order
  - Re-executing test executions
  - Scheduling executions
  - Troubleshooting automated executions
  - FAQ - Feature parity - Test Manager vs Orchestrator
- Performance testing and scenarios for Test Cloud
  - Licensing model for performance testing
    - Performance Testing Virtual Users Bundle
    - Performance testing - usage example
    - Platform Units and infrastructure costs
    - Additional licenses
  - Getting started with performance testing
    - Performance testing - overview
    - Software and system requirements
    - On-premises robot system requirements
  - Creating automated tests
  - Creating performance scenarios
    - Step 1: Complete prerequisites for performance scenarios
    - Step 2: Add performance scenarios
    - Step 3: Add test cases to load groups
    - Step 4: Configure load group settings
  - Executing performance scenarios
  - Analyzing performance results
    - Comparing performance results
    - Interpreting successful results
    - Interpreting failed results
    - Viewing API performance results
  - Known limitations for performance testing
  - Best practices for performance testing
  - Troubleshooting performance testing
- Accessibility testing for Test Cloud
- Test results
  - Analyze test results
  - Deleting test case results
  - Defect synchronization
  - Generate test report
- Autopilot best practices
  - Quality-check requirements
  - Generate tests for requirements
  - Convert text into code
  - Automate manual tests
  - Generate synthetic test data
  - Generate test report
- Searching with Autopilot
Project operations and utilities
- Import project
- Export project
- Export data
- Bulk operations
- Reports
  - Reporting with Insights
  - Test Manager dashboard reports
  - Using external reporting tools
- Migrating Test Manager artifacts to other delivery options
- Testing Data retention policy
Test Manager settings
- Tenant level settings
- User and group access management
- Autopilot search
- Custom fields
- Prompt library
- General project settings
- Automation project configuration
- My notifications
- Customer managed keys encryption
- Audit logs
ALM tool integration
- ALM tool integration
- Test Manager Connect
- Out-of-the-box connectors
  - Outbound IP ranges for connectors
  - SAP Cloud ALM
  - SAP Solution Manager integration
    - Setup and configuration
      - Configuring user machine
      - Configuring SAP Solution Manager
      - Configuring system under test
      - SAP Solution Manager command line
    - Use case scenarios
  - Atlassian Jira
  - Xray for Jira
  - Azure DevOps
  - ServiceNow
  - Webhooks
  - Redmine Integration
API integration
- Test Manager API integration
  - Integrating your tool with Test Manager
  - API Scopes
- Test Manager API
  - Test Manager API
  - API version
  - Test Manager URL
  - API references
  - API rate limits
Troubleshooting
- Troubleshooting Test Manager
- Troubleshooting Autopilot for Testers

Test Manager user guide

DELIVERY:

Last updated Apr 1, 2026

Manual test cases

Add manual steps to define actions that need to be executed sequentially, such as simple user interactions or containing verification operations performed by the testers.

Adding Manual Steps to a Test Case

You can add a maximum number of 250 test steps to a manual test case. To add manual steps to a test case, follow these steps:

Open your project in Test Manager. If you do not have a project yet, see Creating a Project.
In the left navigation panel, go to Test Cases.
Click the test case key to open it.
Go to Manual Steps and click a step to expand the panel.
Configure the following step details:
- Precondition (optional): List the tasks you must execute before the testing starts. This isn't part of the test case workflow, but you have to do these tasks before you start the actual steps.
- Description: Add a short and concise description.
- Expected Behaviour: You can state whether something is expected to happen or to be verified (e.g. VAT is displayed as 32.44).
- Clipboard data: You can define a Clipboard value so you do not have to manually type into the input fields. For a specific use case scenario, see Copying Clipboard Values
  The character limit for the Clipboard data field is 8000 characters.
  .
  Note:
  - Consider adding a single action for each step.
  - To duplicate, delete and reposition the steps, click the vertical ellipsis on a step and choose an action from the dropdown list.
  Figure 1. Adding steps to a manual test case with precondition and postcondition
- Postcondition (optional): Specify the expected state of the application after the test case was executed.
  The postcondition is part of the test case workflow. The manual tester has to confirm whether or not the postcondition has been fulfilled.
Select New test step to add multiple steps to your test case. The steps details are saved automatically.
Tip:
- Analyze test results

Copying clipboard values

When you add steps to a test case, you can enter any string value (e.g. {CLIPBOARD}) in the Clipboard data field.

During , a pop-up window shows the test case execution steps. The string value has been replaced by the Clipboard data value and placed in the Windows Clipboard.

Setting test execution results

When you manually execute a test case, you can set the results as Failed or Passed. For test cases with multiple steps, you can set the result for individual steps by selecting Set Failed, Set Passed, or Set Passed Till Here for all steps. To leave notes, use the Tester comment section.

Debugging

You can debug manual test cases to set the result of each step, by opening a test case and navigating to Tasks > Debug.

On this page

Adding Manual Steps to a Test Case

Was this page helpful?

PREVIOUSDelete test cases

NEXTImporting manual test cases