UiPath-TAEPv1 Sample Questions Answers

0

1

3

4

Test Cases with all of the selected labels are assigned to the Test Set.

Only the manual and automated labels are used to assign Test Cases to the Test Set.

Test Cases with a specified number of the selected labels are assigned to the Test Set.

Test Cases with any of the selected labels are assigned to the Test Set.

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.

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.

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

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.

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 attachment gets skipped.

The file gets automatically compressed.

The user is prompted to manually reduce the file size.

The entire import process is aborted.

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.

10 Test Manager Projects

50 Test Manager

100 Test Manager Projects

Unlimited Test Manager Projects

Go to Tenant > Machines. Click Add Machine and select Cloud Robot - Serverless. Fill in the Name and optionally the Description. Add tags if necessary, but don't configure other settings. Finally, click Save.

Go to Tenant > Robots. Click Add Robot and select Serverless. Fill in the Name and optionally the Description. Add tags if necessary and configure other settings. Finally, click Provision.

Go to Tenant > Robots. Click Add Robot and select Serverless Robot. Fill in the Name and optionally the Description. Add tags if necessary and configure other settings. Finally, click Add Robot.

Go to Tenant > Machines. Click Add Machine and select Cloud Robot - Serverless. Fill in the Name and optionally the Description. Add tags if necessary and configure other settings. Finally, click Provision.

Both at design-time and at run-time.

Never

At run-time.

At design-time.

Execution template, Workflow template, Test case template.

Execution template, Workflow template, Script template.

Execution template, Project template, Custom template.

Test template, Project template, Workflow template.

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.

Random String

Random Text

Random Range

Random Value

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

Rename

Change Default Value

Edit

Delete and Create

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.

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.

Packing Studio projects Deploying NuGet packages to Orchestrator Running jobs in Orchestrator Running Test Sets in Orchestrator

Packing Studio projects Deploying NuGet packages to Orchestrator Running jobs in Orchestrator Creating Orchestrator Queues

Packing Studio projects Deploying NuGet packages to Orchestrator Running jobs in Orchestrator Running Test Sets in Orchestrator Creating Orchestrator Queues

Packing Studio projects Deploying NuGet packages to Orchestrator Setting Triggers in Orchestrator Running Test Sets in Orchestrator

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.

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.

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.

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.

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.

Regression Testing is conducted to validate whether the software application is secure from threats.

Regression Testing is conducted to ensure that changes in the code have not affected existing functionalities.

Regression Testing is conducted to ensure the application's performance under high load conditions.

Regression Testing is conducted to ensure the application's compatibility with different environments.

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.

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.

Only the test cases from Orchestrator.

Test cases from both Orchestrator and Test Manager.

Both manual and automated test cases from multiple Studio projects.

Test cases that have been updated by your user, by specific labels, or the source.

Fetch results into external tools.

Assign test cases to external automations.

Synchronize test sets with external automations.

Create requirements in external tools.