Migration Test Plan for Cosmo 0.6.1

High level test scenarios to be executed

1. Test case 1 - Upgrade vanilla instance of Cosmo 0.6.0.1 to Cosmo 0.6.1
   1. Create a vanilla instance of Cosmo 0.6.0.1.
   2. Populate it with user data from Chandler Desktop and the Web UI
   3. Run the migration script and upgrade it to 0.6.1.
   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.
2. Testcase 2 - Upgrade pre-populated instance of Cosmo 0.6.0.1 to Cosmo 0.6.1
   1. Clone the production instance of osaf.us on lab.osaf.us.
   2. Testers will generate additional test data on it by pointing their "WebDAV 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.6.1
   4. Have testers continue pointing their "WebDAV Sharing" to lab.osaf with /cosmo/dav/ in their path (/home is deprecated) and continue publishing/sharing their calendars. Note: This will continue to use webDAV protocol for sharing.
   5. To use the new morsecode protocol based sharing, testers will republish their collections to lab.osaf.us using the Chandler Hub Sharing account. That account path's field will be "/cosmo" (or "/" based on design discussion outcome)
   6. This will generate a new set of "pim" urls(read-only and read-write). These would need to be re-handed to all the sharers of that collection.
   7. Other testers should subscribe to these collections using the new urls and make changes to the collections and sync them.
   8. Also using these urls, access the collections from the web browsers and make changes to them.
3. Testcase 3 - 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.
4. Testcase 4 - 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.
5. Testcase 5 - Test Triage Status on the migrated data
   1. Update triage status on 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.
6. Testcase 6 - Test Removal and Deletion on the migrated data
   1. Remove events in a shared collection - 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.
7. Testcase 7 - Test updates from the web UI on the migrated data
   1. 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.

-- AparnaKadakia - 16 Apr 2007