What is the correct flow from a high level design standpoint in UiPath Test Manager1?

The correct flow from a high level design standpoint in UiPath Test Manager1 is:

Step 1 = Create Project Step 2 = Create Requirement Step 3 = Create TestCase Step 4 = Create TestSet

According to the UiPath documentation and the Test Manager Overview Demo1, the high level design flow in UiPath Test Manager1 involves the following steps:

Create Project: A project is a container for all the testing artifacts related to a specific application or process. You can create a project in Test Manager by giving it a name, a description, and a type (RPA or Application). You can also import a project from another source, such as Jira or Azure DevOps 2.

Create Requirement: A requirement is a statement of what the application or process should do or achieve. You can create a requirement in Test Manager by giving it a name, a description, and a custom attribute. You can also import a requirement from another source, such as Jira or Azure DevOps 2.

Create TestCase: A test case is a set of steps or actions that verify a specific requirement. You can create a test case in Test Manager by giving it a name, a description, a type (manual or automated), and a custom attribute. You can also import a test case from another source, such as Studio or Task Capture 2.

Create TestSet: A test set is a collection of test cases that are executed together as part of a testing cycle. You can create a test set in Test Manager by giving it a name, a description, a type (manual or automated), and a custom attribute. You can also import a test set from another source, such as Orchestrator 2.

References:

2: UiPath Test Manager - UiPath Documentation Portal

3: Task Capture - UiPath Test Manager - UiPath Documentation Portal

1: Test Manager Overview Demo - Test Automation Case | UiPath