sl@0: # sl@0: # This is STIFTestFramework initialization file sl@0: # Comment lines start with '#'-character. sl@0: # See STIF TestFramework users guide.doc for instructions sl@0: sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: # Set following test engine settings: sl@0: # - Set Test Reporting mode. TestReportMode's possible values are: sl@0: # + 'Summary': Summary of the tested test cases. sl@0: # + 'Environment': Hardware and software info. sl@0: # + 'TestCases': Test case report. sl@0: # + 'FullReport': Set of all above ones. sl@0: # + Example 'TestReportMode= Summary TestCases' sl@0: # sl@0: # - CreateTestReport setting controls report creation mode sl@0: # + YES, Test report will created. sl@0: # + NO, No Test report. sl@0: # sl@0: # - File path indicates the base path of the test report. sl@0: # - File name indicates the name of the test report. sl@0: # sl@0: # - File format indicates the type of the test report. sl@0: # + TXT, Test report file will be txt type, for example 'TestReport.txt'. sl@0: # + HTML, Test report will be html type, for example 'TestReport.html'. sl@0: # sl@0: # - File output indicates output source of the test report. sl@0: # + FILE, Test report logging to file. sl@0: # + RDEBUG, Test report logging to using rdebug. sl@0: # sl@0: # - File Creation Mode indicates test report overwriting if file exist. sl@0: # + OVERWRITE, Overwrites if the Test report file exist. sl@0: # + APPEND, Continue logging after the old Test report information if sl@0: # report exist. sl@0: # - Sets a device reset module's dll name(Reboot). sl@0: # + If Nokia specific reset module is not available or it is not correct one sl@0: # StifHWResetStub module may use as a template for user specific reset sl@0: # module. sl@0: sl@0: [Engine_Defaults] sl@0: sl@0: TestReportMode= FullReport # Possible values are: 'Empty', 'Summary', 'Environment', sl@0: 'TestCases' or 'FullReport' sl@0: sl@0: CreateTestReport= YES # Possible values: YES or NO sl@0: sl@0: TestReportFilePath= C:\LOGS\TestFramework\ sl@0: TestReportFileName= TestReport sl@0: sl@0: TestReportFormat= TXT # Possible values: TXT or HTML sl@0: TestReportOutput= FILE # Possible values: FILE or RDEBUG sl@0: TestReportFileCreationMode= OVERWRITE # Possible values: OVERWRITE or APPEND sl@0: sl@0: DeviceResetDllName= StifResetForNokia.dll # e.g. 'StifHWResetStub.dll' for user specific reseting sl@0: sl@0: [End_Defaults] sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: sl@0: sl@0: sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: # Module configurations start sl@0: # Modules are added between module tags sl@0: # tags. Module name is specified after ModuleName= tag, like sl@0: # ModuleName= XXXXXXXXX sl@0: # Modules might have initialisation file, specified as sl@0: # IniFile= c:\testframework\YYYYYY sl@0: # Modules might have several configuration files, like sl@0: # TestCaseFile= c:\testframework\NormalCases.txt sl@0: # TestCaseFile= c:\testframework\SmokeCases.txt sl@0: # TestCaseFile= c:\testframework\ManualCases.txt sl@0: sl@0: # (TestCaseFile is synonym for old term ConfigFile) sl@0: sl@0: # Following case specifies demo module settings. Demo module sl@0: # does not read any settings from file, so tags sl@0: # IniFile and TestCaseFile are not used. sl@0: # In the simplest case it is enough to specify only the sl@0: # name of the test module when adding new test module sl@0: sl@0: [New_Module] sl@0: ModuleName= widecharclassapiBCTest sl@0: [End_Module] sl@0: sl@0: sl@0: # Load testmoduleXXX, optionally with initialization file and/or test case files sl@0: #[New_Module] sl@0: #ModuleName= testmodulexxx sl@0: sl@0: #TestModuleXXX used initialization file sl@0: #IniFile= c:\testframework\init.txt sl@0: sl@0: #TestModuleXXX used configuration file(s) sl@0: #TestCaseFile= c:\testframework\testcases1.cfg sl@0: #TestCaseFile= c:\testframework\testcases2.cfg sl@0: #TestCaseFile= c:\testframework\manualtestcases.cfg sl@0: sl@0: #[End_Module] sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: sl@0: sl@0: sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: # Set STIFTestFramework logging overwrite parameters for Logger. sl@0: # Hardware and emulator environment logging path and styles can sl@0: # be configured from here to overwrite the Logger's implemented values. sl@0: # sl@0: # Settings description: sl@0: # - Indicates option for creation log directory/directories. If log directory/directories sl@0: # is/are not created by user they will make by software. sl@0: # + YES, Create log directory/directories if not allready exist. sl@0: # + NO, Log directory/directories not created. Only created one is used. sl@0: # sl@0: # - Overwrite emulator path setting. sl@0: # + Example: If 'EmulatorBasePath= C:\LOGS\TestFramework\' and in code is defined sl@0: # Logger's path 'D:\\LOGS\\Module\\' with those definition the path sl@0: # will be 'C:\LOGS\TestFramework\LOGS\Module\' sl@0: # sl@0: # - Overwrite emulator's logging format. sl@0: # + TXT, Log file(s) will be txt type(s), for example 'Module.txt'. sl@0: # + HTML, Log file(s) will be html type(s), for example 'Module.html'. sl@0: # sl@0: # - Overwrited emulator logging output source. sl@0: # + FILE, Logging to file(s). sl@0: # + RDEBUG, Logging to using rdebug(s). sl@0: # sl@0: # - Overwrite hardware path setting (Same description as above in emulator path). sl@0: # - Overwrite hardware's logging format(Same description as above in emulator format). sl@0: # - Overwrite hardware's logging output source(Same description as above in emulator output). sl@0: # sl@0: # - File Creation Mode indicates file overwriting if file exist. sl@0: # + OVERWRITE, Overwrites if file(s) exist. sl@0: # + APPEND, Continue logging after the old logging information if file(s) exist. sl@0: # sl@0: # - Will thread id include to the log filename. sl@0: # + YES, Thread id to log file(s) name, Example filename 'Module_b9.txt'. sl@0: # + NO, No thread id to log file(s), Example filename 'Module.txt'. sl@0: # sl@0: # - Will time stamps include the to log file. sl@0: # + YES, Time stamp added to each line in log file(s). Time stamp is sl@0: # for example'12.Nov.2003 115958 LOGGING INFO' sl@0: # + NO, No time stamp(s). sl@0: # sl@0: # - Will line breaks include to the log file. sl@0: # + YES, Each logging event includes line break and next log event is in own line. sl@0: # + NO, No line break(s). sl@0: # sl@0: # - Will event ranking include to the log file. sl@0: # + YES, Event ranking number added to each line in log file(s). Ranking number sl@0: # depends on environment's tics, for example(includes time stamp also) sl@0: # '012 12.Nov.2003 115958 LOGGING INFO' sl@0: # + NO, No event ranking. sl@0: # sl@0: sl@0: [Logger_Defaults] sl@0: sl@0: #NOTE: If you want to set Logger using next setting(s) remove comment(s)'#' sl@0: sl@0: #CreateLogDirectories= YES # Possible values: YES or NO sl@0: sl@0: #EmulatorBasePath= C:\LOGS\TestFramework\ sl@0: #EmulatorFormat= HTML # Possible values: TXT or HTML sl@0: #EmulatorOutput= FILE # Possible values: FILE or RDEBUG sl@0: sl@0: #HardwareBasePath= D:\LOGS\TestFramework\ sl@0: #HardwareFormat= HTML # Possible values: TXT or HTML sl@0: #HardwareOutput= FILE # Possible values: FILE or RDEBUG sl@0: sl@0: #FileCreationMode= OVERWRITE # Possible values: OVERWRITE or APPEND sl@0: sl@0: #ThreadIdToLogFile= YES # Possible values: YES or NO sl@0: #WithTimeStamp= YES # Possible values: YES or NO sl@0: #WithLineBreak= YES # Possible values: YES or NO sl@0: #WithEventRanking= YES # Possible values: YES or NO sl@0: sl@0: [End_Logger_Defaults] sl@0: # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- sl@0: sl@0: # End of file