Research - scaling the single solution with many projects approach
Posted: Thu Jan 09, 2020 6:32 pm
Hi,
We are about 4 months into our overall automation efforts; we have started the effort using Ranorex. We are considering using the 1 solution / many projects approach instead of mostly separating test suites in their own solution that references an auto framework library. We are using DevOps GIT for our source control and run some test suites using DevOps Pipelines.
Having read through the forums, I see many are using the single solution approach. Seems run configurations are a good way to setup project runs within Studio so that you can test while building the test. Some posted having many or a lot of projects along with a framework lib. I want to get more specifics. I appreciate the help!
1. How many projects have you reasonably managed in a single solution? Was there a project count threshold where it had to be split? In your setup, does each project have only 1 test suite?
2. Do you commit the solution to a single branch in your source control? Do you version your test suites for the various releases of your app? Please elaborate with your setup.
3. Were there any gotchas encountered as your automation effort has grown?
4. If you're using DevOps Pipelines, how are you running a single project from the solution? Can you run 2 projects back to back from a pipeline task?
5. What's your team size?
Thanks!
We are about 4 months into our overall automation efforts; we have started the effort using Ranorex. We are considering using the 1 solution / many projects approach instead of mostly separating test suites in their own solution that references an auto framework library. We are using DevOps GIT for our source control and run some test suites using DevOps Pipelines.
Having read through the forums, I see many are using the single solution approach. Seems run configurations are a good way to setup project runs within Studio so that you can test while building the test. Some posted having many or a lot of projects along with a framework lib. I want to get more specifics. I appreciate the help!
1. How many projects have you reasonably managed in a single solution? Was there a project count threshold where it had to be split? In your setup, does each project have only 1 test suite?
2. Do you commit the solution to a single branch in your source control? Do you version your test suites for the various releases of your app? Please elaborate with your setup.
3. Were there any gotchas encountered as your automation effort has grown?
4. If you're using DevOps Pipelines, how are you running a single project from the solution? Can you run 2 projects back to back from a pipeline task?
5. What's your team size?
Thanks!