Test cases execution from test manager

[Ragul_sharma]

I have created a test set in test manager and uploaded the package to orchestrator. After giving start execution, process started popup raised. But nothing is executed , my test cases are related to desktop application. I have installed using automation developer option. Is there anything to change to execute the test cases like robot configuration or settings change.

[LimaCodes (Lima)]

hey you are trying to test desktop scenarios right?
I’m not sure if I understood it well but you might give it a try to one of these

1. Check Robot Configuration

• Robot Type: Ensure that the Robot associated with the machine where you want to execute the test cases is of the correct type. For test automation, it should be either an Unattended Robot or Testing Robot (if available in your license).
• Robot Environment: Verify that the Robot is correctly connected to Orchestrator and assigned to the environment where the test set is deployed.

2. Test Manager Configuration

• Test Set Configuration: Double-check that the test set in Test Manager is correctly configured with the right test cases and is deployed to the appropriate environment and machine.
• Test Package: Ensure that the correct test package is uploaded to Orchestrator and that it includes all dependencies needed for the desktop application tests.

3. Execution Target

• Machine Configuration: Make sure the machine where the tests are being executed has the necessary applications installed and configured properly. Also, verify that the UiPath Robot service is running.
• Desktop Application: Ensure that the desktop application is accessible and that any required prerequisites are met (e.g., the application is installed, necessary permissions are granted, etc.).

4. Logging and Debugging

• Orchestrator Logs: Check the logs in Orchestrator for any errors or warnings that could indicate why the test cases are not executing. Look for any issues with connecting to the Robot or accessing the desktop application.
• Local Logs: Review the logs on the local machine where the Robot is installed. These logs can often provide more detailed information about what might be going wrong.

5. Robot Configuration Settings

• Interactive Sessions: If the test cases require an interactive session (e.g., desktop interaction), ensure that the Robot is configured to start in an interactive session and that it’s not running in a headless mode.
• User Sessions: Make sure the Robot can start a user session on the machine if needed. Check if the user is logged in, or if a new session needs to be initiated by the Robot.

6. Licensing?

• If the case maybe Test your license: Ensure that your Orchestrator and Robot are properly licensed to execute test cases? A standard Automation Developer license may not include the necessary features for running automated tests from Test Manager.

7. Orchestrator Configuration

• Queue and Triggers: Verify that the process triggers and queues (if used) are correctly configured in Orchestrator.
• Execution User: Ensure that the correct user is assigned for execution in Orchestrator and that this user has the necessary permissions.

8. Update Components

• UiPath Studio & Orchestrator: Make sure you are using compatible versions of UiPath Studio, Orchestrator, and the Test Manager. Outdated components may cause execution issues.