r9 - 09 Apr 2007 - 01:13:37 - PriscillaChungYou are here: OSAF >  Journal Web  >  ContributorNotes > PriscillaChungNotes > CosmoZeroDotSevenTestScenarios

Chandler Hub/Server 0.7 Test Scenarios

Overview

Chandler Server 0.7 is primarily work to build out the minimal set of features for the dashboard. In addition, we'll also be incorporating dogfood feedback from users currently using Chandler Hub. The project will be reviewed in terms of how it handles performance, stability, and features that prevent some users from dogfooding Chandler Hub. The examples listed are detailed specific for QA to use as test cases.

In addition to the 0.6.1 test scenarios, users for 0.7 test scenarios will be able to:

Subscribing to a collection by signing up for a new Chandler Hub account

  1. Ivan the Individual Contributor receives a read-only bookmarkable from Helen the Hub.
  2. From his desktop e-mail client, Ivan clicks 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 'Create an account' dialog pops up to enter in the user's account information. In the dialog, at the bottom, is a check box that says: [ √ ] I'd like to subscribe to this collection once I create my account. (default to: checkbox is checked)
  5. Once the information is entered, an e-mail is sent to his account to verify his account.
  6. Ivan goes into his e-mail client and clicks on the URL to verify his e-mail account is active.
  7. A new tab/window in the browser opens and displays the log in page.
  8. Ivan logs into his new Chandler Hub account, default to Helen's collection.

View/Edit collections without an account. Review particular Items on a list.

  1. Helen the Hub coordinates with her book club group about bringing food for a meeting.
  2. She sends out a read-write bookmarkable URL from Chandler Desktop to the book club members.
  3. Each book club member (CC users) clicks on the URL from their e-mail client, A new tab/window opens to Chandler Hub in the dashboard view.
  4. Each book club member is asked to add to the list of what what food items they are planning to bring.
  5. Book club members are able to do so without a Chandler Hub account.
  6. The day of the meeting, Helen reviews the list to see how many people are coming and write up a list of other preparations she might need to do or have people bring to the meeting.

Add an Event to a Collection: Edit Title, Location, Date/time, Notes field. Send e-mail out of band to confirm modification on the collection.

  1. Helen the Hub sends Ira the Individual Contributor her read-write bookmarkable URL to have him schedule a meeting with her.
  2. Bart is currently logged into Chandler Hub.
  3. Ira clicks on the URL from his desktop e-mail and launches Chandler Hub. The default view is the dashboard with a bunch of item in it.
  4. Ira clicks on the calendar view button and is able to see Helen's work week displayed in calendar view. This is visually easier for him to find an empty spot on the calendar.
  5. He is able to add an event, enters the title, location, date/time & notes field.
  6. He clicks on the 'E-mail this event' link 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.
  7. Ira is also able to modify/add a personal comment to the e-mail before he sends it back to Helen to notify her that he's added his event to her collection.

Add an Event to a Collection: Edit Title, Location, Date/time, Notes field. Send e-mail out of band to confirm modification on the collection. While CC user has an account and is in session on Chandler Hub

  1. Helen the Hub sends Bart the Busybody/Coordinator her read-write bookmarkable URL to have him schedule a meeting with her.
  2. Bart changes his view from Chandler Hub to view his e-mail client.
  3. Bart clicks on the bookmarkable URL. A new tab/window opens on the browser.
  4. Helen's work collection is viewed on the browser default to dashboard view.
  5. Bart is currently logged into Chandler Hub. Bart clicks on the '+' - 'Add to [name of collection] to my Chandler Account'.
  6. Dashboard view refreshes, default to Helen's work collection in the left pull down list. A message at the top of the alert message bar (yellow bar at the top) 'The [name of collection] collection has been added to your account.

Note: If Bart clicks back to the previous window of Chandler Hub (before he clicked on the bookmarkable URL) the collection will still be in the old state before adding the new collection. If he refreshed the browser or creates a new event and clicks 'Save', the browser will then refresh to the new state of his account and the alert message bar will appear with the message: 'The [name of collection] collection has been added to your account.

Currently in 0.6.1, the CC would need to enter in the ID/PW when clicking on the 'Add [collection name] to account'. In this workflow, we are eliminating the sign in step if the user is already logged into the account and is in session.

Browse collections: To switch between calendar and dashboard views with/without an account.

  1. Helen the Hub manages a collection for her daughter's dance recitals.
  2. She writes up the dates of her daughters dance recitals for the year and sends out the bookmarkable URL to her family from Chandler Desktop.
  3. She coordinates with her husband Bob who is bringing the costumes/tutus for their daughters and who is going to pick up and bring the in-laws to the dance recital.
  4. The day of the recital, Helen is unreachable at work. Bob clicks on the bookmarkable URL to Chandler Hub. He sees the dashboard and checks to see if he is tasked to bring the costumes or to pick up the in-laws this time.

