Creating tests and maintaining a repository

Ask general questions here.
Posts: 1
Joined: Tue Jun 23, 2009 4:26 pm

Creating tests and maintaining a repository

Post by revanaken » Tue Jun 23, 2009 4:55 pm

There seems to be a disconnect between the Recorder and the Spy interfaces (both in studio). We use Recorder/Studio to generate large test scripts, but it results in a large disorganized repository. You can create well organized repositories with the Spy/Studio, but I the recorder will not use repository objects created by the Spy. So the two interfaces seem to render each other ineffective.

Is there a “Best Practices” document that describes how to build tests for large software products with many forms?


User avatar
Support Team
Site Admin
Site Admin
Posts: 11734
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Re: Creating tests and maintaining a repository

Post by Support Team » Thu Jun 25, 2009 2:13 pm

The "Best Practises" section in our documentation is currently under development. I recommend to keep the repository as small as you can: One repository for one application (except context menus). Only use globally shared repositories when you need to use those in multiple recordings. Furthermore, keep your recordings simple and clear to ease maintenance. I'm not sure if you're familiar with using the code actions provided by Ranorex Recorder since version 2.1. The Recorder's code actions allow one to create modular and parameter driven recordings as described in our example 'DataDriven Test'. Always try to create automation scripts and recordings as reusable as you can.

We knew that it is currently not really possible to predefine repository objects which should be used during a new Recording automatically, but we're planning to fix this issue in our next minor release (V2.2).

Best regards,

Ranorex Support Team