################################################################################
# TEST:	kickoff
################################################################################
# $Revision: 1.2 $
# $Author: drajovic $
# $Date: 2002/11/28 09:00:43 $
# $Source: d:/Archive/CVS_QS/EMOS/EMOS_FRM_EXAMPLES/FlightDemo/Scripts/kickoff/script,v $
# $NoKeywords: $
################################################################################

#/***
#* This script invokes the tests specified in the associated
#* suite table <code>Data/suite.xls</code>. We call it "kickoff"
#* because all it does is to call the generic test suite driver with a
#* few parameters.
#* <p>
#* By default this suite processes the suite table whose name is hard-coded 
#* in the script (you must read the code to find it out). This is desirable
#* because production suite tables should be kept stable and under 
#* version control (i.e. read-only). Such tables should define 
#* <b>the complete</b> set of tests for the particular test purpose. 
#* <p>
#* However, during development of the test suite or in a 
#* multi-user environment it is often needed to execute only 
#* parts of the whole test suite. One could do this by enbling/disabling 
#* rows in the production suite table. This shall soon prove inconvenient
#* and cumbersome. Moreover, it corrupts the afore mentioned stability of
#* production test suites.
#* <p>
#* A better way to cope with this problem is by creating small 
#* private suite tables and by redirect the kickoff-script to 
#* these tables instead of the default one. 
#* <p>
#* You can do this by allocating the environment variable called
#* <code>MY_SUITE</code> and assiging the appropriate
#* value to it (the name of your suite table relative
#* to the DATA_HOME directory, e.g. "mysuite.xls"). 
#* Remember to remove this variable when you are ready to 
#* execute the default suite. 
#*/

static const SUITE_HDR = "run?,driver,table,testset,description";
static const SUITE_TABLE = "suite.xls"; 

# during development use the following environment variable 
# to redirect the suite to some temporary suite table

static table = getenv("MY_SUITE");

# activates the new driver logic since EMOS Framework v7.01.00.04
# if you want to "see" the old logic, then comment the folowing line out
# and follow it with the debugger (tip: compare the test results)

FRM_DRV_set_new_test_driver( TRUE );

# you may prefer to load your driver library here (instead of the startup script)
#reload( "DRV/main_lib", 0, 0 );

# calls the generic test driver

call "DRV/emos_testsuite_driver" ( TEST_HOME, DATA_HOME, (table==""? SUITE_TABLE : table), FALSE, SUITE_HDR );


