UsingTest Data Queue Item in a Test-Autom

Hello UiPath Community,

I am working on a Test Automation Framework in UiPath and would like to integrate the “Get Test Data Queue Item” activity into my framework. I want to understand:

  1. Is it possible to use the “Get Test Data Queue Item” activity within a custom Test Automation Framework?
  2. If so, how can it be implemented effectively in the context of managing test data for automation?

For context, I am using a test queue to manage my test data, and I aim to fetch test data dynamically during the execution of test cases. If there are any best practices or examples of incorporating this activity in a framework, I would greatly appreciate your insights.

Thank you in advance for your guidance!

we have an activity for that, you can see more detail in this documentation Activities - Get Test Data Queue Item

Thank you for pointing out the documentation for the “Get Test Data Queue Item” activity. I am familiar with this activity, but my question is more about the context of configuring and saving the queue name.

Currently, in the framework, I see that we have an Assets.json file that contains only asset-related information. In REFramework, we usually use a configuration file (like Config.xlsx or similar) that stores not just assets but also queue names and other relevant parameters, which are then initialized and used across the workflow.

My question is:

  • Should we extend this Assets.json file to include queue names and other configurations, or is there a best practice for defining and saving queue names in this type of framework?
  • How would you recommend configuring the queue name so that it can be effectively fetched and initialized during the Init state of the framework?

also is there any way to get the id from test date queue items?

To store the test queue name, you can follow these steps: Right-click on your test case, then click on “Add Test Data.” Next, select the “Test Data Queue” option and follow the instructions provided. I haven’t used this method myself, but it might help you if I’m not mistaken.

Thank you for your quick response! Could you share more details about your solution? Is there a Git repository or example project to see how this is implemented?

I have some test data, but it doesn’t include the IDs of individual queue items. Is this normal, or am I missing something?

Also, is it a good idea to link this framework with Test Manager? If we set up a weekly trigger in Orchestrator, will it only run the test cases? How should this be configured?


This will explain how data driven test case works

linking to test manager is not necessary, as it only provides statistics of how your test flow executed and documentation like creating requirement and all
For triggering part, you can create it from your orchestrator folder in Testing tab by creating test schedules

1 Like

Thanks a lot for your time and help! to summarize, I’m working on a project to automate a system for testing. The goal is to run weekly tests for things like logging in, adding customers, and similar workflows. I was thinking about using the Test Manager in cloud for this.

What do you think is the best way to build these processes? Is Test Manager a good option for this? would a test automation framework be also possible for this kind of work?

If you were to build this testing automation, what approach would you take?

Both approaches perform the same task, but Test Manager provides enhanced data visualization for your testing activities. It offers insights such as the time taken to execute tests, reports indicating whether tests passed or failed, and comprehensive documentation for each test case and test set. This helps in monitoring, managing, and analyzing your test processes effectively. We also use Test Manager for our testing processes, making it an essential tool for ensuring quality and efficiency.

Note: If you are satisfied with any solution, please don’t forget to mark it as the solution.

1 Like

Thank you for the explanation!

As I build test cases, I’ve noticed they need an initial state to run individually or as a set in Test Manager. Adding this initialization to every test case feels a bit repetitive. Is there a better way to handle this in a test automation framework?

Also, there’s an asset JSON file in the test automation framework. Would it be okay to add test data queue names to this file? I’d appreciate your thoughts on this!

You can try that i dont have much information of that

1 Like