i have a condition where i need to to test 7 url and sections in them .. i have automated one url and on test manager have created test set too for it… since i have only one repository in azure i need to automate all 7 url in one program … can i run that program where i develop all 7 url and execution results can be seen different test set in test manager ? as in one program and different test set
Hi @Pooja_Kanwar ,
You can try creating multiple test cases in one project. In your UiPath Studio project, 1st create separate test cases for each URL and its corresponding section.
Use descriptive names like Test_URL1_SectionA, Test_URL2_SectionB, …Test_URL7_SectionG.
Then 2nd thing you have to do is :
- Publish the project to Orchestrator with all test cases included.
- Ensure the test cases are visible in Test Manager via Orchestrator integration.
3rd is In Test Manager, create separate test sets for each URL or logical group.
- Assign the relevant test cases to each test set.
- Example: Test Set: URL1 that includes Test_URL1_Section, Test Set: URL2 that includes Test_URL2_SectionB and so on for rest 5…
Lastly, Run Test Sets Independently. You can execute each test set independently from Test Manager or via Azure DevOps pipelines.
Results will be tracked per test set, even though the test cases come from the same project.
Test Manager - Test sets
according to this document - you can reuse test cases across multiple test sets, and test sets are not limited by project boundaries — only by the test cases you assign to them.
Please try them and let me know the results.
All the best!
Hi @Pooja_Kanwar,
Yes, you can automate all 7 URLs in a single program and still reflect the execution results in different Test Sets in Azure Test Manager. Here’s how:
-
Single Automation Flow: Build one project that handles testing of all 7 URLs. Separate each URL test into its own test case or workflow.
-
Associate with Azure Test Cases: In your code, tag each test case with its Azure Test Case ID using
TestCaseAttribute
or custom annotations (depending on the test framework). -
Publish Results to Azure: After execution, use tools like
vstest.console
, Azure DevOps pipelines, or REST APIs to publish results. Ensure the test results are linked to the right Test Case IDs. -
Test Sets Mapping: In Azure Test Manager, assign each Test Case ID to its respective Test Set. This way, even though tests are run together, results are shown under different Test Sets based on Test Case ID.
Outcome: One automation run → multiple test cases → results visible in their own Test Sets.
Let me know if you need any assistance
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.