| TestCase# | Module | Description | Status | Version |
|---|
| MigrationTest001 | Upgrade vanilla instance of Cosmo 0.6.1 to Cosmo 0.7 | 1. Create a vanilla instance of Cosmo 0.6.1.
2. Populate it with user data from Chandler Desktop and the Web UI
3. Run the migration script and upgrade it to 0.7
4. Without changing anything on the Chandler Desktop, sync the collections. Make changes to items and sync again.
5. Validate data on the migrated instance from Desktop and the Web UI. Mikeal will also run his automated scripts to validate the data between pre-migrated instance and the migrated instance. | Pass
Tested on fresh db instance on qacosmo | |
| MigrationTest002 | Upgrade production snapshot of Cosmo 0.6.1 to Cosmo 0.7 | 1. Clone the production instance of Hub on lab.osaf.us.
2. Testers will generate additional test data on it by pointing their "Chandler Server Sharing" account on Chandler Desktop to lab.osaf.us. Also generate data from the web UI.
3. Run the migration script and upgrade lab.osaf.us to Cosmo 0.7
4. Have testers continue pointing their "Chandler Sharing Sharing" to lab.osaf and continue publishing/sharing their calendars. | Pass
Tested as part of migration testing session on 8/10/2007 | |
| MigrationTest003 | Test recurrence modifications on the migrated data | 1. Generate events with Daily recurrences and make 'Just this event' modifications to it (by changing any of the fields in the detail view) and sync the collection. Validate the results show up correctly on the server using the web UI as well as from a Chandler Desktop that has subscribed to this collection.
2. Generate events with Weekly reccurence and make 'This and Future Events' modifications to it (by changing any of the fields in the detail view) and sync the changes. Validate the results from from the web UI as well as from a Chandler Desktop that has subscribed to this collection.
3. Generate events with Biweekly recurrence and make 'All Events' modifications to it (by changing any of the fields in the detail view) and sync the changes. Validate the results show up correctly on the server using the web UI as well as from a Chandler Desktop that has subscribed to this collection.
4. Generate events with Monthly recurrence and make 'Just this event' modification to it (by changing any of the fields in the detail view) and sync the changes. Validate the results show up correctly on the server using the web UI as well as from a Chandler Desktop that has subscribed to this collection.
5. Generate events with Yearly recurrence and make 'This and Future Events' modifications to it and sync the changes. Validate the results from from the web UI as well as from a Chandler Desktop that has subscribed to this collection. | Bug:10467
(Future) | |
| MigrationTest004 | Test Stamping and Unstamping on the migrated data | 1. Stamp a recurring series of events as mail. No recurrence dialog should pop. Sync the changes and validate from Chandler subscribed to this collection.
2. Stamp a recurring series of events as task. Choose 'Just this event' in the recurrence dialog. Sync changes and validate from Chandler subscribed to this collection.
3. Remove the event stamp on a recurring series. Choose 'All Events' in the recurrence dialog. Sync changes and validate from Chandler subscribed to this collection. | Passed | |
| MigrationTest005 | Test Triage Status on the migrated data | 1. Update triage status on non-recurring events in the Dashboard to Now, Done and Later. Sync changes and validate from Chandler subscribed to this collection if the triage status is indeed shared.
2. Update triage status of non-recurring events from Cosmo detail view and save the changes. Validate the changes from Desktop.
3. Update triage status on recurring events in the Dashboard to Now, Done and Later. Sync changes and validate from Chandler subscribed to this collection if the triage status is indeed shared.
4. Update triage status of recurring events from Cosmo detail view to Now, Done and Later. Sync changes and validate from Chandler subscribed to this collection if the triage status is indeed shared. | Passed | |
| MigrationTest006 | Test Removal and Deletion on the migrated data | 1. Remove events in a shared collection from Desktop - Just this event, All events and All future events. Sync changes and validate the result.
2. Remove events from the webUI - Just this event, All Events and All future events. Save changes and validate from Chandler that is subscribed to this collection. | Passed | Cosmo 5437
Chandler 15236
IE 7.0 |
| MigrationTest007 | Test updates from the web UI on the migrated data | Make updates to recurring events from the web UI and save the changes. Validate that the changes show up in Chandler that is subscribed to this collection. | Passed | |
| MigrationTest008 | Testing of events occuring in the right time range | This is the most important because the migration consists of going through all the events and re-indexing them using a different scheme than 0.6.1. Special attention should be paid to making sure events show. Based on the test data created as described above in Test Data section #2 verfiy the following:
1. Verify single event on Aug 10th at 9:00 AM titled 'Breakfast' shows up in Chandler and Web UI
2. Verify that a daily recurring series starting Aug 1st at 5 PM and never ending, titled 'Go Running' shows up correctly in Chandler and the web UI.
3. Verify a modification in the above series shows up for Aug 10th from 6 PM to 7 PM (just this event) on both Chandler and webUI
4. Verify that an all-day event shows up on Aug 9th in both Cosmo UI and Chandler.
5. Verify that for the recurring series starting Aug 1st at 3 PM titled 'Meet the Press', the duration is 2 hours starting Aug 10th | Passed | |
| MigrationTest009 | Test the fixes to those 26 items on Hub where event modifications exist in different collections than the parent item | 1. Create testdata as described in the Test Data section #1 above
2. From Chandler1, sync TestA? and verify you see the modification added to TestB? from Chandler2. | Pass  | Cosmo 5437
Chandler 15236
IE 7.0 |
| MigrationTest010 | Verify User Preferences stay in tact | Verify User Preferences stay in tact after migration. Currently, this is ensuring the "Advanced/Account Settings" checkbox is preserved and the UI does the right thing. | Confirmed by Jared 2007-08-13 against lab.osaf.us r5393. | |
| MigrationTest011 | Verify DAV files stay intact | Verify that the DAV files(webcal .ics files for instance) stay intact after migration | Automated, Passed | |
