Ranorex Forum

EDIT2 : I got rid of part of the problem (PROB 1, PROB 3 and PROB 4) by manually renaming my folder structure to fit the Solution & Projects (there were some old forum posts that reported success for similar issues) (there were even some folders of deleted projects still standing around) and manually weeding the bin/debug folders for any files that had names like oldProjectnames.* or deletedProjectnames.*.
ToDo: PROB 2

I'm using the trial version 7.1.1 on Win7 64.

My problems: I have created three projects in the same solution, and used one project "ProjA" to build a repository and a trove of Recordings. In that same Project, I made a testcase that worked.
I copied this testcase to the testsuite of another project (same solution).
[PROB 1]: When i run the testcase from ProjB (by pressing the "RUN" -Button in the Testsuite of ProjB) it does the things it would also do in ProjA - building,
showing the licencing nagscreen - then immediately ends the test with a failure report that says

The module 'RecordingA' (with ID {95d6ceba-08e6-46ca-b446-24a4f2ad28fb}) could not be found.

[PROB 2]:
The other problem is that the Testcase in ProjA looks like this:

RecordingA
RecordingB
RecordingC (La\Le\Lu) <- this reflects the folder structure the Recording is in, located in ProjA
RecordingD

The Testcase in ProjB looks like this:
RecordingA (ProjA)
RecordingB (ProjA)
RecordingC (ProjA\La\Le\Lu) <- this reflects the folder structure the Recording is in, located in ProjA
RecordingD (ProjA)

The problem: All recordings are in folder structure la/le or la/le/lu in ProjA, but only Recording C seems to reflect that. The problems may be related.

[PROB 3]: When i delete Recordings A and B from the Testcase in ProjB (so Recording C with its special look is the first) on running it i get another error:

Unexpected exception occurred: Ranorex.RanorexException: There are multiple test suite files in the assembly directory. Please specify the test suite by using command line parameters or rename the test suite file to the current assembly name.
bei Ranorex.Core.Testing.TestSuiteRunner.GetTestSuiteXml(Type containerType, String fileName)
bei Ranorex.Core.Testing.TestSuiteRunner.Run(Type containerType, String cmdLineArgs, String testSuiteXml)
bei Ranorex.Core.Testing.TestSuiteRunner.Run(Type containerType, String cmdLineArgs)
bei TestCasesVictorFlash.Program.Main(String[] args) in c:\Users\manda\Documents\Ranorex\RanorexStudio Projects\ttt\TestCasesVictorFlash\Program.cs:Zeile 39.

Another breadcrumb: In the Management Console a Warning pops up that i do not understand:
[PROB 4]: The referenced project '..\ttt\ProjA.csproj' does not exist.
This warning is given both when i start the testcase in ProjA (which works) and when i start it in ProjB (which does not work, see above)

Any input on this? I did not upload a snapshot as the problem seems to be independent of the tested application.

Thanks!

EDIT: I attached a recreation of the biggest problem (that the recording from ProjA could not be used in ProjB, after copying the containing testcase to Projb)

I have seen that, "There are multiple test suite files in the assembly directory." error when I was invoking my test executableS from the command-line. I had to use the command-line argument "/ts:MyTestSuite.rxtst" to resolve that particular issue. I have multiple .rxtst files in my Ranorex output folder (by design) and running the test executable needed to know which test suite to get its tests from.

Thanks for your answer! I have not graduated to commandline ranorexing yet, but your post strengthened my belief that the filename-level namespaces may be the soft underbelly of this prog - some interventions in that regard solved most of the real problems, the remaining one (see above) is weird but survivable

I think the way you added the modules did not create a reference to project A. If you copy modules from the module browser to your test suite, it will automatically create the reference. If you want to add a reference, please try the following:

In project B right click on References in the solution explorer --> Add --> Add reference --> Projects tab --> Select Project A


Please give this a try and let me know if it works!

Thanks for the tip Vega, but ProjB already had a reference to ProjA (now i have two )
My problem (copy from above):

In the Testsuite-View the Testcase in ProjA looks like this:

RecordingA
RecordingB
RecordingC (La\Le\Lu) <- only this reflects the folder structure the Recording is in, located in ProjA
RecordingD

...and the Testcase in the other project, ProjB, looks like this:

RecordingA (ProjA)
RecordingB (ProjA)
RecordingC (ProjA\La\Le\Lu) <- only this reflects the folder structure the Recording is in, located in ProjA
RecordingD (ProjA)

The problem: Why does only RecordingC get the nice path, while the other recordings only get referenced (correctly) to Proja, but (incorrectly) not specific folders?
The Solution looks like this:

ProjA
.|---La
.....|---Le
...........|---Lu
.................|---RecordingA
.................|---RecordingB
.................|---RecordingC
.................|---RecordingD

ProjB

You have multiple recorded modules named "RecordingC".

Edit*
Edited your example.

You are right, Vaughan.Douglas! I never noticed, because the folders represent different Tabs of the same program, and my naming convention led to the same names, because, well, these are the same controls just on different tabs.

I actually like the form of display (with the full "path" of the module in parentheses behind it) - is there a way to have it for every module? (The obvious hack would be to have one folder full of empty recordings mirroring the names of the real recordings, but that feels rather crass...)

loonquawl wrote:I actually like the form of display (with the full "path" of the module in parentheses behind it) - is there a way to have it for every module? (The obvious hack would be to have one folder full of empty recordings mirroring the names of the real recordings, but that feels rather crass...)

To my knowledge, there is not. However you can always make a suggestion over at UserVoice.

Voiced.