- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- 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
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- 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
- Creating automated tests
- Executing performance scenarios
- Known limitations for performance testing
- Best practices for performance testing
- Troubleshooting performance testing
- Accessibility testing for Test Cloud
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Consult the list of common errors and debugging failed scenarios.
Selector not found.
Solution: Update UI selectors and validate in Studio.
Package mismatch.
Solution: Upgrade to supported package versions and redeploy.
Robot connection issues.
Solution: Check Orchestrator configuration and credentials.
Debugging failed scenarios.
Solution: Use application logs, drill into HTTP error details, and analyze infrastructure usage charts to isolate root causes.
Troubleshooting Missing PT Metrics (Port 5671 Blocked)
If Performance Testing charts are empty or metrics are missing, it may be caused by a firewall blocking Port 5671, which is required for communication with Azure Event Hub. The UiPath Robot uses this port to send performance metrics to the Performance Testing Service. If the port is blocked, metrics cannot be transmitted.
Context:
- Communication protocol
- Protocol: AMQP (Advanced Message Queuing Protocol)
- Transport: TCP
- Port: 5671
- Encryption
- All communication is secured using TLS 1.2.
- Encryption in transit is enforced by Azure Event Hub.
- Data at rest is encrypted using Microsoft-managed keys UiPath does not apply additional encryption at the application layer.
- Authentication
- Authentication is handled using Shared Access Signature (SAS) tokens.
- Tokens are issued and validated by Azure Event Hub.
- Only authenticated clients can publish messages.
- Endpoint details
- Endpoint format:
*.http://servicebus.windows.net|servicebus.windows.net. - Service: Azure Event Hub (Microsoft Azure managed service).
- Endpoint format:
- Architecture overview
- The Robot sends performance metrics using AMQP over TLS.
- Data is transmitted to Azure Event Hub.
- The Performance Testing service consumes the events.
- Metrics are processed and displayed in dashboards.
Solution:
- Run the following command on the Robot machine using Windows PowerShell.
Test-NetConnection -ComputerName tmh-prod-tmh-eus-ehn.servicebus.windows.net -Port 5671Test-NetConnection -ComputerName tmh-prod-tmh-eus-ehn.servicebus.windows.net -Port 5671 - Interpret the results.
- Port is open (Expected). This means the Robot can successfully communicate with Azure Event Hub.
TcpTestSucceeded : TrueTcpTestSucceeded : True - Port is blocked. This indicates that the firewall is blocking outbound communication on Port 5671.
WARNING: TCP connect to (x.x.x.x : 5671) failedWARNING: TCP connect to (x.x.x.x : 5671) failedTcpTestSucceeded : FalseTcpTestSucceeded : False
- Port is open (Expected). This means the Robot can successfully communicate with Azure Event Hub.
Allow the following outbound connection (firewall rule).
```
ProtocolPortDestinationTCP5671*.http://servicebus.windows.net|servicebus.windows.net
```
```
ProtocolPortDestinationTCP5671*.http://servicebus.windows.net|servicebus.windows.net
```
Additional information:
- If port 5671 is blocked, performance metrics cannot be delivered, resulting in empty charts.
- If connectivity is successful but metrics are still missing, further investigation of Robot logs is required.