We use a common folder on a share drive, then sub folders for gui files,
functions &c. The initialization file holds the references to all of
the folders (const DRIVE = "X:\\", const WR_DIR = DRIVE & "WinRunner\\",
const GUI_FILES = ...) - you get the idea. It makes it easy to add
more items and if we ever need to move to a different drive, it's
trivial. The solution works very cleanly and is very easy to maintain.
Other solutions are possible.
Much the same way as I run Winrunner. The only addition I have is that the
information on where the files are stored are input into the initialization
file from a data table, using ddt..() functions. The main advantage to this
is that the WR environment can be changed without editing WR scripts, which
is useful when not all your test team are WR conversant.
User Richard McCrae (firstname.lastname@example.org) posted:
A useful suggestion. Also, that would allow you significant context shifts without much effort. In fact, you could
have a selection box which indicates which table to load and thereby controls that. I won't change my current
environment, but would consider that approach for the next one.