Edit collections: To change triage status from the dashboard with/without and account. (This is similar checking off items from a shared task list.)

  1. Helen the Hub plans a holiday to London with her husband Bob.
  2. She creates a packing list of who is responsible for taking care of specific errands before they leave.
  3. Bob is at work and receives an e-mail from Helen. He clicks on a link to view the read-write collection list Helen created on Chandler Hub.
  4. As the travel dates grow closer, the items which were once marked as 'Later' are now marked as 'Now when Bob logs into his account.
  5. Bob goes through his list of errands to do before the trip and checks items off as 'Done' once he completes his tasks.
  6. He also bought tickets to HayFever at the Haymarket Theater Royal. He enters the item and stamps it as a calendar event to place on the calendar.

Edit collections: Add a 'Task' to a collection: Edit Title, Notes field. Send e-mail out of band to confirm modification on the collection.

  1. Helen the Hub sends Bart the Busybody/Coordinator her read-write bookmarkable URL to a work collection named 'SMASH 06'
  2. Bart receives an e-mail in his desktop e-mail application and clicks on the bookmarkable URL.
  3. Bart and Helen coordinate on an appropriate date and time in calendar view.
  4. Bart is also able to switch to dashboard view to review the list and see which items he is tasked to bring to the 'SMASH 06' meeting, ie. projector, tape recorders, large pads of paper, markers, etc. He may add some more additional items to the list and task Helen to bring them to the meeting.

When a Chandler Desktop user unpublishes (or deletes) 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. When he refreshes his browser, select from another collection back to 'SMASH 06', creates any events (on the dashboard or calendar) and clicks 'Save'—An an error message will appear in a dialog box, calendar background is faded to 50% grey, error message: This collection has been deleted and is no longer available.' [Okay]
  5. The calendar defaults back to the out of the box dashboard view. (Or next valid collection)

Note: See state map listed in 0.7 specification for other test scenarios.

  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'

All users with an account will always have an out of the box Chandler Hub collection, so even if a collection is deleted, there will always be one calendar collection in the pull down list in the left navigation. Bug#8722

Subscribing to the same collection (renamed collection)

  1. Helen the Hub sends out her bookmarkable URL to Iris the Individual Contributor.
  2. Iris already has an account on Chandler Hub. She clicks on Helen's bookmarkable URL and adds it to her account.
  3. Iris forgot she had already subscribed to this collection and had changed Helen's collection name from 'Work' to 'Helen's work' (display name) collection.
  4. When she logs into her account, an alert message bar will display at the top (in the yellow background). 'You have already subscribed to this collection. [Okay]'
  5. The message will also automatically disappear (roll up) after a few seconds.
  6. The collection should default to 'Helen's work' (the display name) renamed by Iris.

Note: If Iris did not rename the collection, when she clicks on subscribe [name of collection] collection to this account, it will still take her into Helen's collection after logging in and an alert message bar will also appear at the top (in a yellow background): 'You have already subscribed to this collection. [Okay]'. The message will also automatically disappear (roll up) after a few seconds.

Chandler Desktop users may set time zone information on a collection and Chandler Hub users are notified that the collection has time zone information.

  1. Helen the Hub is located in San Francisco and has sent her read-write bookmarkable URL from Chandler Desktop to Iris the Individual Contributor in New York.
  2. Helen currently has her time zone turned on to PST.
  3. When Iris receives Helen's e-mail, she will click on the URL and notice that the calendar she is viewing is set to PST in the time zone drop down.
  4. Iris has an account on Chandler Hub and decides to subscribe to Helen's collection.
  5. Iris clicks on the '+' add collection to her account. She logs into her account without time zones turned on.
  6. An alert message bar will appear (in the yellow background) at the top of the application to inform Iris that she is does not have time zones turned on. The message will read: "The 'Helen's work' collection contains time zone information. Turn on time zone information to view events and alarms correctly. [Ignore] | [Okay]"

Subscribe to Collection/Item via Atom feed (Will Atom be implemented by 0.7?)

  1. Brian receives Ted's read-write bookmarkable URL in his Google Mail (GMail).
  2. Brian would like to be able to view his calendar in his Google Calendar (GCal).
  3. He clicks on the URL and is directed to Chandler Hub.
  4. He selects 'and 'Other' from the 'Subscribe with…' pull down menu.
  5. A dialog box appears, defaulted to 'Other' in the pull down menu. He copies/pastes the Atom URL into the 'Add another calendar' section in GCal.
  6. Ted's collection appears as one of the calendars visible in Brian's GCal.
  7. When Ted updates and syncs his calendar information from Chandler Desktop, Brian's GCal will also be updated.

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. Create a new event item on the dashboard
  5. Edit an event item on the dashboard
  6. Log in to Chandler Hub once user puts in their ID/PW and clicks 'Okay'
  7. Switch from dashboard view to calendar view
  8. Double click to enter an event. Fill out detail view and 'Save'.
  9. Calendar view, user clicks forward two weeks forward and one week back. User adds an event on the calendar.
  10. 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.
  11. Hub user makes a change on a collection. Refresh the browser to view modification on the collection on Chandler Hub.
  12. 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 - 03 Apr 2007

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | 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.