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

What happens if a Test Execution is re-executed?

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

What can the Clipboard data field be used for in the manual steps of a test case?

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

What actions can be done for test cases that contain data variation?

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

How can manual steps be marked in a Test Case as passed or failed in the Manual Execution Assistant?

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

What is the scope of custom fields in UiPath Test Suite?

• Define custom attributes unique to the project and the set of APIs, test cases, and test sets.
• Define project-specific custom attributes for the requirements, test cases, and test sets.
• Define project-specific custom attributes for the requirements workflows, test sets, and test executions.
• Define project-specific custom attributes for the requirements, test cases, test sets, and reports.

Which are the sub-tasks available under test task in UiPath CLI?

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

If during the importing process in Test Manager, a file attachment exceeds the size limits, what happens to this attachment?

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

What are the two methods for executing tests and where are they invoked??

• Manual and semi-automated: invoked in Studio.
• Manual and Automated; invoked in Test Manager only.
• Manual and Scripted; invoked in Orchestrator only
• Manual and Automated; invoked in Test Manager and Orchestrator.

What happens with the attachment if an Attach Document activity in a workflow is run, as part of an automation job?

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

How can a Serverless Robot be added to an Orchestrator tenant?

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