1 # |
|
2 # This is STIFTestFramework initialization file 123 |
|
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': Sret 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.sd |
|
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 |
|
39 [Engine_Defaults] |
|
40 |
|
41 TestReportMode= FullReport # Possible values are: 'Empty', 'Summary', 'Environment', 'TestCases' or 'FullReport' |
|
42 |
|
43 CreateTestReport= YES # Possible values: YES or NO |
|
44 |
|
45 TestReportFilePath= c:\Logs\Fusion\ |
|
46 TestReportFileName= TestReport |
|
47 |
|
48 TestReportFormat= TXT # Possible values: TXT or HTML |
|
49 TestReportOutput= FILE # Possible values: FILE or RDEBUG |
|
50 TestReportFileCreationMode= APPEND # Possible values: OVERWRITE or APPEND |
|
51 |
|
52 DeviceResetDllName= StifResetForNokia.dll # e.g. 'StifHWResetStub.dll' for user specific reseting |
|
53 |
|
54 DisableMeasurement= stifmeasurementplugin04 |
|
55 UITestingSupport= YES |
|
56 SeparateProcesses= YES |
|
57 [End_Defaults] |
|
58 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |
|
59 |
|
60 |
|
61 |
|
62 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |
|
63 # Module configurations start |
|
64 # Modules are added between module tags |
|
65 # tags. Module name is specified after ModuleName= tag, like |
|
66 # ModuleName= XXXXXXXXX |
|
67 # Modules might have initialisation file, specified as |
|
68 # IniFile= c:\testframework\YYYYYY |
|
69 # Modules might have several configuration files, like |
|
70 # TestCaseFile= c:\testframework\NormalCases.txt |
|
71 # TestCaseFile= c:\testframework\SmokeCases.txt |
|
72 # TestCaseFile= c:\testframework\ManualCases.txt |
|
73 |
|
74 # (TestCaseFile is synonym for old term ConfigFile) |
|
75 |
|
76 # Following case specifies demo module settings. Demo module |
|
77 # does not read any settings from file, so tags |
|
78 # IniFile and TestCaseFile are not used. |
|
79 # In the simplest case it is enough to specify only the |
|
80 # name of the test module when adding new test module |
|
81 |
|
82 |
|
83 [New_Module] |
|
84 ModuleName= TestScripter |
|
85 TestCaseFile= c:\TestFramework\VCXProvisioningTest.cfg |
|
86 TestCaseFile= c:\TestFramework\VCXIapListTest.cfg |
|
87 TestCaseFile= c:\TestFramework\VCXServiceTest.cfg |
|
88 [End_Module] |
|
89 |
|
90 |
|
91 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |
|
92 |
|
93 |
|
94 |
|
95 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |
|
96 # Set STIFTestFramework logging overwrite parameters for Logger. |
|
97 # Hardware and emulator environment logging path and styles can |
|
98 # be configured from here to overwrite the Logger's implemented values. |
|
99 # |
|
100 # Settings description: |
|
101 # - Indicates option for creation log directory/directories. If log directory/directories |
|
102 # is/are not created by user they will make by software. |
|
103 # + YES, Create log directory/directories if not allready exist. |
|
104 # + NO, Log directory/directories not created. Only created one is used. |
|
105 # |
|
106 # - Overwrite emulator path setting. |
|
107 # + Example: If 'EmulatorBasePath= C:\LOGS\TestFramework\' and in code is defined |
|
108 # Logger's path 'D:\\LOGS\\Module\\' with those definition the path |
|
109 # will be 'C:\LOGS\TestFramework\LOGS\Module\' |
|
110 # |
|
111 # - Overwrite emulator's logging format. |
|
112 # + TXT, Log file(s) will be txt type(s), for example 'Module.txt'. |
|
113 # + HTML, Log file(s) will be html type(s), for example 'Module.html'. |
|
114 # |
|
115 # - Overwrited emulator logging output source. |
|
116 # + FILE, Logging to file(s). |
|
117 # + RDEBUG, Logging to using rdebug(s). |
|
118 # |
|
119 # - Overwrite hardware path setting (Same description as above in emulator path). |
|
120 # - Overwrite hardware's logging format(Same description as above in emulator format). |
|
121 # - Overwrite hardware's logging output source(Same description as above in emulator output). |
|
122 # |
|
123 # - File Creation Mode indicates file overwriting if file exist. |
|
124 # + OVERWRITE, Overwrites if file(s) exist. |
|
125 # + APPEND, Continue logging after the old logging information if file(s) exist. |
|
126 # |
|
127 # - Will thread id include to the log filename. |
|
128 # + YES, Thread id to log file(s) name, Example filename 'Module_b9.txt'. |
|
129 # + NO, No thread id to log file(s), Example filename 'Module.txt'. |
|
130 # |
|
131 # - Will time stamps include the to log file. |
|
132 # + YES, Time stamp added to each line in log file(s). Time stamp is |
|
133 # for example'12.Nov.2003 115958 LOGGING INFO' |
|
134 # + NO, No time stamp(s). |
|
135 # |
|
136 # - Will line breaks include to the log file. |
|
137 # + YES, Each logging event includes line break and next log event is in own line. |
|
138 # + NO, No line break(s). |
|
139 # |
|
140 # - Will event ranking include to the log file. |
|
141 # + YES, Event ranking number added to each line in log file(s). Ranking number |
|
142 # depends on environment's tics, for example(includes time stamp also) |
|
143 # '012 12.Nov.2003 115958 LOGGING INFO' |
|
144 # + NO, No event ranking. |
|
145 # |
|
146 |
|
147 [Logger_Defaults] |
|
148 |
|
149 #NOTE: If you want to set Logger using next setting(s) remove comment(s)'#' |
|
150 |
|
151 #CreateLogDirectories= YES # Possible values: YES or NO |
|
152 |
|
153 #EmulatorBasePath= C:\LOGS\TestFramework\ |
|
154 #EmulatorFormat= HTML # Possible values: TXT or HTML |
|
155 #EmulatorOutput= FILE # Possible values: FILE or RDEBUG |
|
156 |
|
157 #HardwareBasePath= C:\ |
|
158 #HardwareFormat= TXT # Possible values: TXT or HTML |
|
159 #HardwareOutput= FILE # Possible values: FILE or RDEBUG |
|
160 |
|
161 #FileCreationMode= APPEND # Possible values: OVERWRITE or APPEND |
|
162 |
|
163 #ThreadIdToLogFile= YES # Possible values: YES or NO |
|
164 #WithTimeStamp= YES # Possible values: YES or NO |
|
165 #WithLineBreak= YES # Possible values: YES or NO |
|
166 #WithEventRanking= YES # Possible values: YES or NO |
|
167 |
|
168 [End_Logger_Defaults] |
|
169 # -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |
|
170 |
|
171 # End of file |
|