0.7 Alpha5 – End User Test Scenarios


Created On: Jan 5, 2006

Last Modified: Jan 5, 2007

Release version: alpha5


Content

I. Introduction

 

·       Description

Date

Update Purpose

Modified By

Notes

Jan 6, 2007

First Draft

Aparna Kadakia

First draft of the test spec

 

II. Areas to be Tested

Module

Test Case id

Description

Status/ Remark

Sending an email invitation to a group

TC0001

1.     Create an event on the calendar.

2.     Add an agenda in the body by adding notes

3.     Stamp it as Communication and send it to users demo1, demo2, demo3 and demo4 by typing their email addresses in the TO field

4.     Select the email account to send the invitation From.

5.     Send the invite

 

Sharing the same event thru a shared collection.

TC0002

1.     Demo1 is sharing this event via a shared collection should see this newly created item in the Dashboard as Unread item and who column should display CR: Username(aka me)

 

Viewing my invitation

TC0003

Go to My Mail collection and view the invite. The following visual feedback should be seen:

1.     Send button is greyed out once the invitation is sent.

2.     Communication stamp in the markup changes to reflect it is a Sent communication

3.     Who column should display list of people invitation was sent to (demo1, demo2, demo3, demo4)

4.     The Send as: field is non-editable and Sent via : includes date/time information about when the email was sent

 

non-Chandler user receiving the invite and replying to it

TC0004

1.     Demo1 (non-Chandler user) receives the invitation in his email client with the event attached as an .ics file

2.     Demo1 manually adds the event to his calendar

3.     Demo1 hits reply to the email and types in some suggestions for the Agenda and hits Send

(Since the reply was sent from anotehr email client we will lose any special Chandler header information)

 

Me receiving the reply from non-chandler user

TC0005

1.     I receive the reply in Chandler as well as my email client

2.     In Chandler, reply appears as an unread item in Dashboard All and Mail app areas

3.     Communication stamp shows that the reply is an inbound unread email

4.     Who column shows who send the reply, FROM demo1

 

Non-Chandler user re-replies to the invite

TC0006

1.     Demo1 replies again to the invite with another suggestion

2.     The second reply appears in the All and Mail app areas as another new unread item.

 

Update the original invitation and add Demo1’s suggestions

TC0007

Edit the original invitation in the calendar or Dashboard to all Demo1’s suggestion. As soon as I make changes the following should happen

1.     Send button should reactivate and change to Update

2.     “Send By” field in detail view should become editable “Edited by: me” account pull down

3.     Clicking away from the item and then clicking back makes “Edited by: me” into non-editable text, “Edited by me on…”

4.     Clicking in the detail view to edit the item should reactivate the “Edit by me” pulldown.

5.     The Communication stamp should change to show that the invitation is a Draft of an Update.

 

Click Update to Send the invitation

TC0008

 

Click Update to send the invitation

1.     Update button in the toolbar grays out

2.     Communication stamp should change again to show invitation was updated

3.     “Edited by:” field should change into a non-editable Updated by: field that also includes date/time information about when the update was sent.

 

Another Chandler user updates the shared event

TC0009

 

Chandler user demo2 who is sharing the event with  me via a shared makes some changes of his own and updates the invitation.

Demo2 hits update:

1.     Communication stamp shows that the item is a Sent-Update. The From field shows that the item is still From me, To: demo1, demo2, demo3 and demo4

 

Updated Invitation in Chandler

TC0010

Demo2’s update re-enters the invitation item in the NOW section of my Dashboard.

1.     The communication stamp should show that the invitation item is an Unread-Inbound-Update.

2.     The who column should show that the invitation has been UP by demo2

3.     I should still show up in the From field of the invitation when I go to demo2’s update

 

Updating the shared event

TC0011

Demo3 updates the invitation via the shared collection. When demo3 hits update

1.     Communication stamp should show item as Sent-Update.

2.     From field should continue to show the item was sent From:me To: demo1, demo2, demo3 and demo4

 

Receiving the update to the shared event

TC0012

demo1, demo2, demo3 and demo4 receive demo3’s update in their respective email clients.

1.     It should appear in Now section of my Dashboard

2.     The communication stamp should show that the invitation item is an Unread-Inbound-Update

3.     Who column should show that the invitation was Up by demo3

4.     When I access demo3’s update, I should be listed on the recipient list. On the original invitation item I should still be in the From field.

 

Updating the event via the shared collection

TC0013

 

Demo1 edits the event invitation. Demo1 does not send out an update instead syncs the shared collection. The following should happen:

1.     demo1 should be able to edit the invitation even if she has read-only privileges via the shared collection, because she is an explicit recipient on the item

2.     When demo1 first aw the shared event/invitation, the Send button was disabled and Communication stamp displayed Inbound Unread status

3.     Demo1 received the update to the invitation via email. My update should re-center the invitation in the NOW section of her Dashboard.

4.     Once demo1 edited the invitaion, the Update button should get enabled for him and the Communication stamp should change to Draft-Update and text under the To: field should change to Edited by
: Demo1

