omadmadapters/mms/tsrc/init/mmstest.ini
changeset 45 0f9fc722d255
parent 44 137912d1a556
equal deleted inserted replaced
44:137912d1a556 45:0f9fc722d255
       
     1 #
       
     2 # This is STIF initialization file
       
     3 # Comment lines start with '#'-character.
       
     4 # See STIF TestFramework users guide.doc for instructions
       
     5 
       
     6 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
     7 # Set following test engine settings:
       
     8 #	- Set Test Reporting mode. TestReportMode's possible values are:
       
     9 #		+ 'Summary': Summary of the tested test cases.
       
    10 #		+ 'Environment': Hardware and software info.
       
    11 #		+ 'TestCases': Test case report.
       
    12 #		+ 'FullReport': Set of all above ones.
       
    13 #		+ Example 'TestReportMode= Summary TestCases'
       
    14 #
       
    15 # 	- CreateTestReport setting controls report creation mode
       
    16 #		+ YES, Test report will created.
       
    17 #		+ NO, No Test report.
       
    18 #
       
    19 # 	- File path indicates the base path of the test report.
       
    20 # 	- File name indicates the name of the test report.
       
    21 #
       
    22 # 	- File format indicates the type of the test report.
       
    23 #		+ TXT, Test report file will be txt type, for example 'TestReport.txt'.
       
    24 #		+ HTML, Test report will be html type, for example 'TestReport.html'.
       
    25 #
       
    26 # 	- File output indicates output source of the test report.
       
    27 #		+ FILE, Test report logging to file.
       
    28 #		+ RDEBUG, Test report logging to using rdebug.
       
    29 #
       
    30 # 	- File Creation Mode indicates test report overwriting if file exist.
       
    31 #		+ OVERWRITE, Overwrites if the Test report file exist.
       
    32 #		+ APPEND, Continue logging after the old Test report information if
       
    33 #                 report exist.
       
    34 # 	- Sets a device reset module's dll name(Reboot).
       
    35 #		+ If Nokia specific reset module is not available or it is not correct one
       
    36 #		  StifHWResetStub module may use as a template for user specific reset
       
    37 #		  module.
       
    38 # 	- Sets STIF test measurement disable options. e.g. pluging1 and pluging2 disablation
       
    39 #		DisableMeasurement= stifmeasurementplugin01 stifmeasurementplugin02
       
    40 #
       
    41 
       
    42 [Engine_Defaults]
       
    43 
       
    44 TestReportMode= FullReport    # Possible values are: 'Empty', 'Summary', 'Environment',
       
    45                                                      'TestCases' or 'FullReport'
       
    46 
       
    47 CreateTestReport= YES         # Possible values: YES or NO
       
    48 
       
    49 TestReportFilePath= C:\LOGS\TestFramework\
       
    50 TestReportFileName= TestReport
       
    51 
       
    52 TestReportFormat= TXT         # Possible values: TXT or HTML
       
    53 TestReportOutput= FILE        # Possible values: FILE or RDEBUG
       
    54 TestReportFileCreationMode= OVERWRITE # Possible values: OVERWRITE or APPEND
       
    55 
       
    56 DeviceResetDllName= StifResetForNokia.dll # e.g. 'StifHWResetStub.dll' for user specific reseting
       
    57 
       
    58 DisableMeasurement= stifmeasurementdisablenone  # Possible values are:
       
    59               # 'stifmeasurementdisablenone', 'stifmeasurementdisableall'
       
    60               # 'stifmeasurementplugin01', 'stifmeasurementplugin02',
       
    61               # 'stifmeasurementplugin03', 'stifmeasurementplugin04',
       
    62               # 'stifmeasurementplugin05' or 'stifbappeaprofiler'
       
    63 
       
    64 Timeout= 0                    # Default timeout value for each test case. In milliseconds
       
    65 #UITestingSupport= YES        # Possible values: YES or NO
       
    66 #SeparateProcesses= YES       # Possible values: YES or NO (default: NO)
       
    67 [End_Defaults]
       
    68 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
    69 
       
    70 
       
    71 
       
    72 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
    73 # Module configurations start
       
    74 # Modules are added between module tags
       
    75 # tags. Module name is specified after ModuleName= tag, like
       
    76 # ModuleName= XXXXXXXXX
       
    77 # Modules might have initialisation file, specified as
       
    78 # IniFile= c:\testframework\YYYYYY
       
    79 # Modules might have several configuration files, like
       
    80 # TestCaseFile= c:\testframework\NormalCases.txt
       
    81 # TestCaseFile= c:\testframework\SmokeCases.txt
       
    82 # TestCaseFile= c:\testframework\ManualCases.txt
       
    83 
       
    84 # (TestCaseFile is synonym for old term ConfigFile)
       
    85 
       
    86 # Following case specifies demo module settings. Demo module
       
    87 # does not read any settings from file, so tags 
       
    88 # IniFile and TestCaseFile are not used.
       
    89 # In the simplest case it is enough to specify only the
       
    90 # name of the test module when adding new test module
       
    91 
       
    92 #[New_Module]
       
    93 #ModuleName= demomodule
       
    94 #[End_Module]
       
    95 
       
    96 
       
    97 [New_Module]
       
    98 ModuleName= testscripter
       
    99 #DM
       
   100 TestCaseFile= c:\testframework\mmstest.cfg
       
   101 [End_Module]
       
   102 
       
   103 
       
   104 # Load testmoduleXXX, optionally with initialization file and/or test case files
       
   105 #[New_Module]
       
   106 #ModuleName= testmodulexxx
       
   107 
       
   108 #TestModuleXXX used initialization file
       
   109 #IniFile= c:\testframework\init.txt
       
   110 
       
   111 #TestModuleXXX used configuration file(s)
       
   112 #TestCaseFile= c:\testframework\testcases1.cfg
       
   113 #TestCaseFile= c:\testframework\testcases2.cfg
       
   114 #TestCaseFile= c:\testframework\manualtestcases.cfg
       
   115 
       
   116 #[End_Module]
       
   117 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
   118 
       
   119 
       
   120 
       
   121 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
   122 # Set STIF logging overwrite parameters for Logger.
       
   123 # 	Hardware and emulator environment logging path and styles can
       
   124 # 	be configured from here to overwrite the Logger's implemented values.
       
   125 #	
       
   126 #	Settings description:
       
   127 #	- Indicates option for creation log directory/directories. If log directory/directories
       
   128 #         is/are not created by user they will make by software.
       
   129 #		+ YES, Create log directory/directories if not allready exist.
       
   130 #		+ NO, Log directory/directories not created. Only created one is used.
       
   131 #
       
   132 #	- Overwrite emulator path setting.
       
   133 #		+ Example: If 'EmulatorBasePath= C:\LOGS\TestFramework\' and in code is defined 
       
   134 #		           Logger's path 'D:\\LOGS\\Module\\' with those definition the path
       
   135 #		           will be 'C:\LOGS\TestFramework\LOGS\Module\'
       
   136 #
       
   137 #	- Overwrite emulator's logging format.
       
   138 #		+ TXT, Log file(s) will be txt type(s), for example 'Module.txt'.
       
   139 #		+ HTML, Log file(s) will be html type(s), for example 'Module.html'.
       
   140 #
       
   141 #	- Overwrited emulator logging output source.
       
   142 #		+ FILE, Logging to file(s).
       
   143 #		+ RDEBUG, Logging to using rdebug(s).
       
   144 #
       
   145 #	- Overwrite hardware path setting (Same description as above in emulator path).
       
   146 #	- Overwrite hardware's logging format(Same description as above in emulator format).
       
   147 #	- Overwrite hardware's logging output source(Same description as above in emulator output).
       
   148 #
       
   149 #	- File Creation Mode indicates file overwriting if file exist.
       
   150 #		+ OVERWRITE, Overwrites if file(s) exist.
       
   151 #		+ APPEND, Continue logging after the old logging information if file(s) exist.
       
   152 #
       
   153 #	- Will thread id include to the log filename.
       
   154 #		+ YES, Thread id to log file(s) name, Example filename 'Module_b9.txt'.
       
   155 #		+ NO, No thread id to log file(s), Example filename 'Module.txt'.
       
   156 #
       
   157 #	- Will time stamps include the to log file.
       
   158 #		+ YES, Time stamp added to each line in log file(s). Time stamp is 
       
   159 #                 for example'12.Nov.2003 115958    LOGGING INFO'
       
   160 #		+ NO, No time stamp(s).
       
   161 #
       
   162 #	- Will line breaks include to the log file.
       
   163 #		+ YES, Each logging event includes line break and next log event is in own line.
       
   164 #		+ NO, No line break(s).
       
   165 #
       
   166 #	- Will event ranking include to the log file.
       
   167 #		+ YES, Event ranking number added to each line in log file(s). Ranking number
       
   168 #                 depends on environment's tics, for example(includes time stamp also)
       
   169 #                 '012   12.Nov.2003 115958    LOGGING INFO'
       
   170 #		+ NO, No event ranking.
       
   171 #
       
   172 #	- Will write log file in unicode format.
       
   173 #		+ YES, Log file will be written in unicode format
       
   174 #		+ NO, Log will be written as normal, not unicode, file.
       
   175 #
       
   176 
       
   177 [Logger_Defaults]
       
   178 
       
   179 #NOTE: If you want to set Logger using next setting(s) remove comment(s)'#'
       
   180 #NOTE: TestEngine and TestServer logging settings cannot change here
       
   181 
       
   182 #CreateLogDirectories= YES    # Possible values: YES or NO
       
   183 
       
   184 #EmulatorBasePath= C:\LOGS\TestFramework\
       
   185 #EmulatorFormat= HTML         # Possible values: TXT or HTML
       
   186 #EmulatorOutput= FILE         # Possible values: FILE or RDEBUG
       
   187 
       
   188 #HardwareBasePath= D:\LOGS\TestFramework\
       
   189 #HardwareFormat= HTML         # Possible values: TXT or HTML
       
   190 #HardwareOutput= FILE         # Possible values: FILE or RDEBUG
       
   191 
       
   192 #FileCreationMode= OVERWRITE  # Possible values: OVERWRITE or APPEND
       
   193 
       
   194 #ThreadIdToLogFile= YES       # Possible values: YES or NO
       
   195 #WithTimeStamp= YES           # Possible values: YES or NO
       
   196 #WithLineBreak= YES           # Possible values: YES or NO
       
   197 #WithEventRanking= YES        # Possible values: YES or NO
       
   198 
       
   199 #FileUnicode= YES             # Possible values: YES or NO
       
   200 #AddTestCaseTitle= YES        # Possible values: YES or NO
       
   201 [End_Logger_Defaults]
       
   202 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
       
   203 
       
   204 # End of file