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