os/ossrv/stdcpp/tsrc/BC/apps/BCThread/group/testframework.ini
changeset 0 bde4ae8d615e
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/os/ossrv/stdcpp/tsrc/BC/apps/BCThread/group/testframework.ini	Fri Jun 15 03:10:57 2012 +0200
     1.3 @@ -0,0 +1,179 @@
     1.4 +#
     1.5 +# This is STIFTestFramework initialization file
     1.6 +# Comment lines start with '#'-character.
     1.7 +# See STIF TestFramework users guide.doc for instructions
     1.8 +
     1.9 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    1.10 +# Set following test engine settings:
    1.11 +#	- Set Test Reporting mode. TestReportMode's possible values are:
    1.12 +#		+ 'Summary': Summary of the tested test cases.
    1.13 +#		+ 'Environment': Hardware and software info.
    1.14 +#		+ 'TestCases': Test case report.
    1.15 +#		+ 'FullReport': Set of all above ones.
    1.16 +#		+ Example 'TestReportMode= Summary TestCases'
    1.17 +#
    1.18 +# 	- CreateTestReport setting controls report creation mode
    1.19 +#		+ YES, Test report will created.
    1.20 +#		+ NO, No Test report.
    1.21 +#
    1.22 +# 	- File path indicates the base path of the test report.
    1.23 +# 	- File name indicates the name of the test report.
    1.24 +#
    1.25 +# 	- File format indicates the type of the test report.
    1.26 +#		+ TXT, Test report file will be txt type, for example 'TestReport.txt'.
    1.27 +#		+ HTML, Test report will be html type, for example 'TestReport.html'.
    1.28 +#
    1.29 +# 	- File output indicates output source of the test report.
    1.30 +#		+ FILE, Test report logging to file.
    1.31 +#		+ RDEBUG, Test report logging to using rdebug.
    1.32 +#
    1.33 +# 	- File Creation Mode indicates test report overwriting if file exist.
    1.34 +#		+ OVERWRITE, Overwrites if the Test report file exist.
    1.35 +#		+ APPEND, Continue logging after the old Test report information if 
    1.36 +#                 report exist.
    1.37 +# 	- Sets a device reset module's dll name(Reboot).
    1.38 +#		+ If Nokia specific reset module is not available or it is not correct one
    1.39 +#		  StifHWResetStub module may use as a template for user specific reset
    1.40 +#		  module. 
    1.41 +
    1.42 +[Engine_Defaults]
    1.43 +
    1.44 +TestReportMode= FullReport		# Possible values are: 'Empty', 'Summary', 'Environment',
    1.45 +                                                               'TestCases' or 'FullReport'
    1.46 +
    1.47 +CreateTestReport= YES			# Possible values: YES or NO
    1.48 +
    1.49 +TestReportFilePath= C:\LOGS\TestFramework\
    1.50 +TestReportFileName= TestReport
    1.51 +
    1.52 +TestReportFormat= TXT			# Possible values: TXT or HTML
    1.53 +TestReportOutput= FILE			# Possible values: FILE or RDEBUG
    1.54 +TestReportFileCreationMode= OVERWRITE	# Possible values: OVERWRITE or APPEND
    1.55 +
    1.56 +DeviceResetDllName= StifResetForNokia.dll # e.g. 'StifHWResetStub.dll' for user specific reseting
    1.57 +
    1.58 +[End_Defaults]
    1.59 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    1.60 +
    1.61 +
    1.62 +
    1.63 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    1.64 +# Module configurations start
    1.65 +# Modules are added between module tags
    1.66 +# tags. Module name is specified after ModuleName= tag, like
    1.67 +# ModuleName= XXXXXXXXX
    1.68 +# Modules might have initialisation file, specified as
    1.69 +# IniFile= c:\testframework\YYYYYY
    1.70 +# Modules might have several configuration files, like
    1.71 +# TestCaseFile= c:\testframework\NormalCases.txt
    1.72 +# TestCaseFile= c:\testframework\SmokeCases.txt
    1.73 +# TestCaseFile= c:\testframework\ManualCases.txt
    1.74 +
    1.75 +# (TestCaseFile is synonym for old term ConfigFile)
    1.76 +
    1.77 +# Following case specifies demo module settings. Demo module
    1.78 +# does not read any settings from file, so tags 
    1.79 +# IniFile and TestCaseFile are not used.
    1.80 +# In the simplest case it is enough to specify only the
    1.81 +# name of the test module when adding new test module
    1.82 +
    1.83 +[New_Module]
    1.84 +ModuleName= Testscripter
    1.85 +TestCaseFile= c:\testframework\BCThread.cfg
    1.86 +[End_Module]
    1.87 +
    1.88 +
    1.89 +# Load testmoduleXXX, optionally with initialization file and/or test case files
    1.90 +#[New_Module]
    1.91 +#ModuleName= testmodulexxx
    1.92 +
    1.93 +#TestModuleXXX used initialization file
    1.94 +#IniFile= c:\testframework\init.txt
    1.95 +
    1.96 +#TestModuleXXX used configuration file(s)
    1.97 +#TestCaseFile= c:\testframework\testcases1.cfg
    1.98 +#TestCaseFile= c:\testframework\testcases2.cfg
    1.99 +#TestCaseFile= c:\testframework\manualtestcases.cfg
   1.100 +
   1.101 +#[End_Module]
   1.102 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
   1.103 +
   1.104 +
   1.105 +
   1.106 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
   1.107 +# Set STIFTestFramework logging overwrite parameters for Logger.
   1.108 +# 	Hardware and emulator environment logging path and styles can
   1.109 +# 	be configured from here to overwrite the Logger's implemented values.
   1.110 +#	
   1.111 +#	Settings description:
   1.112 +#	- Indicates option for creation log directory/directories. If log directory/directories
   1.113 +#         is/are not created by user they will make by software.
   1.114 +#		+ YES, Create log directory/directories if not allready exist.
   1.115 +#		+ NO, Log directory/directories not created. Only created one is used.
   1.116 +#
   1.117 +#	- Overwrite emulator path setting.
   1.118 +#		+ Example: If 'EmulatorBasePath= C:\LOGS\TestFramework\' and in code is defined 
   1.119 +#		           Logger's path 'D:\\LOGS\\Module\\' with those definition the path
   1.120 +#		           will be 'C:\LOGS\TestFramework\LOGS\Module\'
   1.121 +#
   1.122 +#	- Overwrite emulator's logging format.
   1.123 +#		+ TXT, Log file(s) will be txt type(s), for example 'Module.txt'.
   1.124 +#		+ HTML, Log file(s) will be html type(s), for example 'Module.html'.
   1.125 +#
   1.126 +#	- Overwrited emulator logging output source.
   1.127 +#		+ FILE, Logging to file(s).
   1.128 +#		+ RDEBUG, Logging to using rdebug(s).
   1.129 +#
   1.130 +#	- Overwrite hardware path setting (Same description as above in emulator path).
   1.131 +#	- Overwrite hardware's logging format(Same description as above in emulator format).
   1.132 +#	- Overwrite hardware's logging output source(Same description as above in emulator output).
   1.133 +#
   1.134 +#	- File Creation Mode indicates file overwriting if file exist.
   1.135 +#		+ OVERWRITE, Overwrites if file(s) exist.
   1.136 +#		+ APPEND, Continue logging after the old logging information if file(s) exist.
   1.137 +#
   1.138 +#	- Will thread id include to the log filename.
   1.139 +#		+ YES, Thread id to log file(s) name, Example filename 'Module_b9.txt'.
   1.140 +#		+ NO, No thread id to log file(s), Example filename 'Module.txt'.
   1.141 +#
   1.142 +#	- Will time stamps include the to log file.
   1.143 +#		+ YES, Time stamp added to each line in log file(s). Time stamp is 
   1.144 +#                 for example'12.Nov.2003 115958    LOGGING INFO'
   1.145 +#		+ NO, No time stamp(s).
   1.146 +#
   1.147 +#	- Will line breaks include to the log file.
   1.148 +#		+ YES, Each logging event includes line break and next log event is in own line.
   1.149 +#		+ NO, No line break(s).
   1.150 +#
   1.151 +#	- Will event ranking include to the log file.
   1.152 +#		+ YES, Event ranking number added to each line in log file(s). Ranking number 
   1.153 +#                 depends on environment's tics, for example(includes time stamp also)
   1.154 +#                 '012   12.Nov.2003 115958    LOGGING INFO'
   1.155 +#		+ NO, No event ranking.
   1.156 +#
   1.157 +
   1.158 +[Logger_Defaults]
   1.159 +
   1.160 +#NOTE: If you want to set Logger using next setting(s) remove comment(s)'#' 
   1.161 +
   1.162 +#CreateLogDirectories= YES		# Possible values: YES or NO
   1.163 +
   1.164 +#EmulatorBasePath= C:\LOGS\TestFramework\
   1.165 +#EmulatorFormat= HTML			# Possible values: TXT or HTML
   1.166 +#EmulatorOutput= FILE			# Possible values: FILE or RDEBUG
   1.167 +
   1.168 +#HardwareBasePath= D:\LOGS\TestFramework\
   1.169 +#HardwareFormat= HTML			# Possible values: TXT or HTML
   1.170 +#HardwareOutput= FILE			# Possible values: FILE or RDEBUG
   1.171 +
   1.172 +#FileCreationMode= OVERWRITE		# Possible values: OVERWRITE or APPEND
   1.173 +
   1.174 +#ThreadIdToLogFile= YES			# Possible values: YES or NO
   1.175 +#WithTimeStamp= YES			# Possible values: YES or NO
   1.176 +#WithLineBreak= YES			# Possible values: YES or NO
   1.177 +#WithEventRanking= YES			# Possible values: YES or NO
   1.178 +
   1.179 +[End_Logger_Defaults]
   1.180 +# -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
   1.181 +
   1.182 +# End of file
   1.183 \ No newline at end of file