Hi,
I have to test a web application with over 2000 test cases and several modules.
I will be handling multiple reusable workflows for regression testing, API testing, end-to-end testing, test case verification, module integration testing, mock testing, and database testing. and a lot more.
How should I oversee the UiPath test project’s project structure?
Should I use object repository as one library?
Should I create separate project for API and database testing?
How can I keep all test cases properly in a single project?
While publishing the project, will it take time to upload?
If I change one test case in the future, will I have to publish the entire project?
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Create Test Automation project for Regression test, end-to-end and others
if all testing belongs one single application - 1 project with object Repo and Ui Library will be an efficient way to go
if they are small small component wise testing from different applications - better to just create separate test project and just link them in orchestrator
Project publishing no matter how many times you make change - does not take much time to publish, each time you make change YES - you will have to publish to orchestrator - automatically it will over ride when you publish test case structure changes and dataset whatever you updated.
technically you can reference one workflow in another but practically you would may be want to take 1 simple scenario to that out - as long as the components and dependencies for that particular workflow is in another project - with invoke xml should let you use and create test case.
I was also new about 2 months back and almost learned over breaking and making things. Best is keep API and Database test project totally separate- it might interject and break in automation while running unless you are very experienced and you know and have played out with this before.
