Overview | Package | Class | Use | Tree | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES

## Package drv

Package: DRV
This package contains all EMOS Framework test drivers for this project.

See
Description

Class Diagram Summary
drv |

Class Summary
drv1 | This main test implements a "dummy" step driver which you may use to implement the real one.
drv1_lib | This main test implements a "dummy" step driver which you may use to implement the real one.
emos_test_driver | Calls the FRM_DRV_test_driver() function.
emos_testset_driver | A simple driver for a single test set.
emos_testsuite_driver | This test processes the test suite table.

## Package drv Description

Package: DRV
This package contains all EMOS Framework test drivers for this project. An EMOS Framework test driver is a TSL library that implements a few specific functions (they must have specified names). The purpose of this libraries is to match keywords used in data tables (Excel spreadsheets) with functions that reside in LIB.FRM package.

### Directory Structure

In addition to project-specific test drivers this package contains three special- purpose drivers provided by EMOS Framework which should not be modified or removed.

- emos_testsuite_driver whose only purpose is the interface to standard library EMOS_GPL/FRM/emos_frm_driver_lib that resides in WinRunner lib directory.
- emos_testset_driver whose primary purpose is to link EMOS Framework tests with TestDirector
- emos_test_driver whose only purpose is to avoid yet another WinRunner's "feature"

emos_testsuite_driver is the replacement for EMOS_GPL/FRM/emos_frm_driver script. By placing this script in project directory we assure that all test results are placed in project directory and are not scattered all over the system (this has to deal with some very dark corners of WinRunner's behavior concerning interactive and batch processing).

Therefore a warning to old friends of EMOS Framework: Make sure your kickoff scripts call DRV/emos_testsuite_driver instead of EMOS_GPL/FRM/emos_frm_driver.

### Naming conventions

There are no particular naming conventions other than the recommendation to keep driver names short which in turn makes Excel tables (where these drives are usually called) look a bit more elegant.
NOTE
As of release 7.01.00.04 we recomend the usage of new driver logic. This logic fixes the inherent TSL "feature" that makes it impossible to implement a clean return code strategy for recursive main tests (due to fact that main tests cannot keep variables local to the individual invocation of suc main tests). This has proved to be a signifficant problem with reporting tools such as WrLog which are capable of marking nested tests as "passed" or "failed".
The consequence of the new driver logic is that new test drivers are no more main tests but libraries. For compatibility reasons we now introduce a naming convention so that all new test driver names must end with "_lib".
For example if your old test driver used to be called "main" and you desided to re-implement it with new logic, than you should name the new driver "main_lib". No other modifications anywhere else (in particularily in data tables) are necesary.

### Other conventions

None.
river logic is that new test drivers are no more main tests but libraries. For compatibility reasons we now introduce a naming convention so that all new test driver names must end with "_lib".
For example if your old test driver used to be called "main" and

Overview | Package | Class | Use | Tree | Index | Help
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES