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

Mobile Device Connection

Mobile Device Manager

Mobile Testing Template

Mobile Automation Activities

There is a need to have all the test cases automated in your test set.

There is a need to have at least one manual test case in a test set.

There are no specific prerequisites to execute automated tests.

There is a need for at least one automated test case in a test set and should be either linked from Orchestrator or created in TestManager with test cases linked from Studio.

Coded automations are primarily used to create structured code with no enhanced productivity, performance improvement, or increased readability.

Coded automations allow to work with low-code automations only, manage basic automation scenarios and developers find it challenging to maintain the code.

Coded automations are used only in complex automation scenarios and they have no role in productivity, performance, hybrid automation or code readability.

Coding can increase productivity, manage complex automation scenarios, work seamlessly with low-code automations, enhance performance, and improve code readability.

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.

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.

Use the "Execute Manually" button.

Click "Set Failed" or "Set Passed" at the end of the test.

Click "Set Failed" or "Set Passed" for each step.

Only automated steps can be marked; manual steps are automatically passed.

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.

• There can be only one mock file for a workflow

• Nested mocks are available

• Mock.json file does not contain configuration settings for mock files

• Changes made in the source workflow file are not applied to the mock file when the project is saved

• There can be multiple mock files for a workflow

• Nested mocks are not available

• Mock.json file contains configuration settings for mock files

• Changes made in the source workflow file are applied to the mock file when the project is saved

• There can be multiple mock files for a workflow

• Nested mocks are available

• Mock.json file contains configuration settings for mock files

• Changes made in the source workflow file are not applied to the mock file when the project is saved

• There can be only one mock file for a workflow

• Nested mocks are not available

• Mock.json file contains configuration settings for mock files

• Changes made in the source workflow file are applied to the mock file when the project is saved

Using "Run" on the specific test case in Test Explorer panel.

Right click on the test case in Project panel + 'Update Test Data' + 'Run File" on the specific test case in Design tab.

Using "Run File' on the specific test case in Design tab.

Using 'Update Test Data' + 'Run' in Test Explorer panel.

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.

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

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.

Test Case Name not unique within the Project

Activity Restrictions

Unused Mocking

Test Case Without Annotations

0

1

3

4

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.

public (int LoanRate) Execute(bool IsLoanApproved)

public int Execute (bool IsLoanApproved)

public bool Execute (bool IsLoanApproved, int loanRate)

public (bool IsLoanApproved) Execute(int LoanRate)

View execution details, View automation rate, and View logs.

View execution details, View assertions, and View logs.

View execution details, View logs, and View requirements.

View execution details, View assertions, and View attachments.

Only through Orchestrator.

Directly in Orchestrator or through Test manager.

Only through Studio.

Directly in Orchestrator or through Studio.

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.

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 test cases within the test set are deleted but the test set remains.

The test set is moved to a recycle bin from where it can be recovered later.

The test set is permanently saved for future reference.

The test sets and any associated test schedules are deleted.

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.

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.

Different project versions were used while publishing the test automation project.

Different test automation project machine hosts were used while publishing.

The Test Case is linked to multiple Test Manager projects.

The Test Case is used in multiple Test Sets.

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.

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.

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.