In UiPath Test Manager, the action "Change Default Value" is specifically used to modify the default value of a custom field within an object, such as a requirement, test case, or defect. This helps maintain consistent metadata across projects.

When test sets are linked from Orchestrator to Test Manager, they include only the test cases from Orchestrator. These are typically automated test cases published from Studio and managed through Orchestrator.

Once a Test Set execution starts in UiPath Test Manager, a test execution container with the same name as the Test Set is created. Additionally, for each Test Case in the Test Set, an empty test result entry, called a test case log, is added. This structure helps track the execution results for each individual test case under the overall test set.

The current test case manually iterates through the Excel file using a For Each Row loop. A better practice is to use the Excel file as a Data Variation Source by configuring it as a data-driven test case. This allows Test Suite to automatically generate separate test runs for each row in the file, improving maintainability, visibility of test results, and alignment with Test Suite best practices.

The two methods for executing tests in UiPath are Manual and Automated. These can be invoked from both Test Manager and Orchestrator, depending on whether the execution is user-triggered or scheduled/triggered via CI/CD.

The fastest way to test with updated data from a Test Data Queue is by selecting ‘Update Test Data’ followed by ‘Run’ from the Test Explorer panel. This ensures the latest queue items are pulled and used during execution.

To give the Project Owner role to a different user in UiPath Test Manager, you need to select the Transfer ownership option for the new user via Manage access in Project Settings. This allows the ownership to be transferred to the new user.

A limitation when re-executing data-driven test case executions is that only one test case execution can be re-executed at a time. This is due to the unique data sets tied to each execution, which require individual handling.

In UiPath Test Manager, the ability to re-execute test executions is granted to specific pre-defined user roles, including Test Manager, Test Executor, and Manual Tester. These roles are designed to manage and validate test runs as part of the testing lifecycle.

In the context of UiPath, application testing refers to executing an RPA process and verifying the results to ensure that the application or workflow behaves as expected under various conditions.

To create a Test Data Queue from static test data in UiPath Studio, you need to provide both the Test Data Queue name and the corresponding JSON schema. The schema ensures the structure of the data is defined correctly for the queue items.

The licensing model for Testing runtimes in UiPath is based on the maximum number of Testing robots that can execute tests simultaneously, which is determined by the total number of runtimes allocated to all online machines. This ensures efficient utilization of available resources.

When creating CI/CD pipelines in UiPath, the following activities are in scope:

Packing Studio projects

Deploying NuGet packages to Orchestrator

Running jobs in Orchestrator

Running Test Sets in Orchestrator

These actions enable automated build, test, and deployment of RPA solutions.

In UiPath Test Manager, the Grey color code in the status tab represents a test case that has not yet been executed or does not have a definitive result, but is part of a test set that is currently being executed.

When creating a new test case in UiPath, you can use local templates such as:

Execution template – defines how the test case is executed

Workflow template – provides reusable workflow logic

Test case template – serves as the base structure for new test cases

These templates help standardize and streamline test creation.

The UiPath Test Manager Hub acts as the integration point between UiPath Test Suite and third-party ALM tools (like Jira, Azure DevOps). It enables synchronization of requirements, defects, test results, and assignments, supporting seamless lifecycle management.

Before uploading items to test data queues, it is essential to ensure that the test data queue is created with a corresponding JSON schema. This schema defines the structure of the data to be uploaded, ensuring that the items are correctly formatted and compatible with the test case execution.

The Activity Coverage panel in UiPath Studio shows which activities were executed during a test case run. By double-clicking the test case in this panel, you can review coverage and identify untested or redundant activities.

Test cases are duplicated in Orchestrator when different project versions are used while publishing the test automation project. Each published version of the project includes its own instance of the test case, resulting in multiple entries appearing in Orchestrator.

When an Attach Document activity is run as part of an automation job, the attachment is unavailable. This activity is intended for test case execution contexts where attachments are linked to test results, not regular automation jobs.

To configure a new Jira connection in UiPath Test Manager, you need to navigate to the Integrations tab within Admin Settings. This is where external ALM tools like Jira can be connected and managed centrally.

The Total Coverage KPI in the UiPath Test Manager Dashboard measures the percentage of requirements that have at least one test case linked to them, out of the total number of requirements. It reflects how well the requirements are being tested.

The Run All in View action in the Test Explorer panel executes all test cases currently visible after applying filters or folder selections. This allows users to target specific subsets of test cases without manually selecting each one.

The test data queue items can be uploaded directly in Orchestrator or through Studio. These two platforms allow users to manage and upload test data to the test data queue, enabling integration and execution of data-driven tests.

The Random Value activity enables retrieving random data from a defined set of test data. It can be used to generate random values based on the specified data set, which is useful in data-driven testing scenarios.

Robot authentication settings can be seen and configured in UiPath Orchestrator by navigating to Tenant > Settings, under the Robot security tab. This is where you manage how robots authenticate with Orchestrator.

The "Synchronize mock" action is used to sync the mock files with the source workflow files. This ensures that any changes made to the original workflows are reflected in the associated mock files, maintaining consistency during mock testing.

According to the Workflow Analyzer Settings shown in the image "Unused Mocking" (code TA-DBP-004) has its Default action set to "Warning".

In Coded Workflows within UiPath, both C# and VB.Net can be used as programming languages. These languages provide flexibility for developers to write complex logic that cannot be achieved with the standard UiPath activities.

The Mobile Device Manager is required both at design-time and run-time when working with mobile automation in UiPath. At design-time, it connects Studio to mobile devices for building workflows. At run-time, it enables execution of mobile automation on those devices.