|
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 Single Alarm Notification Mode tests |
|
17 |
|
18 PRINT Running_Single_Alarm_Notification_Mode_Tests |
|
19 |
|
20 // Load the test |
|
21 LOAD_SUITE TestMultipleAlarmsServer -SharedData |
|
22 |
|
23 // Start alert server in single alarm notification mode |
|
24 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestStartAlertServerStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini start_single |
|
25 |
|
26 // Initial Cleanup |
|
27 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
28 |
|
29 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-001-HP-0001 |
|
30 //! @file TestMultipleAlarmsSuite.script |
|
31 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-001-HP-0001 |
|
32 //! @SYMTestCaseDesc Single alarm support |
|
33 //! @SYMFssID <App-Services>/<AlarmServer>/039 |
|
34 //! @SYMTestStatus Implemented |
|
35 //! @SYMTestPriority High |
|
36 //! @SYMTestActions 1. Start the Alarm Alert Serverwithout passing a value for aMaxAlarms value. |
|
37 //! 2. Create many calendar entries with alarms that have imminent expiry times |
|
38 //! 3. Wait for the alarms to expire. |
|
39 //! 4. Verify that the test code is not notified of more than one alarm at a time. |
|
40 //! 5. Acknowledge the first alarm to be notified, and verify that the next alarm is notified. |
|
41 //! @SYMTestExpectedResults Only one alarm is notified at a time. |
|
42 //! @SYMTestType CIT |
|
43 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
44 |
|
45 // Start alert server in single mode, create entries with imminent alarms and wait for the alarms to expire |
|
46 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
47 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_5mins |
|
48 |
|
49 // 1st alarm must be notifying |
|
50 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_1 |
|
51 |
|
52 // The other 3 alarms must not have a corresponding alarm control object. |
|
53 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
54 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
55 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
56 |
|
57 // Acknowledge the first alarm and wait for sometime |
|
58 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_1 |
|
59 DELAY 500 |
|
60 |
|
61 // 2nd alarm must be notifying |
|
62 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_2 |
|
63 |
|
64 // The other alarms must not have a corresponding alarm control object. |
|
65 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
66 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
67 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
68 |
|
69 // Acknowledge the second alarm and wait for sometime |
|
70 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_2 |
|
71 DELAY 500 |
|
72 |
|
73 // 3rd alarm must be notifying |
|
74 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_3 |
|
75 |
|
76 // The other alarms must not have a corresponding alarm control object. |
|
77 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
78 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
79 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
80 |
|
81 // Acknowledge the third alarm and wait for sometime |
|
82 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_3 |
|
83 DELAY 500 |
|
84 |
|
85 // 4th alarm must be notifying |
|
86 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_4 |
|
87 |
|
88 // The other alarms must not have a corresponding alarm control object. |
|
89 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
90 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
91 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
92 |
|
93 // Acknowledge the fourth alarm and wait for sometime |
|
94 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_4 |
|
95 DELAY 500 |
|
96 |
|
97 // All 4 alarms must not have a corresponding alarm control object. |
|
98 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
99 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
100 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
101 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
102 |
|
103 // Cleanup |
|
104 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
105 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-001-HP-0001 |
|
106 |
|
107 |
|
108 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-007-1-HP-0001 |
|
109 //! @file TestMultipleAlarmsSuite.script |
|
110 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-007-1-HP-0001 |
|
111 //! @SYMTestCaseDesc Clear all alarms in single alarms mode |
|
112 //! @SYMFssID <App-Services>/<AlarmServer>/041 |
|
113 //! @SYMTestStatus Implemented |
|
114 //! @SYMTestPriority High |
|
115 //! @SYMTestActions 1. Start the Alarm Alert Server without passing a value for aMaxAlarms value. |
|
116 //! 2. Create many calendar entries with alarms that have imminent expiry times |
|
117 //! 3. Wait for the alarms to expire. |
|
118 //! 4. Verify that the test code is not notified of more than one alarm at a time. |
|
119 //! 5. Issue the Clear-all request |
|
120 //! @SYMTestExpectedResults 1. When the alarms expire, the alarms are displayed continuously, without waiting |
|
121 //! for an action from the test code on the previous alarm. |
|
122 //! 2. All the alarms are cleared. |
|
123 //! @SYMTestType CIT |
|
124 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
125 |
|
126 // Start alert server in single mode, create entries with imminent alarms and wait for the alarms to expire |
|
127 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
128 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_4mins |
|
129 |
|
130 // 1st alarm must be notifying |
|
131 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini showingandplaying_1 |
|
132 |
|
133 // The other 3 alarms must not have a corresponding alarm control object. |
|
134 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
135 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
136 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
137 |
|
138 // Issue the clear-all request |
|
139 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_all |
|
140 DELAY 500 |
|
141 |
|
142 // All 4 alarms must not have a corresponding alarm control object. |
|
143 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_1 |
|
144 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_2 |
|
145 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_3 |
|
146 RUN_TEST_STEP !Error=-1 100 TestMultipleAlarmsServer TestAlarmControlStateStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini notshowing_4 |
|
147 |
|
148 // Cleanup |
|
149 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
150 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-007-1-HP-0001 |
|
151 |
|
152 |
|
153 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-008-1-AND-9-HP-0001 |
|
154 //! @file TestMultipleAlarmsSuite.script |
|
155 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-008-1-AND-9-HP-0001 |
|
156 //! @SYMTestCaseDesc Associated Data – URL - Single Alarms Mode, Reference to Calendar Entry |
|
157 //! @SYMFssID <App-Engines>/<CalInterimAPI>/EAS 1.0, <App-Engines>/< AgnModel >/EAS 1.1 |
|
158 //! @SYMTestStatus Implemented |
|
159 //! @SYMTestPriority High |
|
160 //! @SYMTestActions 1. Start the Alarm Alert Server without passing a value for aMaxAlarms value. |
|
161 //! 2. Create many calendar entries with alarms that have the same expiry time. |
|
162 //! Set the 8-bit URL associated data for all the calendar entries during creation. |
|
163 //! 3. Wait for the alarms to expire. |
|
164 //! 4. Retreive the Alarm Data from the Alert Server for the notifying alarm |
|
165 //! 5. Retrieve the corresponding Calendar entry’s details, e.g., GUID, recurrence id etc. |
|
166 //! from the Alarm Server for the notifying alarm |
|
167 //! 6. Retrieve the Calendar entriy using the information received. |
|
168 //! 7. Retrieve the associated data from the Calendar entry and compare with the original |
|
169 //! values used for setting them. |
|
170 //! @SYMTestExpectedResults The associated data is set and retrieved consistently. |
|
171 //! @SYMTestType CIT |
|
172 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
173 |
|
174 // Start alert server in single mode, create entries with imminent alarms and wait for the alarms to expire |
|
175 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_3 |
|
176 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_2mins |
|
177 |
|
178 // Test the associated data of the notifying alarm |
|
179 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_3.entry1 |
|
180 |
|
181 // Cleanup |
|
182 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
183 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-008-1-AND-9-HP-0001 |
|
184 |
|
185 |
|
186 START_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-010-1-HP-0001 |
|
187 //! @file TestMultipleAlarmsSuite.script |
|
188 //! @SYMTestCaseID PIM-APPSRV-ALMSRV-PREQ1118-I-010-1-HP-0001 |
|
189 //! @SYMTestCaseDesc Associated Data – MIME - Single Alarms Mode |
|
190 //! @SYMFssID <App-Engines>/<CalInterimAPI>/EAS 1.0 |
|
191 //! @SYMTestStatus Implemented |
|
192 //! @SYMTestPriority High |
|
193 //! @SYMTestActions 1. Start the Alarm Alert Server without passing a value for aMaxAlarms value. |
|
194 //! 2. Create many calendar entries with alarms that have the same expiry time. |
|
195 //! Set the MIME associated data for all the calendar entries during creation. |
|
196 //! 3. Wait for the alarms to expire. |
|
197 //! 4. Retreive the Alarm Data from the Alert Server for the notifying alarm |
|
198 //! 5. Retrieve the corresponding Calendar entry’s details, e.g., GUID, recurrence id etc. |
|
199 //! from the Alarm Server for the notifying alarm |
|
200 //! 6. Retrieve the Calendar entriy using the information received. |
|
201 //! 7. Retrieve the associated data from the Calendar entry and compare with the original |
|
202 //! values used for setting them. |
|
203 //! @SYMTestExpectedResults The associated data is set and retrieved consistently. |
|
204 //! @SYMTestType CIT |
|
205 //! @SYMTestCaseDependencies The test can only run on a TEXTSHELL environment, as the Alert Server is loaded by the test code |
|
206 |
|
207 // Start alert server in single mode, create entries with imminent alarms and wait for the alarms to expire |
|
208 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCreateCalEntriesStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4 |
|
209 RUN_TEST_STEP -1 TestMultipleAlarmsServer TestWaitStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini wait_3mins |
|
210 |
|
211 // The first alarm has URL associated data. Clear it. So that the second one notifies |
|
212 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_1 |
|
213 DELAY 500 |
|
214 |
|
215 // Test the associated data of the notifying second alarm |
|
216 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry2 |
|
217 |
|
218 // Clear the second alarm. The third one too has MIME associated data. |
|
219 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAlarmClearStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini clear_2 |
|
220 DELAY 500 |
|
221 |
|
222 // Test the associated data of the notifying third alarm |
|
223 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestAssociatedDataStep Z:\TestData\Ini\TestMultipleAlarmsSuite.ini createcalentries_4.entry3 |
|
224 |
|
225 // Cleanup |
|
226 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestCleanupStep |
|
227 END_TESTCASE PIM-APPSRV-ALMSRV-PREQ1118-I-010-1-HP-0001 |
|
228 |
|
229 |
|
230 // Kill alert server thread |
|
231 RUN_TEST_STEP 100 TestMultipleAlarmsServer TestKillAlertServerStep |