Test Suite Structure

[ggaspari]

Hi guys,

My test suite works pretty well but i'm just wondering if the project structure is ok or maybe You guys with more experience have some suggestion/idea.
Basically, i have three applications to test ( maybe in future will be more ) so i've created 3 projects ( one for every application!) within my main suite.
Within every project, i've created a "test case modules" folder which contains vb modules with my test cases ( 1 module = 1 test case)
The rxtst file contains 3 folders (one for every application to test) and every folder has associated test cases!

Maybe You can get a picture of the structure from attached screenshot.

[Support Team]

Hi,

There is a Blog where we describe how we think huge projects should be structured.
I hope the blog will show you how to structure large projects.
If you need further clarification do not hesitate to post your questions.

Regards,
Markus
Ranorex Support Team

[ggaspari]

Thanx , the blog looks nice

But, what do You suggest in this situation?
What would be your approach in case you have 3 different project (totally different , so dont have anything in common. ) ?
Create one test suite for each of them and keep them separate? And ,of course, if the answer is yes...why ?

thanx

[Support Team]

Hi,

Create one test suite for each of them and keep them separate?

Yes, we would suggest splitting them into different solutions.
I would use Ranorex Solutions with just one test suite for each of your projects, but you can use more Ranorex Test Suite Module Libraries for your reusable Recordings and UserCode Modules within that Solution.
This would make it easier to maintain and it would allow different tester to work on the same project but on different parts at the same time.
This is quite the same as suggested in our blog .

Regards,
Markus
Ranorex Support Team

[ggaspari]

Yes, now i definitely agree. I think is the best solution
Thanx