How to structure a solution for a huge company

Ask general questions here.
BS_MR
Posts: 7
Joined: Sun Feb 04, 2018 12:39 pm

How to structure a solution for a huge company

Post by BS_MR » Sun Feb 04, 2018 1:17 pm

Hello, I work in a big company, and we are starting using Ranorex for automatize some manual tests. At the moment, only 2-3 people of the same team are working together testing a module of web ERP Solution. So are starting thinking big(dozens of users designing their hundreds test cases at the same time), but we need advice from more experimented people to face it properly. So I will explain how are we currently working, based on the issues we had and other conflicts we faced with concurrency and git, and then you can give us your advice to improve our procedures.

We are using GIT for version control. And we will execute all the test cases in a virtual machine every day with Jenkins. So we have one big solution, inside this solution we got several projects:

Solution 1
|------------Sandbox project
|------------TestCase1 project
|------------TestCase2 project
|------------TestCase3 project
...

So as you can see, we have a master sandbox project where we execute all test cases and where we try to merge all other projects repositories. Every time we are adding a test case we create a new project in a new branch of git. In this new project, we copy the sandbox repository to reuse previous items tracked. We create records in these projects if we cannot reuse anyone of the sandbox project. Once it is finished, we push it and then merge to the master branch in git. Then the git supervisor, will take all of these records, and copy to the sandbox project, merging the associated repositories. Then he will clean up the project and push the changes in the master. The supervisor will pull the new changes in to the virtual machine. Then others can merge the new changes to their actual branch and keep working with the new changes, or start a new branch with the last changes.

In the other hand, we pretend to use Jenkins to program run the sandbox test suite once a day. That test suite will contain all test cases of other projects, but sometimes we want to execute only some of them. Can we do it directly with Jenkins?

The solution at the moment contains 30 different projects with hundreds of tracked items, and start taking a long tine to build he solution.

So now it's your time, if you have reach this point, thank you for reading all. Are we structuring Ranorex properly? Will you change anything to make the process more efficient? Any suggestions?

Thanks in advance,
Miguel

qwertzu
Posts: 178
Joined: Wed Jan 25, 2017 11:08 am

Re: How to structure a solution for a huge company

Post by qwertzu » Thu Feb 08, 2018 1:56 pm

hi,

This seems to be a very structured and good approach in working with git for avoiding merging conflicts.

regarding your question:
In the other hand, we pretend to use Jenkins to program run the sandbox test suite once a day. That test suite will contain all test cases of other projects, but sometimes we want to execute only some of them. Can we do it directly with Jenkins?
Via command line you can trigger specific test cases from a project.
So in your case, you could run a batch file from Jenkins which contains commands for triggering test cases.
The exact commandline arguments can be found here: https://www.ranorex.com/help/latest/les ... ommandLine

regards, quertzu

BS_MR
Posts: 7
Joined: Sun Feb 04, 2018 12:39 pm

Re: How to structure a solution for a huge company

Post by BS_MR » Mon Feb 12, 2018 8:50 am

Ok, glad to hear it. Thank you qwertzu for your feedback and also for the link.

If anyone wants to add something will be welcome :)