|
1 // |
|
2 // Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies). |
|
3 // All rights reserved. |
|
4 // This component and the accompanying materials are made available |
|
5 // under the terms of "Eclipse Public License v1.0" |
|
6 // which accompanies this distribution, and is available |
|
7 // at the URL "http://www.eclipse.org/legal/epl-v10.html". |
|
8 // |
|
9 // Initial Contributors: |
|
10 // Nokia Corporation - initial contribution. |
|
11 // |
|
12 // Contributors: |
|
13 // |
|
14 // Description: |
|
15 // |
|
16 //Script file for running Multiple Alarm Notification Mode tests |
|
17 |
|
18 PRINT Running_Multiple_Alarm_Notification_Mode_Tests |
|
19 |
|
20 // Load the test |
|
21 LOAD_SUITE TestMultipleAlarmsServer -SharedData |
|
22 |
|
23 // Start alert server in multiple alarms notification mode |
|
24 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestStartAlertServerStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini start_multiple_3 |
|
25 |
|
26 // Initial Cleanup |
|
27 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
28 |
|
29 |
|
30 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-002-HP-0001 |
|
31 //! @file TestMultipleAlarmsSuite.script |
|
32 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-002-HP-0001 |
|
33 //! @SYMTestCaseDesc Multiple alarms support |
|
34 //! @SYMFssID <App-Services>/<AlarmServer>/038 |
|
35 //! @SYMTestStatus Implemented |
|
36 //! @SYMTestPriority High |
|
37 //! @SYMTestActions 1. Start the Alarm Alert Server passing a value for aMaxAlarms value. |
|
38 //! 2. Create many calendar entries with alarms that have imminent expiry times |
|
39 //! 3. Wait for the alarms to expire. |
|
40 //! 4. Verify that the test code is not notified of more than aMaxAlarms alarms |
|
41 //! @SYMTestExpectedResults When these alarms expire, the alarms are displayed continuously, without waiting |
|
42 //! for an action from the test code on the previous alarm. |
|
43 //! Only aMaxAlarms are notified at a time |
|
44 //! @SYMTestType CIT |
|
45 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
46 |
|
47 // Start alert server in multiple mode, create entries with imminent alarms and wait for the alarms to expire |
|
48 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
49 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
50 |
|
51 // First 3 alarms must be showing (3rd one playing) |
|
52 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
53 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
54 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
55 |
|
56 // 4th one must not be showing/playing. There must not even be an alarm control object for it. |
|
57 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
58 |
|
59 // Acknowledge the first alarm and wait for a minute |
|
60 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_1 |
|
61 DELAY 500 |
|
62 |
|
63 // Now the fourth one must be notifying |
|
64 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_4 |
|
65 |
|
66 // Cleanup |
|
67 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
68 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-002-HP-0001 |
|
69 |
|
70 |
|
71 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-003-HP-0001 |
|
72 //! @file TestMultipleAlarmsSuite.script |
|
73 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-003-HP-0001 |
|
74 //! @SYMTestCaseDesc Snooze when number of alarms is equal to MaxAlarms |
|
75 //! @SYMFssID <App-Services>/<AlarmServer>/040 |
|
76 //! @SYMTestStatus Implemented |
|
77 //! @SYMTestPriority High |
|
78 //! @SYMTestActions 1. Create as many armed calendar entries as the value of max alarms |
|
79 //! 2. Wait for the alarms to expire. |
|
80 //! 3. Snooze one of the alarms |
|
81 //! @SYMTestExpectedResults 1. When these alarms expire, the alarms are displayed continuously, without waiting |
|
82 //! for an action from the test code on the previous alarm. |
|
83 //! 2. Only the alarm, on which the snooze request was placed, is snoozed, and the |
|
84 //! others still keep notifying |
|
85 //! 3. The alarm that was snoozed, is notified again, after the snooze period even if the |
|
86 //! test code does not respond to the already notifying alarms. |
|
87 //! @SYMTestType CIT |
|
88 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
89 |
|
90 // Create entries with imminent alarms and wait for the alarms to expire |
|
91 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_3 |
|
92 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_3mins |
|
93 |
|
94 // All 3 alarms must be showing (3rd one playing) |
|
95 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
96 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
97 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
98 |
|
99 // Snooze 3rd alarm |
|
100 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmSnoozeStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snooze_3 |
|
101 DELAY 500 |
|
102 |
|
103 // 1st and 2nd alarms must be showing (2nd one playing). 3rd alarm is snoozing. |
|
104 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
105 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_2 |
|
106 // Since alert server must maintain only currently notifying alarms, alarms server asks |
|
107 // alert server to remove alarm3 from its list |
|
108 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snoozing_3 |
|
109 |
|
110 // Wait for 3rd alarm to wake up again |
|
111 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_2mins |
|
112 |
|
113 // All 3 alarms must be showing (3rd one playing) |
|
114 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
115 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
116 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
117 |
|
118 // Cleanup |
|
119 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
120 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-003-HP-0001 |
|
121 |
|
122 |
|
123 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-004-HP-0001 |
|
124 //! @file TestMultipleAlarmsSuite.script |
|
125 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-004-HP-0001 |
|
126 //! @SYMTestCaseDesc Snooze when number of alarms is greater than MaxAlarms |
|
127 //! @SYMFssID <App-Services>/<AlarmServer>/040 |
|
128 //! @SYMTestStatus Implemented |
|
129 //! @SYMTestPriority High |
|
130 //! @SYMTestActions 1. Create more armed calendar entries than the value of max alarms |
|
131 //! 2. Wait for the alarms to expire. |
|
132 //! 3. Snooze one of the alarms |
|
133 //! 4. Wait till szooze period ends and check that the snoozed alarm queues itself after waking up |
|
134 //! 5. Snooze another alarm and verify that the one that was snoozed previously notifies now. |
|
135 //! @SYMTestExpectedResults 1. When the alarms expire, the alarms are displayed continuously, without waiting |
|
136 //! for an action from the test code on the previous alarm. |
|
137 //! 2. Only the alarm, on which the snooze request was placed, is snoozed, and the |
|
138 //! others still keep notifying. |
|
139 //! 3. Another alarm which was in queue starts notifying |
|
140 //! 4. After the snooze period ends, the alarm that was snoozed is queued |
|
141 //! 4. When a second alarm is snoozed, the first one notifies. |
|
142 //! @SYMTestType CIT |
|
143 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
144 |
|
145 // Create entries with imminent alarms and wait for the alarms to expire |
|
146 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
147 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
148 |
|
149 // First 3 alarms must be showing (3rd one playing) |
|
150 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
151 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
152 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
153 |
|
154 // Fourth alarm not yet notified |
|
155 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
156 |
|
157 // Snooze 2nd alarm |
|
158 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmSnoozeStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snooze_2 |
|
159 DELAY 500 |
|
160 |
|
161 // 1st and 3rd alarms must be showing. 2nd one snoozing. The 4th one starts showing and playing. |
|
162 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
163 // Since alert server must maintain only currently notifying alarms, alarms server asks |
|
164 // alert server to remove alarm2 from its list |
|
165 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snoozing_2 |
|
166 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
167 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_4 |
|
168 |
|
169 // Wait for 2nd alarm to wake up again |
|
170 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_2mins |
|
171 |
|
172 // 2nd alarm pre-empts the 4th alarm when it wakes up and starts playing. 4th alarm is removed from alert server |
|
173 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
174 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
175 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_2 |
|
176 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
177 |
|
178 // Snooze 1st alarm |
|
179 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmSnoozeStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snooze_1 |
|
180 DELAY 500 |
|
181 |
|
182 // 4th alarm starts showing and playing |
|
183 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini snoozing_1 |
|
184 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
185 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
186 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_4 |
|
187 |
|
188 // Cleanup |
|
189 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
190 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-004-HP-0001 |
|
191 |
|
192 |
|
193 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-005-HP-0001 |
|
194 //! @file TestMultipleAlarmsSuite.script |
|
195 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-005-HP-0001 |
|
196 //! @SYMTestCaseDesc Clear when number of alarms is equal to MaxAlarms |
|
197 //! @SYMFssID <App-Services>/<AlarmServer>/041 |
|
198 //! @SYMTestStatus Implemented |
|
199 //! @SYMTestPriority High |
|
200 //! @SYMTestActions 1. Create as many armed calendar entries as the value of max alarms |
|
201 //! 2. Wait for the alarms to expire. |
|
202 //! 3. Clear one of the alarms |
|
203 //! @SYMTestExpectedResults 1. When these alarms expire, the alarms are displayed continuously, without waiting |
|
204 //! for an action from the test code on the previous alarm. |
|
205 //! 2. Only the alarm, on which the clear requestwas placed, is cleared, and the |
|
206 //! others still keep notifying |
|
207 //! @SYMTestType CIT |
|
208 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
209 |
|
210 // Create entries with imminent alarms and wait for the alarms to expire |
|
211 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_3 |
|
212 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_3mins |
|
213 |
|
214 // All 3 alarms must be showing (3rd one playing) |
|
215 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
216 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
217 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
218 |
|
219 // Clear 3rd alarm |
|
220 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_3 |
|
221 DELAY 500 |
|
222 |
|
223 // 1st and 2nd alarms must be showing (2nd one playing). 3rd alarm is cleared |
|
224 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
225 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_2 |
|
226 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
227 |
|
228 // Wait for sometime just to check if the same state is maintained. |
|
229 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_2mins |
|
230 |
|
231 // 1st and 2nd alarms must be showing (2nd one playing). 3rd alarm is cleared |
|
232 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
233 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_2 |
|
234 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
235 |
|
236 // Cleanup |
|
237 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
238 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-005-HP-0001 |
|
239 |
|
240 |
|
241 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-006-HP-0001 |
|
242 //! @file TestMultipleAlarmsSuite.script |
|
243 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-006-HP-0001 |
|
244 //! @SYMTestCaseDesc Clear when number of alarms is greater than MaxAlarms |
|
245 //! @SYMFssID <App-Services>/<AlarmServer>/041 |
|
246 //! @SYMTestStatus Implemented |
|
247 //! @SYMTestPriority High |
|
248 //! @SYMTestActions 1. Create more armed calendar entries than the value of max alarms |
|
249 //! 2. Wait for the alarms to expire. |
|
250 //! 3. Clear one of the alarms |
|
251 //! 4. Clear another alarm and verify that another queued one notifies now. |
|
252 //! @SYMTestExpectedResults 1. When the alarms expire, the alarms are displayed continuously, without waiting |
|
253 //! for an action from the test code on the previous alarm. |
|
254 //! 2. Only the alarm, on which the clear request was placed, is cleared, and the |
|
255 //! others still keep notifying. |
|
256 //! 3. Another alarm which was in queue starts notifying |
|
257 //! 4. When a second alarm is cleared another queued one notifies. |
|
258 //! @SYMTestType CIT |
|
259 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
260 |
|
261 // Create entries with imminent alarms and wait for the alarms to expire |
|
262 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5 |
|
263 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_5mins |
|
264 |
|
265 // First 3 alarms must be showing (3rd one playing) |
|
266 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
267 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
268 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
269 |
|
270 // Fourth and fifth alarms not yet notified |
|
271 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
272 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_5 |
|
273 |
|
274 // Clear 2nd alarm |
|
275 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_2 |
|
276 DELAY 500 |
|
277 |
|
278 // 1st and 3rd alarms must be showing. 2nd one cleared. The 4th one starts showing and playing. |
|
279 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
280 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
281 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
282 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_4 |
|
283 |
|
284 // Clear 4th alarm |
|
285 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_4 |
|
286 DELAY 500 |
|
287 |
|
288 // 1st 3rd and 5th alarms must be showing.(5th one playing) 2nd and 4th ones cleared. |
|
289 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
290 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
291 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
292 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
293 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_5 |
|
294 |
|
295 // Wait for sometime just to check if the same state is maintained. |
|
296 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_2mins |
|
297 |
|
298 // 1st and 3rd alarms must be showing.(3rd one playing) 2nd and 4th ones cleared. |
|
299 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
300 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
301 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_3 |
|
302 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
303 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_5 |
|
304 |
|
305 // Cleanup |
|
306 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
307 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-006-HP-0001 |
|
308 |
|
309 |
|
310 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-007-2-HP-0001 |
|
311 //! @file TestMultipleAlarmsSuite.script |
|
312 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-007-2-HP-0001 |
|
313 //! @SYMTestCaseDesc Clear all alarms in multiple alarms mode |
|
314 //! @SYMFssID <App-Services>/<AlarmServer>/041 |
|
315 //! @SYMTestStatus Implemented |
|
316 //! @SYMTestPriority High |
|
317 //! @SYMTestActions 1. Start the Alarm Alert Server passing a value for aMaxAlarms value. |
|
318 //! 2. Create many calendar entries with alarms that have imminent expiry times |
|
319 //! 3. Wait for the alarms to expire. |
|
320 //! 4. Verify that the test code is not notified of more than one alarm at a time. |
|
321 //! 5. Issue the Clear-all request |
|
322 //! @SYMTestExpectedResults 1. When the alarms expire, the alarms are displayed continuously, without waiting |
|
323 //! for an action from the test code on the previous alarm. |
|
324 //! 2. All the alarms are cleared. |
|
325 //! @SYMTestType CIT |
|
326 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
327 |
|
328 // Start alert server in multiple mode, create entries with imminent alarms and wait for the alarms to expire |
|
329 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
330 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
331 |
|
332 // 1st, 2nd and 3rd alarm must be notifying. (3rd one playing) |
|
333 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_1 |
|
334 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showing_2 |
|
335 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
336 |
|
337 // The 4th alarm must not have a corresponding alarm control object. |
|
338 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
339 |
|
340 // Issue the clear-all request |
|
341 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_all |
|
342 DELAY 500 |
|
343 |
|
344 // All 4 alarms must not have a corresponding alarm control object. |
|
345 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
346 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
347 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
348 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
349 |
|
350 // Cleanup |
|
351 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
352 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-007-2-HP-0001 |
|
353 |
|
354 |
|
355 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-008-2-AND-009-HP-0001 |
|
356 //! @file TestMultipleAlarmsSuite.script |
|
357 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-008-2-AND-009-HP-0001 |
|
358 //! @SYMTestCaseDesc Associated Data Multiple Alarms Mode, Reference to Calendar Entry |
|
359 //! @SYMFssID <App-Engines>/<CalInterimAPI>/ EAS 1.0, <App-Engines>/< AgnModel >/EAS 1.1 |
|
360 //! @SYMTestStatus Implemented |
|
361 //! @SYMTestPriority High |
|
362 //! @SYMTestActions 1. Start the Alarm Alert Server passing a value for aMaxAlarms value. |
|
363 //! 2. Create many calendar entries with alarms that have the same expiry time. |
|
364 //! Set either the 8-bit URL associated data or the MIME associated data for all |
|
365 //! the calendar entries during creation. |
|
366 //! 3. Wait for the alarms to expire. |
|
367 //! 4. Retreive the Alarm Data from the Alert Server for the notifying alarms |
|
368 //! 5. Retrieve the corresponding Calendar entries' details, e.g., GUID, recurrence id etc. |
|
369 //! from the Alarm Server for the notifying alarm |
|
370 //! 6. Retrieve the Calendar entries using the information received. |
|
371 //! 7. Retrieve the associated data from the Calendar entries and compare with the original |
|
372 //! values used for setting them. |
|
373 //! @SYMTestExpectedResults The associated data is set and retrieved consistently. |
|
374 //! @SYMTestType CIT |
|
375 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
376 |
|
377 // Start alert server in multiple mode, create entries with imminent alarms and wait for the alarms to expire |
|
378 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
379 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
380 |
|
381 // Test the associated data of the notifying alarms |
|
382 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry1 |
|
383 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry2 |
|
384 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry3 |
|
385 |
|
386 // 4th alarm must not have been notified to alert server |
|
387 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry4 |
|
388 |
|
389 // Cleanup |
|
390 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
391 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-008-2-AND-009-HP-0001 |
|
392 |
|
393 |
|
394 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-010-HP-0001 |
|
395 //! @file TestMultipleAlarmsSuite.script |
|
396 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-010-HP-0001 |
|
397 //! @SYMTestCaseDesc Associated Data – MIME - Multiple Alarms Mode. Different combinations of alarm sound name |
|
398 //! and rich data. |
|
399 //! @SYMFssID <App-Engines>/<CalInterimAPI>/EAS 1.0 |
|
400 //! @SYMTestStatus Implemented |
|
401 //! @SYMTestPriority High |
|
402 //! @SYMTestActions 1. Start the Alarm Alert Server without passing a value for aMaxAlarms value. |
|
403 //! 2. Create many calendar entries with alarms that have the same expiry time. |
|
404 //! Set the MIME associated data for all the calendar entries during creation. |
|
405 //! Try different combinations like, a) no sound name, but has rich data; |
|
406 //! b) does not have both etc. |
|
407 //! 3. Wait for the alarms to expire. |
|
408 //! 4. Retreive the Alarm Data from the Alert Server for the notifying alarms |
|
409 //! 5. Retrieve the corresponding Calendar entries' details, e.g., GUID, recurrence id etc. |
|
410 //! from the Alarm Server for the notifying alarm |
|
411 //! 6. Retrieve the Calendar entries using the information received. |
|
412 //! 7. Retrieve the associated data from the Calendar entries and compare with the original |
|
413 //! values used for setting them. |
|
414 //! @SYMTestExpectedResults The associated data is set and retrieved consistently. If no alarm sound name was set when |
|
415 //! creating the entries, the alarm sound name given to the UI by the alert server must be a NULL |
|
416 //! descriptor |
|
417 //! @SYMTestType CIT |
|
418 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
419 |
|
420 // Start alert server in multiple mode, create entries with imminent alarms and wait for the alarms to expire |
|
421 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5 |
|
422 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
423 |
|
424 // Test the first entry. It neither has sound name, nor has rich data. |
|
425 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5.entry1 |
|
426 |
|
427 // Test the associated data of the second and third alarms which has MIME associated data. |
|
428 // Second one does not have sound name. Third one has sound name. |
|
429 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5.entry2 |
|
430 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5.entry3 |
|
431 |
|
432 // Clear one alarm, and give way to the fourth alarm. |
|
433 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_1 |
|
434 DELAY 1000 |
|
435 |
|
436 // Test the associated data of the fourth alarm which has MIME associated data too |
|
437 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_5.entry4 |
|
438 |
|
439 // Cleanup |
|
440 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
441 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-010-HP-0001 |
|
442 |
|
443 |
|
444 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-011-HP-0001 |
|
445 //! @file TestMultipleAlarmsSuite.script |
|
446 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-011-HP-0001 |
|
447 //! @SYMTestCaseDesc The time lag between the expiry of the alarm at the alarm server and the notification |
|
448 //! received from the alert server by the UI application. |
|
449 //! @SYMFssID |
|
450 //! @SYMTestStatus Implemented |
|
451 //! @SYMTestPriority High |
|
452 //! @SYMTestActions 1. Start the Alarm Alert Server passing a value for aMaxAlarms value. |
|
453 //! 2. Create many calendar entries with alarms that have imminent expiry times |
|
454 //! Attach URL or MIME associated data to the entries |
|
455 //! 3. Wait for the alarms to expire. |
|
456 //! 4. Note down the time when alert server notifies the alarm control |
|
457 //! 5. Note down the original expiry time of the alarm |
|
458 //! 6. Compare both the times and check if they do not breach the allowed time |
|
459 //! 7. Similarly measure the time taken for retreiving the associated data |
|
460 //! @SYMTestExpectedResults The time lag between the expiry of the alarm and the receipt of the notification must |
|
461 //! not be greater than the allowed time for this (0.5 seconds). Similarly for the time lag |
|
462 //! between retreiving the associated data. |
|
463 //! @SYMTestType CIT |
|
464 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
465 |
|
466 // Start alert server in multiple mode, create entries with imminent alarms and wait for the alarms to expire |
|
467 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini create_arbitrary |
|
468 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
469 |
|
470 // Test the performance of all alarms |
|
471 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestPerformanceStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini performance |
|
472 |
|
473 // Cleanup |
|
474 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
475 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-011-HP-0001 |
|
476 |
|
477 |
|
478 // Kill alert server thread |
|
479 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestKillAlertServerStep |