The ability for a user without an automation developer license to run a test from shared in the orchestrator depends on several factors related to licensing and user permissions within the UiPath ecosystem. Generally, an automation developer license is required for creating, editing, and testing automation workflows. However, running tests from a shared folder in the orchestrator may be possible if the user has been granted specific permissions by an administrator.
In UiPath Orchestrator, roles and permissions can be customized to control what actions a user can perform. For example, an administrator can assign permissions that allow a user to execute certain processes, including tests, without requiring a developer license. This setup might include giving the user access to specific folders or enabling the execution of pre-defined test cases.
However, it’s important to note that while executing a test, users without a developer license may not have access to development features such as debugging or making changes to the automation. They can only execute the test as configured by someone with the appropriate development rights.
Therefore, if a user needs to run tests from the shared section of the orchestrator, it’s essential to check the organization’s licensing setup and ensure that the user’s role has the necessary permissions to execute these tasks. Collaborating with the IT or administrative team responsible for managing UiPath licenses and roles can help clarify any restrictions and enable the desired functionalities.
Hie @Alexandru_Duta
Yes, your understanding is correct. In UiPath, the ability to run tests from a shared folder in Orchestrator does depend on licensing and permissions. Here’s a summary to clarify:
Developer License: Typically required for creating, editing, and debugging automation workflows.
Running Tests Without a Developer License: A user can execute tests if they have been granted specific permissions by an administrator. This means that while a developer license is needed for development and debugging, a user with the right permissions can run tests that have been set up by someone with a developer license.
Permissions in Orchestrator: Roles and permissions in UiPath Orchestrator can be customized. An administrator can configure roles to allow users to run predefined test cases or processes. This configuration ensures that even users without a developer license can execute tests if they have been granted the appropriate permissions.
Restrictions for Non-Developer Users: Users without a developer license will not have access to development features like editing or debugging. They can only run the tests as configured by those with the necessary development rights.
Can someone tell me if this is correct?
And if there is a video material or documentation for this, please?
Therefore, a user without an Automation Developer License can run a test from a shared folder in UiPath Orchestrator, provided they have the correct permissions. Here’s how you can set up this environment:
Setup for Running Tests Without a Developer License
1. Orchestrator Setup
Publish Tests: Developers with the appropriate licenses should publish the automation tests to a shared folder in Orchestrator. This makes the tests accessible to users who have the necessary permissions.
Create Shared Folder: In Orchestrator, create a shared folder that contains the automation tests you want other users to run.
2. Role and Permission Configuration
Define Roles:
In Orchestrator, define roles that allow users to execute tests but restrict them from development activities.
Create a role, such as “Test Runner,” that includes permissions to view and run test sets, start jobs, and access logs.
Assign Permissions:
Assign the “Test Runner” role to users who need to run the tests.
Ensure that these users have access to the shared folder where the tests are located.
Permissions should be set to allow viewing and running tests but should restrict access to editing or publishing workflows.
3. Robot Configuration
Use Attended or Unattended Robots:
Ensure that the users have access to Attended or Unattended Robots, which are configured in Orchestrator.
Attended Robots: These require user intervention to start but can run tests on the user’s machine.
Unattended Robots: These can execute tests without human intervention and are typically scheduled or triggered via Orchestrator.
4. Executing Tests
Access Orchestrator:
Users with the necessary permissions can log in to UiPath Orchestrator.
Select and Run Tests:
Navigate to the shared folder and select the test sets or processes they want to run.
Start the tests using the configured robots.
5. Monitor and Review Results
Monitor Execution:
Use Orchestrator to monitor test execution. Users can check job statuses and view logs to ensure tests run successfully.
Review Test Results:
Users can access test results through Orchestrator to analyze performance and identify any issues.
Summary
Shared Folder: Central repository for test cases, accessible to authorized users.
Roles and Permissions: Use Orchestrator to manage permissions, allowing users to run tests without editing capabilities.
Robots: Attended or Unattended Robots are necessary for test execution.
Orchestrator Management: All operations, from test selection to execution, are managed via Orchestrator.
By following this setup, you can effectively manage and run tests without requiring every user to have a Developer License, ensuring efficient use of resources and maintaining control over the automation environment.
Thank you, but I don’t think this is what I want. I’m not sure what permissions I need to give a user without a UiPath license to run automated tests. Where should I go in Orchestrator, and I’m really not clear on what I should do to have a user without a license run my automated tests.
Yoichi
ashokkarale
jast1631
Anil_G
adiijaiin
Eric_Alvarado
mukeshkala
Daniel_Rabin1
Avala_Parameswara_Reddy
natcmll