Best Practice in Folder Structure/Organization

Best practices, code snippets for common functionality, examples, and guidelines.
Posts: 109
Joined: Wed Mar 26, 2014 6:23 pm

Best Practice in Folder Structure/Organization

Post by gilbar16 » Wed Sep 30, 2015 7:04 pm


Any suggestion on Best Practice on how to organize your Ranorex folders/files?

\Generic or Common Functions

What File/Folder Structure do most Ranorex users use?

Also, why is it that when a New Test Solution is created, Ranorex creates two folders named after the Project name by default as in
"c:\Libraries\Documents\Ranorex\RanorexStudio Projects\ProjectName_Test\ProjectName_Test\"?


User avatar
Support Team
Site Admin
Site Admin
Posts: 12145
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: Best Practice in Folder Structure/Organization

Post by Support Team » Fri Oct 09, 2015 9:14 am

Hello Gilbert,

How to organize the folder structure of your project depends very much on your special needs and the scope of your test solution.

If you have for example a lot of modules, it would be a good approach to separate them into different folders.
For example you could create a folder for code modules and another folder for recording modules.
This could be done within the solution explorer directly.
Regarding the path of the project, one 'ProjectName_Test'-folder represents the project and the other one corresponds to the Ranorex solution.

One solution could contain a variety of projects.

I would recommend taking a look at the blog post about how to organize a test automation project with Ranorex.

You do not have the required permissions to view the files attached to this post.