r17 - 12 Jul 2007 - 08:35:16 - MimiYinYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > CosmoZeroDotSixDotOneTestScenarios

Cosmo 0.6.1 Test Scenarios

Overview

Cosmo 0.6.1 is a infrastructure release, specifically focused on the sharing format between Chandler Desktop and Chandler Server. The test scenarios listed here are no different from that outlined in the Cosmo 0.6 spec workflows for the Casual Collaborator. The examples listed are detailed specific for QA to use as test cases.

Background Reading

Workflows based on the Cosmo 0.6 tenet

To allow OSAF employees to use the web application (with or) without a Cosmo account to enter their PTO (paid time off) on the OSAF office calendar.

  1. The OSAF office calendar collection is published by Morgen using Chandler Desktop. The collection is published to Chandler Hub (osaf.us).
  2. The read-write bookmarkable URL is sent from Chandler Desktop to all employees at OSAF.
  3. The policy at OSAF is when someone takes a vacation, they send an e-mail out to everyone to let them know about their PTO.
  4. Andi in an employee at OSAF. He is going to France on holiday from June 10-28.
  5. When he receives the e-mail from Morgen on his desktop email application, he clicks on the URL sent from Chandler Desktop.
  6. Andi's web browser will open and the OSAF office calendar will appear.
  7. Andi bookmarks the URL so that he will not have to dig up Morgen's e-mail next time he goes off on holiday.
  8. He enters in the date 6/10/2007 in the 'Jump to date' field, clicks on the 'Go' button.
  9. The calendar jumps to the week of June 10-16, and the date.
  10. Andi double clicks on June 10th in the 'All day' event area at the top of the application.
  11. An event is created and the 'Title' field is highlighted in the detail view for Andi to fill out the event information.
  12. Andi fills out the form elements in the detail view and clicks on the 'save' button to save his calendar event.
  13. Andi click on the 'E-mail this event' link on the top right area in the detail view.
  14. Andi's desktop e-mail client opens, and an email is pre-populated with the name of the collection name and the title of the event in the subject field. In the body of the e-mail the title, time zone information, starts and end time, type of event, and recurrence information is pre-populated in the body of the e-mail.
  15. Andi can modify the e-mail or send it out to all employees at OSAF.
  16. Morgen syncs chandler desktop, and views Andi's PTO in his dashboard.
  17. Andi goes back to Chandler Hub, finds his event and modifies the time he is leaving and adds contact information in the description field.
  18. Morgen syncs the desktop and sees Andi's changes.

Additional Workflows for Cosmo 0.6 and 0.6.1

Subscribe to a collection in Chandler Hub sent from a Chandler Desktop User

  1. Helen the Hub creates a work calendar in Chandler Desktop.
  2. Helen publishes this collection on Chandler Hub.
  3. She sends Bart the Busy Body/Coordinator (Casual Collaborator) her read-write bookmarkable URL (of her work collection) from Chandler Desktop.
  4. Bart does not use Chandler Desktop but already has an account on Chandler Hub. He receives Helen's work read-write bookmarkable URL in GMail, a web based e-mail client.
  5. Bart click on the URL and opens a new tab/window from his browser.
  6. He notices the '+' (Add this collection to your Cosmo account) button and clicks on it.
  7. A dialog pops up to log into his Cosmo account.
  8. Once he is logged in, Helen's work collection is added to the list of collections in Bart's Cosmo account.

Sign up for a new Cosmo account

  1. Ivan the Individual Contributor receives a read-only bookmarkable from Helen the Hub.
  2. From his desktop e-mail client, Ivan click on the URL and opens a new tab/window from his browser.
  3. Ivan sees Helen's work calendar and clicks on the 'Sign up for an account' button/graphic.
  4. A dialog pops up to enter in the user's account information.
  5. Once the information is entered, an e-mail is sent to his account to verify his account. Ivan goes into his e-mail client and displays the log in page.
  6. A new tab/window in the browser opens and asks Ivan to log into his Cosmo account.
  7. Ivan logs into his new Cosmo account.
  8. *Note:*Currently in 0.6.1, In order for Ivan to subscribe to Helen's collection, Ivan would then need to go back to the previous window w/ Helen's the read-only calendar collection or back to his e-mail to click on the read-only bookmarkable from Helen and follow the workflow above (Subscribe to a collection sent from a Chandler Desktop User). This is specified differently in workflow B in Cosmo 0.6 specification. We'll be working towards a better user experience in future releases.

Chandler to Chandler Desktop sharing

  1. Helen the Hub creates a work calendar in Chandler Desktop.
  2. Helen publishes this collection on Chandler Hub.
  3. She sends Henry (Hub) her read-write bookmarkable URL (of her work collection) from Chandler Desktop.
  4. Henry manages his calendar+task information (PIM) on Chandler Desktop. When he receives Helen's e-mail, he clicks on the bookmarkable URL and his web browser automatically launches and goes to Helen's collection on Chandler Hub.
  5. He clicks on the 'Subscribe with…' drop down list and selects, 'Subscribes with Chandler'.
  6. The 'Collection Details' dialog pops up with information about the collection. Henry copies and pastes the URL from the 'Collection Address' field to Chandler desktop, under the Share menu/Subscribe field. Note this is the sharing format work done in 0.6.1
  7. Helen's work collection should appear in Henry's list on the left side bar of Chandler Desktop.
  8. When Helen makes an update to her work calendar and syncs (on Chandler Desktop), Henry will also see the changes in Chandler Desktop when it syncs.

