PDF UiPath-ADPv1 Study Guide

A mock file is a copy of a workflow file that is used for testing purposes, where some activities are replaced by mock activities that simulate the expected behavior1. A mock file can be created by selecting Mock workflow under test in the Create Test Case window2. The mock file is stored in the Project > Mocks folder, and it has the same name as the original workflow file, with the suffix “_mock” added2. For example, if the original workflow file is named “MySequence.xaml”, the mock file will be named “MySequence_mock.xaml”.

When a mock file is created, the changes made in the original workflow file are automatically applied to the mock file when the project is saved2. This means that any new activities or modifications in the original workflow file are reflected in the mock file, except for the activities that are surrounded by mock activities2. The mock activities are not affected by the changes in the original workflow file, and they can only be edited within the mock file2.

Therefore, if you update “MySequence” and add a Log Message activity and a Verify Expression activity, and then save the project, the changes will be applied to the mock file, assuming that the file is closed. This means that the mock file will also have the Log Message activity and the Verify Expression activity added, unless they are inside a mock activity

The Test Explorer panel in UiPath Studio shows information relevant to test automation, such as test cases, test results, and activity coverage1. You can use the Test Explorer toolbar to filter test results based on result state, and to run or debug test cases using various options1. According to the UiPath documentation12, the available actions in Test Explorer are:

Refresh: Refresh the information shown in the Test Results panel.

Clear execution results: Clear all execution results shown in the Test Explorer Panel.

Run All in View: Run tests that are currently in view through all filters.

Run All: Run all test cases and workflows.

Run Selected: Run only selected test cases and workflows.

Run Failed Test Cases: Run only failed test cases.

Debug Selected: Debug only selected test cases and workflows.

Debug Failed Test Cases: Debug only failed test cases.

Repeat Last Test Run: Run the latest test.

Passed Test Cases: Show only test cases that have passed.

Failed Test Cases: Show only test cases that have failed.

Not Executed Test Cases: Show only test cases that have not been executed.

Filter by Covered/Uncovered Activities: Choose whether to show in the Designer panel the activities that have been covered during the execution.

Filter by Test Cases/Workflows: Choose what to show in the Test Explorer panel.

Search Tests: Use the search function to look for test case names.

As you can see, there is no action called Run Passed Test Cases in Test Explorer, so this is the correct answer to the question.

References:

Studio - Test Explorer - UiPath Documentation Portal

Studio - Test Activities - UiPath Documentation Portal

Studio - Test Explorer - UiPath Documentation Portal

Orchestrator alerts are real-time notifications related to robots, queue items, triggers, and more. Alerts can have one of the following severity levels, which indicate the importance and impact of the events1:

Info - notifies you about low importance events, that do not interrupt the process execution, such as robots becoming available, users being assigned as reviewers, etc.

Success - notifies you about a successful status, such as a job being completed, a queue item being processed, etc.

Warn - notifies you about possible risky events that may interrupt your process execution, but any interruption can be recovered, such as queue items failing with business exceptions, triggers not being able to create new jobs, etc.

Error - notifies you about imminent risky events that prevent the process from executing successfully, such as jobs failing, robots not responding, queue items failing with application exceptions, etc.

Fatal - notifies you about events that force-stop the process execution, such as robots going offline or being disconnected, etc.

Option A is the correct answer, as it lists the five severity levels of Orchestrator alerts as defined in the documentation1. Option B is incorrect, because there is no Critical severity level, but rather Fatal. Option C is incorrect, because there are no Information, Complete, or Failure severity levels, but rather Info, Success, and Fatal. Option D is incorrect, because there are no Completed or Fatal severity levels, but rather Success and Fatal.

References: 1: Alerts Overview