UiPath UiPath-TAEPv1 UiPath Test Automation Engineer Professional v1.0 Exam Exam Practice Test

The description can not be edited, but the name and version can be edited in Test Manager.

The name description, or version can not be edited. Any changes need to be made in Orchestrator.

The name can not be edited, but the version and description can be edited in Test Manager.

The version can not be edited, but the name and description can be edited in Test Manager.

0

1

3

4

Execution will not start.

'TestCase123" will execute aqainst the data in test data queue 'TestData" from "FolderB".

Execution will be stuck in Pending state.

'TestCase123" will execute aqainst the data in test data queue 'TestData" from "FolderA".

UiPath Test Manager Connect offers a one-way synchronization of objects and supports a limited number of ALM tools.

UiPath Test Manager is only compatible with ALM solutions for defect management, and the integration is facilitated by an external provider.

UiPath Test Manager is compatible with leading ALM solutions, and the UiPath Test Manager Connect, provided by Planview, ensures bidirectional synchronization for seamless data exchange.

UiPath Test Manager excludes agile planning and requirement management, and the integration is facilitated by UiPath itself.

A test execution container is created without a name, and an empty test result entry, called a test case log. is added for each Test Case.

A test execution container with the same name as the Test Set is created, and for each Test Case, an empty test result entry, called a test case log. is added.

An empty test result, called a Test Case log. is created, but no test execution container is formed.

A Test Case log is created for each executed Test Case, and an empty test result entry is added to an unnamed test execution container.

Manual and semi-automated: invoked in Studio.

Manual and Automated; invoked in Test Manager only.

Manual and Scripted; invoked in Orchestrator only

Manual andAutomated; invoked in Test Manager and Orchestrator.

By checking the Run tab under Robot Executor.

By opening the Activity Coverage panel and double-clicking the test case.

By checking the Output tab in UiPath Studio.

By opening the Descriptor Coverage panel and double-clicking the test case.

The latest project version starting with 1.0. will be used.

A validation error will be displayed after clicking on the Next button.

The first project version starting with 1.0. will be used.

Any project version starting with 1.0. will be used.

Use the Attach Document activity and set its AttachmentType property to Screenshot.

Surround the Verity activity in a Try Catch and use a Take Screenshot activity in the Catch block.

Use a Take Screenshot activity and set its AttachToExecution property to True.

Use one of the Verify activities and set its TakeScreenshotlfFailed property to True.

On the parent test cases in the Test Results panel.

On the individual test case data variations in the Test Results panel.

In the Test Manager configuration.

In the Assertions tab of the corresponding test case result.

Job, Run, Deploy, Delete, Analyze.

Asset Job, Package, Test, Help, Version.

Analyze, Delete, Deploy, Pack.

Run, Test, Deploy, Pack, Help, Version.

Random String

Random Text

Random Range

Random Value

A Test Data File isuseful when application testing requires working with large data sets to verify workflow execution and cover edge cases.

A Test Data File should only be used when there is a need to perform tests using multiple argument types for a decision tree.

A Test Data File is used only when there is a needto perform runtime data fetchingfrom the first entry in the entity in UiPath Data Service.

A Test Data File is only used when there is a needto execute test cases containingdata variations from UiPath Data Service in Orchestrator.

Navigate to Testing > Test Cases, select a test run, go to More actions > Details, select a test case, and go to More actions > Re-execute.

Navigate to Testing > Test Executions, select a test run, go to More actions > Details, select a test case, and go to Details > Re-execute.

Navigate to Testing > Test Executions, select a test run. go to More actions > Details, select a test case, and go to View Assertions > Re-execute.

Navigate to Testing > Test Executions, select a test run, go to More actions > Details, select a test case, and go to More actions > Re-execute.

Run on both Windows and Linux devices without any restrictions.

Execute certainpre-defined tasks for RPA package management and testing.

Run only Windows - Legacy projects.

Build Studio projects that are not compatible with Orchestrator.

Assign the Project Owner role via the Assign users/group option in Project Settings.

Assign the Project creator role via Role Assignment in overall UiPath Test Manager settings.

Select the new user via the Ownership tab in Project Settings.

Select the Transfer ownership option for the new user via Manage access in Project Settings.

Only through Orchestrator.

Directly in Orchestrator or through Test manager.

Only through Studio.

Directly in Orchestrator or through Studio.

To sync the mock files with the source workflow files.

To sync the workflows into newly mock files for mock testing.

To copy the workflows into mock files for mock testing.

To sync the mock files into newly created workflow files.

The percentage of manual test cases that are also automated.

The percentage of requirements that have at least one test case out of the total number of requirements.

The percentage of projects in an organization that have at least one test case out of the total number of projects in that organization.

The percentage of projects in a tenant that have at least one test case out of the total number of projects in that tenant.

Only one test case execution can be re-executed at a time.

There is no limitation when re-executing data-driven test case executions.

Multiple data-driven test case executions can be re-executed at once.

Data-driven test case executions cannot be re-executed.

Just Task Capture license

Just Test Manager license.

Studio license and Test Manager license.

Studio license and Orchestrator license.

The total number of selectors in a test case execution.

The number of selectors that have been manually verified.

The number of times a selector has been successfully executed.

The total number of selectors available in the Object Repository.

Test execution in a scheduled manner or build-driven through a CI/CD pipeline.

Integration between UiPath Test Suite and third-party ALM tools.

Reporting and dashboards for test results.

Management of the testing process.

Text and Screenshot

Text and documents

Text and Video recording

Only text

Red

Black

Grey

Green

Only users who originally created the artifact in the ALM system.

Anyone with access to the project.

Any user that has a valid Test Manager License.

Only users that are specifically designated by the admin.

View, Duplicate, Delete

View, Clone, Delete

Edit, Duplicate, Delete

Edit, Clone, Delete

Citizen Developer

RPA Developer

Testing

NonProduction

A log with all the previous executions is kept.

A log with only the previous execution is kept.

New test execution results are generated, independent from the previous ones.

The old execution results are deleted and replaced with the new results.

10 Test Manager Projects

50 Test Manager

100 Test Manager Projects

Unlimited Test Manager Projects

An application testing works with large data sets to verify workflow execution and covers corer cases.

An application testing creates test cases that verify RPA workflow outputs.

An application testing executes an RPA process and verifies the results.

An application testing invokes different test frameworks and retrieves the results.

Set the property ContinueOnFailure of the first Verify activity to False.

Use a Stop Job activity after each verification.

Set the property ContinueOnFailure of the Verify activities to False.

Use a Terminate Workflow activity after each verification.