5.     I should see “Edited by demo1..on” as non-editable text . If  I click in the detail view to make an edit, then the “Edited by Demo1 on..” non-editable text should turn into editable “Edited by: me” pulldown.

 

Receiving forwarded email

TC0023

\automatically be stamped as event and put on the calendar. Event details should be available in the Notes field

 

Non-Chandler user receiving email from Chandler user

TC0024

TC0025

Email received by non-Chandler user shows up as regular email.

If the item received is stamped as an event when it was sent by the Chandler user, the event details appear in the message body

 

Pulling in emails from Task, Event and Message IMAP folders

TC0026

Chandler user brings in items from Task, Event and Message IMAP folders, they should be stamped in Chandler as the appropriate kind.

 

Item byline – Created by …on

TC0027

Create an item in Chandler and do not edit it or stamp it to be addressed. The “Created by ..on” should appear in the detail view

 

Send as

TC0028

Create a note in Chandler and stamp it as a message to be sent out. The “Send As” by-line should appear in the detail view

 

Sent by…on

TC00029

Create a message in Chandler and send it. The “Sent by” by-line should appear in the detail view when the message has been sent for the first time

 

Edited by

TC0030

“Edited By” by-line should reflect the last person who edited the item regardless of whether it has been Sent/Updated or not.

Stamp and address the message and the “Edited By” field should be a pull-down menu to select the email account to send it from.

 

Edited by…on

TC0031

Edit an item in Chandler and click away. The “Edited by…on” by-line should appear in the detail view regardless of whether it has been Sent/Updated or not

 

Updated by..on

TC0032

“Updated by..on” should appear in the detail view and show the last person who updated the item once an item has been updated in Chandler

 

In Collection

TC0033

If you are in the TO, CC or BCC you should see the item in the In collection. Who the message is From, Edited or Updated should appear in the who column

 

Out Collection

TC0034

If you are in the From, Send Via, Sent By, Edited By, Updated By fields it should appear in the Out collection. And who the message is TO should appear in the who column

 

Updating item in read-only share

TC0035

1.     Subscribe to an event via a Read-only share

2.     Another user sends the same item via email

3.     The item should be editable by me now.

 

 

Module

Testcase ID

Description

Status/Bug

Personal Scheduling

TC0035

1.     Demo1 overlays her  Work and Home calendars to schedule a dinner party

2.     Demo1 then overlays husband demo2’s calendar to narrow down available times

3.     Demo1 sends out a message to friends with a list of 3-4 times and questions them about food preferences etc

4.     After receiving replies in her regular email client, Demo1 drags the final email she sends out confirming data, time, place and menu to her special changler events IMAP folder

The email, stamped as event shows up in her Chandler and she adds it to her Home calendar which she shares with spouse demo2

 

Workgroup Scheduling

TC0036

1.     Demo1 overlays her Work calendar with Demo3’s calendar and another Demo4’s calendar to figure out a good time for half day management offsite

2.     Demo1 sends out an email proposing a few good times

 

 

Collaborating on an item

TC0037

1.     Demo1 and Demo2 frame an email for a project launch mtg with details on goal of the mtg, agenda, attendees etc

2.     Demo1 sends out the first pass

3.     Demo2 adds comments to it

4.     Others respond via email with their comments

5.     Final draft gets sent out to entire working group

6.     All the while, the draft cycles in and out of Demo1 and Demo2’s shared Project collection in NOW section

 

Lightweight Collaboration via Cosmo : Shared Calendar

TC0038

1.     demo3 received a ticket to the shared office calendar weeks ago

2.     demo3 informs demo1 of upcoming vacation

3.     demo1 suggests to demo3 to update the info on the office calendar and supplies the r-w sharing ticket

4.     demo3 clicks on the ticket and goes to cosmo to enter his PTO

5.     demo3 uses the jump-to-date to jump to the right week

6.     demo3 d-clicks on the calendar canvas to enter his PTO dates

7.     when he is done, he clicks on the mail-to-link in the detail view of his PTO event item to send out an email to everyone in the office informing of his PTO dates

 

 

Heavy Collaboration via Cosmo : Shared Dashboard

TC0039

1.     demo1 and demo2 work together on a project task list and calendar

2.     demo1 asks demo2 to update the shared project collection with varoius tasks and milestones dates

3.     demo2 updates the collection via cosmo, where he has an account and subscribes to multiple collections

4.     demo1 goes back to the project later to Triage the new items demo2 has entered.

5.     Demo1 moves one of the tasks up in the queue for Bart to look at right away. She also writes him a note to start the task as soon as possible

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


 

III. Approach

State how testing will be done.

·     Black box testing and white box testing.

·    Functionality test will be done by a combination of automated scripts and manual steps.

·       Integration testing will be more end to end testing of the entire system.

 

IV. Resources

Description the resource needed to perform testing
 

Software/Tools

 

Data

Test Data needed to perform this module test

Personnel

QA Team

 

VI. Sign Off Approval

 

Role

Name

Program Manager

Sheila Mooney

UI Designer

Mimi Yin

QA Manager

Aparna Kadakia

QA Team

Dan Stenicke, Mikeal Rogers