Dear Ranorex Board,
first of all, sorry for my bad English!
We have a core software with multiple manifestations (customer versions).
Now we are thinking about a refactoring.
We have one Solution with a main project, which holds functions in a Collections directory. In these functions we have different cases for each customer. We create Modules which use the functions of the Collections.
And we have a project just for our datapool (input for the different customers and global parameters).
The modules are structured by test suites and we let them run remotely.
I would appreciate it very much to get some tips and tricks or a best practice architecture.
Please let us know, which steps should we go to get best maintainable, manageable and fast code?
Kind Regards,
Adrian
Best Practice to structure my Ranorex Project
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: Best Practice to structure my Ranorex Project
Hi!
Please contact us via the links below and we will be more than happy to further assist you with this!
Ranorex Team
Please contact us via the links below and we will be more than happy to further assist you with this!
- Existing Customer: https://www.ranorex.com/support-query
- Evaluation Customer: https://www.ranorex.com/prices/contact/
Ranorex Team