Test Environment Setup

We start by setting up the test environment. Since we are using WinRunner we are dealing with test scripts that are located on the file system. First we need some

Naming Conventions

The place where Winrunner is installed on a machine (e.g. "c.\programs\ mercury\winrunner") is called



Winrunner Root directory

As mentioned above, EMOS Framework Libraries are located in <M_ROOT>\lib\EMOS_GPL. This directory will be aliased as



Contains EMOS libraries (foundation for EMOS FRM

The first step is to

Create Base Structure

The easiest way to perform this is by unzipping a prepared template. It is located in <EMOS_HOME>\FRM\TPL\tpl.zip. Decide where your automated tests are going to reside. Unzip tpl.zip to that location and you will get a directory named "ProjectX". Rename it to a name suitable to your project. Our convention is to name this directory "WR". We reference this directory <ROOT>.

EMOS FRM distinguisheses between test data and test scripts. We separete them in different directories. So you will find two subdirectories



Contains all test data



Contains all test scripts, results & GUI maps

Ignore "Data" for now. Under the "Scripts" directory you will find



Contains all GUI maps



Contains all libraries (compiled modules)



Contains all test driver scripts

Modify Startup Test

Following the WinRunner standards we are creating the startup test. The purpose of this test is to set up everything that is needed for other scripts. In particular we are:

  1. setting up the search path

  2. load generic libraries (incl. EMOS)

  3. load generic GUI maps

  4. and perform anything necessary to ensure a "clean" start

There is a startup script in <TEST_HOME> which one could/should modify to start with. So do the following:

That's it. Restart WinRunner to verify that your startup script works properly. As you continue you will occasionally come back and modify the startup script to reflect your changes. For now, that's it. You are ready to go.