iCal calendar (other CalDAV calendars) publish to Chandler Server sharing (repeat this scenario w/ Sunbird)

  1. Henry the Hub creates a home calendar in iCal.
  2. Henry publishes his home calendar collection to Chandler Hub.
  3. He sends e-mails his iCal URL to Helen the Hub.
  4. Helen copies and pastes the URL (.ics) into the 'subscribe' dialog in Chandler Desktop
  5. When Henry makes an update to his home calendar and syncs, Helen will also see the changes in Chandler Desktop when it syncs.

Subscribe to a collection in iCal (or some other DAV calendar client) sent from a Chandler Desktop User

  1. Helen the Hub creates a work calendar in Chandler Desktop.
  2. Helen publishes this collection on Chandler Hub.
  3. She sends Isabella the Individual Contributor her read-write bookmarkable URL (of her work collection) from Chandler Desktop.
  4. Isabella manages her calendar information on iCal. When she receives Helen's e-mail, she clicks on the bookmarkable URL and her web browser automatically launches and goes to Helen's collection on Chandler Hub.
  5. She clicks on the 'Subscribe with…' drop down list and selects, 'Subscribes with iCal'.
  6. The 'Collection Details' dialog pops up with information about the collection. Isabella copies and pastes the URL from the 'Collection Address' field to her 'Subscribe' dialog in iCal. Note: Currently there is an issue with iCal 2.x that it does not recognize 'https://' and unless the 's' is removed. See Cosmo FAQ
  7. Helen's work collection should appear in Isabella's iCal. Note: in iCal, even w/ a read-write collection, it will only display as a read-only collection.
  8. When Helen makes an update to her work calendar and Chandler Desktop syncs, Isabella will see the changes in Helen's work collection when she syncs her iCal.

Subscribe to a collection in using a a feed reader.

  1. Brian receives Ted's read-write bookmarkable URL in his GMail.
  2. He clicks on the ticket and selects 'Feed Reader' from the 'Subscribe with…' drop down list.
  3. Brian then copies and pastes the URL into his favorite feed reader client. Note. FF now has a setting that when you click on a feed link it will pop up a window to allow the user to select the feed reader from the browser. See Bug#8329
  4. Everytime Ted updates his work calendar, Brian is updated by viewing his feed reader.

When a Chandler Desktop user unpublish (or delete) a collection while the Chandler Hub user is viewing the deleted collection (logged in).

  1. Bart has kept his browser open to Chandler Hub.
  2. He is currently viewing Helen's old collection, 'SMASH 06'.
  3. Helen the Hub deletes 'SMASH 06' from Chandler Desktop. She sends e-mail to notify users sharing the collection to update to her new 'SMASH 07' collection.
  4. He refreshes his browser, selects from another collection back to 'SMASH 06'
  5. He creates any events and clicks 'Save'—An an error message will appear on the canvas: 'This collection has been deleted and is no longer available.'
  6. The calendar collection defaults back to the out of the box calendar collection.

Note:

  1. If Bart is viewing a bookmarkable URL, the calendar will default to the error message: 'This collection has been deleted and is no longer available. Please check back with the person who originally published the collection. [Okay]'
  2. Redirect to landing page: 'cosmo.osafoundation.org'

  1. If Bart goes back to his e-mail and click on the bookmarkable URL, it will launch an error message page same as above: 'This collection has been deleted and is no longer available. Please check back with the person who originally published the collection. [Okay]'
  2. Redirect to landing page: 'cosmo.osafoundation.org'

In addition, this workflow will appear slightly different in 0.7. All users with an account will always have an out of the box Chandler Hub account, so even if a collection is deleted, there will always be one calendar collection in the pull down list in the left navigation. Bug#8385

Adding a recurring event in Chandler Hub (test with both log on and with the bookmarkable URL)

  1. Helen the Hub sends out her work collection to Bart the Busybody/Coordinator
  2. Bart checks his e-mail and clicks on the bookmarkable URL
  3. Bart creates a couple of meetings, one bi-weekly meeting on Thursdays at 2PM. A weekly meeting on Tuesday at 10AM. A monthly meeting on Monday morning at 11AM.
  4. On the third Thursday the month, the Thursday meeting at 2PM would need to change the title/description of the event and to change the time from 2PM to 10AM.
  5. Helen deletes one event (only the first Tuesday meeting in April).


Top ten use cases for performance testing

  1. Once a user clicks on a bookmarkable URL, how long will it take for Chandler Hub to display? Test w/ Office Calendar
  2. Once a user clicks on a bookmarkable URL, how long will it take for Chandler Hub to display? Test w/Hub's calendar (either Katie, Sheila, Ted etc.)
  3. CC user bookmarks the URL sent from Hub user. Closes Chandler Hub window. CC user goes back to bookmarkable URL by clicking on the bookmark in the browser.
  4. Double click to enter an event. Fill out detail view and 'Save'.
  5. Log in to Chandler Hub once user puts in their ID/PW and clicks 'Okay'
  6. Modify an event, in the detail view, click 'Save'.
  7. Calendar view, user clicks forward two weeks forward and one week back. User adds an event on the calendar, click 'Save'.
  8. Sign up for an account—e-mail verification, user clicks on the e-mail link and check the performance on how long it takes for the browser to load Chandler Hub.
  9. Hub user makes a change on a collection. Refresh the browser to view modification on the collection on Chandler Hub.
  10. In the calendar view, user 'jumps to date' 6 months from today on the 'Office Calendar' collection. Then test again with w/ a Hub's calendar collection.

-- PriscillaChung - 31 Mar 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r17 < r16 < r15 < r14 < r13 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.