| Documentation produced with EMOS WrDoc and Together® | ||||||||
PREV NEXT | FRAMES NO FRAMES |
Due to its demonstration purpose the environment shown here is simplified in many aspects and overcomplicated in others. The depth of detail however should be sufficient for many real projects. In other words, real projects are not likely to introduce many new concepts but will definitely introduce plenty of similar test scripts (libraries) and data tables.
In addition to aspects of designing test cases (which is the main objective of EMOS Framework) this example also demonstrates an effective technique for documenting WinRunner test environments. This has been achieved with our tool WrDoc and Together® by prcessing formatted comments in the test code.
Note that EMOS Framework requires quite a bit of attention to be understood properly. We usualy teach it through many examples with gradually increasing complexity. In an example such as this one it is almost impossible to organise the concepts in some particularily intuitive way so be prepared to "dig" into details and please make sure to have read the User Manual which explains the basic concepts of EMOS Framework. EMOS Framework user manual is available on our download pages (www.emos.de)
In order to invoke the example do the following:
Scripts/startup
script your startup script and restart WRFlight1a
application and log inScripts/kickoff
script in interactive mode
Pay attention to the directory structure which shows a typical organisation of an
WinRunner project realised with EMOS Framework technique. The clear separtion of
test scripts and test data (Excel tables) is particularily important. We urge you to
investigate the "Data" directory first. EMOS Framework tests are expressed in
data tables. If you want to find out what is being tested, then you should look in tables
such as Data/Tests1/table1.xls
.
Once you are done with data tables you will should find out that EMOS Framework test
scripts are everything but spectacular. In fact EMOS Framework atempts to make them
as boring as possible. For example library LIB/FRM/frm_flight_lib
implements
most of the code that is actually testing something. The rest of the code can be found
in LIB/AUT_lib
and TST/init
. These two scripts are
created in order to demonstate important concepts such as calling arbitrarry functions
and/or main tests from Framework. Make sure to check the data tables to see how
these concepts are actually used (e.g. look for EVAL and CALL directives).
You may discover the naming conventions which are favorised by our team (such as
naming files, functions, GUI objects, etc.). You may prefer a different stype so please
feel free to adopt it to your preferences. The important part is not to abandon them
because such conventions are absolutely critical in bigger projects that involve work
of several people.
Make sure to check the data tables to see how
these concepts are actually used (e.g. look for EVAL and CALL directives).
<
Packages | |
<default> | Package (i.e. directory) "Scripts" contains all WinRunner scripts and GUI-Maps for this project. |
drv |
|
gui | |
lib |
|
lib.frm |
|
| Documentation produced with EMOS WrDoc and Together® | ||||||||
PREV NEXT | FRAMES NO FRAMES |