Organization and Best Practice : RanorexNet

[slither]

We recently bought Ranorex Pro with the intention of developing our test scripts in VS2008.
Our application is a large Enterprise application. We have a lot of forms (over 100) in it.

We will be creating a Repository for it using RanorexSpy. Once your repository is created, how do you use it?

Would you use the repository items straight into the testcases, or do you abstract it somewhat?

Also, are there other "best practices" that Ranorex users observe in order to create, manage and maintain the testcases and supporting code for larger applications?

I'd be interested to see a full project for a larger application (not just a sample, but a project built for solid test cases), so see how it could be structured and organized.

Maybe the Ranorex team could publish a real life test project, like the one they use to test RanorexStudio?

[Support Team]

Hi,

I see what you mean. And I'm really sorry for not providing you with a best practice example in our documentation. The good news for now: We're currently in the progress of creating an example project describing how to organize recordings, repositories and automation code in the context of testing complex software solutions.

We'll keep you up to date regarding this.

kind regards,

Christoph,
Ranorex Support Team