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
The place where Winrunner is installed on a machine (e.g. "c.\programs\ mercury\winrunner") is called
M_ROOT |
|
Winrunner Root directory |
As mentioned above, EMOS Framework Libraries are located in <M_ROOT>\lib\EMOS_GPL. This directory will be aliased as
EMOS_HOME |
<M_ROOT>\lib\EMOS_GPL |
Contains EMOS libraries (foundation for EMOS FRM |
The first step is to
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
DATA_HOME |
<ROOT>\Data |
Contains all test data |
TEST_HOME |
<ROOT>\Scripts |
Contains all test scripts, results & GUI maps |
Ignore "Data" for now. Under the "Scripts" directory you will find
GUI_HOME |
<TEST_HOME>\GUI |
Contains all GUI maps |
LIB_HOME |
<TEST_HOME>\Lib |
Contains all libraries (compiled modules) |
DRV_HOME |
<TEST_HOME>\Drv |
Contains all test driver scripts |
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:
setting up the search path
load generic libraries (incl. EMOS)
load generic GUI maps
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:
open script <TEST_HOME>\startup
make any corrections you find necessary
define <TEST_HOME>\startup as your startup test in Settings\General Options...\Environment.
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.