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

## Package lib

Package: LIB
This package contains all WinRunner libraries for this project.

See
Description

Class Diagram Summary
lib |

Class Summary
AUT_lib | This library contains application-specific routines such as synchronisation with status object or setting up the typical initial state (new order).
FRM_lib | This library contains generic Framework-related functions.
FRM_TBL_lib | This library contains function specially designed fro processing table objects.

## Package lib Description

Package: LIB
This package contains all WinRunner libraries for this project. A library or "compiled module" in WinRunner terminology is a particular kind of test script which contains functions that can be used from other scripts. EMOS Framework technique is based on the extensive use of libraries. For this reason it is important to control the growth of this directory for example by the conventions named below.

### Directory Structure

- FRM with time we expect any project to have plenty of Framework libraries. Their number and size will depend on the complexity of the AUT and on the number of automated tests. We place all such libraries in the FRM subpackage (and its subpackages).
- Other libraries are usually placed right here in LIB package using the naming conventions described below. If you develop a family of related libraries, you may probably want to place them in a subpackage of your choice. Don't forget to give it a short name and to prefix all libraries and functions with that name.

### Naming conventions

- name prefix choose a short uppercase prefix for each library (e.g. "AUT_")
- middle part choose any middle part you want
- name postfix add "_lib" postfix to each library name

Remember 1) WinRunner allows you to load functions with same name (which hide each other) without issuing an error or even a warning. This can cause very strange surprises that may cost you days to debug. The best "medicine" in avoiding naming collisions in WinRunner is by the means of name spaces (i.e. distinct name prefixes). Since WinRunner does not have such a concept built in we must aproach it with the discipline (i.e. naming convention). Our style is to give all public functions in a particular library the same prefix (e.g. ORA_ for Oracle specific functions) and repeat the same prefix in the name of the library itself. This will not only avoid name collisions but will also help you finding out where do the functions "come from" as you read or debug your code.

Remember 2) Neither WinRunner nor TestDirector help you distinguish between main tests and compiled modules (the same icon is shown for both, you have to look in the test properties to find out). Attaching "_lib" or some other naming convenction makes life a bit easier.

### Other conventions

- AUT stands for Application Under Test and we use it often to identify the project-specific libraries/functions. Feel free to invent the better name.

b>Remember 2) Neither WinRunner nor TestDirector help you distinguish between main tests and compiled modules (the same icon is shown for both, you have to look in the test properties to find out). Attaching "_lib" or some other naming convenction makes life a bit easier.

### Other conventions

- AUT stands for Applicatio

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