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

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.

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.

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.

Create one comprehensive test case that covers all scenarios in one execution.

Alter the workflow to ensure a single test case covers all scenarios.

Create separate test cases to cover each scenario during the execution.

Use the same test case, but execute it in different workflows.

1. Open the project in Test Manager

2. Open the Test Requirement tab

3. Open a test case in Test Manager that should be documented

4. Click Document with Task Capture

5. Start capturing the test steps based on the test case description

1. Open the project in Test Manager

2. Open a test case in Test Manager that should be documented

3. Open the Test Requirement tab

4. Open the Manual Steps tab

5. Stat capture the test steps based on the test case description

1. Open the project in Test Manager

2. Open the Test Requirement tab

3. Open the Manual Steps tab

4. Click Document with Task Capture

5. Stat capture the test steps based on the test case description

1. Open the project in Test Manager

2. Open a test case in Test Manager that should be documented

3. Open the Manual Steps tab

4. Click Document with Task Capture

5. Stat capture the test steps based on the test case description

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.

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.

View, Duplicate, Delete

View, Clone, Delete

Edit, Duplicate, Delete

Edit, Clone, Delete

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.

Test case execution is stopped and any subsequent verification is failed.

Test case execution is stopped and an exception is thrown.

Test case execution continues and any subsequent verification is skipped.

Test case execution is stopped and the applications used are closed gracefully.

In the Projects tab, under the namespace of the imported Postman collection.

In the Activities tab, under the namespace that you have set.

In the Debug tab, within the testing activities pack.

In the Activities tab, under the Postman imported libraries list.

Consider applying validation measures which include using extra activities that wait for the desired application state before other interactions.

Use as many hardcoded delays as needed to ensure the application has reached the desired state before proceeding with other interactions.

Validate an application's state by implementing hardcoded delays before proceeding with other interactions.

Avoid waiting for the desired application state and directly proceed with other interactions.

Navigate to the External Connections tab within Admin Settings.

Navigate to the Integrations tab within Admin Settings.

Navigate to the Connection tab within Project Settings.

Navigate to the Integration tab within Project Settings.

It's a data-driven test case with 2 variations, 2 variations were run and 2 not yet run.

It's a data-driven test case with 3 variations, 3 variations were run and 3 not yet run.

It's a data-driven test case with 6 variations, 3 variations were run and 3 not yet run.

It's an automated test case with 8 variations.

Results are tenant-based.

Results are project-based.

Results are session-based.

Results are user-based.

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.

Use the Excel file as a Data Variation Source, instead of iterating through it inside the test case.

Replace the Verify Expression activity with Verify Expression with Operator to benefit from built-in operators.

Surround the SumWorkfiow in a Retry Scope to improve error handling.

Replace the Given-When-Then structure with a custom-built framework.

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.

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.

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.

In the Verification point '_autogenerated_TextString' should be removed.

The ObjectRepository should be changed so all the elements fall into Home screen.

The ApplicationPath should be provided dynamically.

Click 'OK' should be removed.

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.

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.

RPA testing and application testing are the same thing, the term used simply depends on the specific software involved.

RPA testing involves checking the quality of robotic processes, whereas application testing checks the functionality of software applications.

RPA testing checks the functionality of a software application, but application testing evaluates the performance of robots.

RPA testing evaluates human interactions with software, while application testing checks robotic processes.

It counts the total number of licenses available and divides them amongst the Testing robots.

It counts the maximum number of Testing robots that are able to execute tests simultaneously, given by the total number of runtimes allocated to all the online machines.

It counts the individual testing robots on a machine and assigns each of them an equal number of licenses.

It works by allocating a fixed number of licenses per testing robot, regardless of the maximum number that can execute tests simultaneously.

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

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.

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".

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.