UiPath-TAEPv1 UiPath Test Automation Engineer Professional v1.0 Exam Questions and Answers

Fetch results into external tools.

Assign test cases to external automations.

Synchronize test sets with external automations.

Create requirements in external tools.

public (int LoanRate) Execute(bool IsLoanApproved)

public int Execute (bool IsLoanApproved)

public bool Execute (bool IsLoanApproved, int loanRate)

public (bool IsLoanApproved) Execute(int LoanRate)

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.

0

1

3

4

Storing the login credentials for the application under test.

Capturing the state of the application under test at the time of test case execution.

Saving the output of the test case for future use.

Defining a Clipboard value to avoid manually typing into the input fields.

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.

Navigate to Test Results, open a test result, open a test case log and then select Tasks > Override result.

Select the test case from the Results tab and click on Override result.

Navigate to Test Results, click on Test Manager settings and then select Override test results feature.

Go to Test Results, select a test case and then use the Override tool in the toolbar.

Only the Test Manager can perform re-executions.

The pre-defined user roles that can perform re-executions are: Test Manager, Test Executor and Manual Tester.

Any user with access to the Test Manager can perform re-executions.

Only the Test Executor can perform re-executions.

Update test data, Remove test data, and Modify test data JSON file.

Create test data, Remove test data, and Modify test data JSON file.

Create test data, Update test data, and Remove test data.

Create test data, Update test data, and Modify test data JSON file.

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.

Automated test executions can be performed only in UiPath Orchestrator, while manual executions can only be performed in UiPath Test Manager.

Manual and automated test executions do not have specific distinctions and can be executed interchangeably.

Manual executions require user interaction for each test step, while automated executions are self-running without any manual intervention.

Manual executions are done for test sets created in UiPath Test Manager or linked from Orchestrator with manual steps, while automated executions are invoked through Orchestrator for test cases linked from Studio.

File (Excel and CSV)

Auto Generate

Data Service

Existing data already Stored in the Test Data folder of the project

File (Excel and CSV)

Data Service

Existing data already Stored in the Test Data folder of the project

Test Data Queue

File (Excel and CSV)

Auto Generate

Existing data already Stored in the Test Data folder of the project

Test Data Queue

File (Excel and CSV)

Auto Generate

Data Service

Test Data Queue

It's a set of conditions under which a tester determines if a system under test satisfies requirements and functions correctly.

It's the maximum load that the system can tolerate without crashing.

It's the process of executing the system to reveal bugs.

It's a written document outlining the detailed process of software development.

Job, Run, Deploy, Delete, Analyze.

Asset Job, Package, Test, Help, Version.

Analyze, Delete, Deploy, Pack.

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

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.

The attachments are available only if the workflow is run as part of a job.

The attachment is unavailable.

The attachment is available.

Attachments support only the following type of files: JSON, TXT, XML, PNG and JPEG formats.

To use them as base models for the test cases needed.

To convert them into workflows and publish them for execution.

To be used as a direct replacement for regular test cases.

To store them in a library alongside their respective test data variations.

RunTest block is where the Test Case is executed. The Placeholder activity changes at runtime into an Invoke Workflow File activity.

RunTest block is where the Test Case should be created. The RunTest should contain the actions specific to the Test Case.

RunTest block is where workflows specific to the Test Case should be invoked. If an Application Exception occurs, the current transaction is being retried. If a Business Rule Exception occurs, the block will skip the transaction.

RunTest block is where the Test Case should be invoked. The RunTest should be replaced at design time with an Invoke Workflow activity referencing the Test Case at the execution time. At the execution time, the Test Case will run instead of the RunTest block.

In the Object Repository, under the application LoanResults.

In the LoanResults class that contains a setter for LoanRate.

In the UiAutomation class that contains a setter for LoanRate.

In the Object Repository, under the screen LoanResults.

Convert: converts test results written as CSV to another format.

Run: tests a given package, or runs an existing Test Set on Orchestrator.

Convert: converts test results written in JSON or CSV to another format.

Run: tests a given package, or runs an existing Test Set on Orchestrator.

Convert: converts test results written in JSON to another format.

Run: tests a given package, or runs an existing Test Set on Orchestrator.

Convert: converts test results written in JSON to another format.

Test: tests a given package.

Run: runs an existing Test Set on Orchestrator.

Code reusability should not be a consideration when creating test projects.

Try to reuse workflows as much as possible between projects.

Try to use libraries and object repository, whenever possible.

Try to use the project code base entirely independent of others.

No additional information is necessary.

Only the Test Data Queue name.

Test Data Queue name and JSON schema.

Only the JSON schema.

It is used to encode the data into a format that can be easily read and processed by the UiPath Orchestrator.

It is used to connect UiPath Studio with Orchestrator during test data queue creation.

It usually describes the default values for the queue items.

It formats the data properly to support uploading items to the test data queue.

VB.Net

C#

C# and VB.Net

VBScript

To handle Global Exception Handlers in behaviour driven development approach.

To create test cases based on If-Then-Else containers.

To structure the test around If-Then-Else statements.

To structure the test around Given-When-Then containers.

Red

Black

Grey

Green

Edit the Test Set in UiPath Test Manager and change the value by adding or editing the argument of the Test Case in the Arguments section.

An input argument value ca be changed only at Test Case level in UiPath Test Manager, not at the Test Set level.

Edit the Test Set in UiPath Orchestrator and change the value by adding or editing the argument value of the Test Case in the Arguments section.

An input argument value ca be changed only at Test Case level in UiPath Orchestrator, not at the Test Set level.

It runs tests that are currently in view through all filters.

It runs only failed test cases.

It runs all test cases and workflows.

It runs only selected test cases and workflows.

The Descriptor Coverage panel is only used when there are failed selectors, it has no use during successful test case runs.

The Descriptor Coverage panel is used to store the selectors and Object Repository Ul elements that will be needed for different test cases.

The Descriptor Coverage panel is used for inputting Ul elements for object recognition, that are required to be covered during the execution process.

The Descriptor Coverage panel is used to view Ul elements that have beencovered duringexecutionand to analyze selector coverage or debugworkflows with failed coverage.