As Alex said, smaller solutions and they are well-organized.Gunner1980 wrote:What benefits do I get if I use this approach?
Just like in the original answer: Just add another Test Suite project. Right click on the solution node in the Project tree view, select "Add -> New Project..." and make sure you select the "Ranorex C#/VB Test Suite" (NOT "Ranorex Test Suite Module Library") that resides in the the "C#" or "VBNet", respectively. That will add another test suite project containing a Ranorex Test Suite file to your solution.xrayspex wrote:I have the same need as the original poster. I need to create a second test suite within a single solution. I have created a second project, but like the original poster I do not see an .rxtst file. How do I make one?
The recommendation "Don't do that" (or "Can't do that") is just for having multiple test suites in one project. In general, the recommendation is not to have everything in one project/test suite, but separate different aspects into separate projects and solutions. That will speed up performance and alleviate team work.xrayspex wrote:It appears the official answer to this is "Don't do that", which is not helpful. I see no obvious way to do this in Studio. Is there a non-obvious way?
We think the majority wants to create a Test Suite Module Library and not a Test Suite Project therefore we structured it in that way.Making the top level C#/VBNet directory the default starting point when searching for a type of project to add might be an enhancement to think about to make this a bit clearer in the future.