0.7 Alpha5 – Email Test specification


Created On: Dec 6, 2006

Last Modified: Jan 4, 2006

Release version: Chandler 0.7 alpha5


Content

I. Introduction

 

·       Description

This document details the features for supporting email in Chandler. The goal for Preview is to be able to support small work group collaboration usage scenarios.

                        *  Allowing users to get data in and out of their Chandler world via Email

                        *  Allow users to share data with others via Email + Web access

                        *  Allow users to send sharing notifications via Email

 

Additionally the following 3 features are targeted to achieve this goal:

                        *  Pull down emails that have special Chandler headers

                        *  Subscribe to a select set of IMAP folders

                        *  Emailing items to collections

 

Date

Update Purpose

Modified By

Notes

Dec 6, 2006

First Draft

Aparna Kadakia

First draft of the test spec

 

II. Areas to be Tested

 

Module

Test Case id

Description

Status/ Remark

Email – receiving email in Chandler

TC0001

Configure IMAP and SMTP accounts and get email into Chandler

 

Email – Reply, Reply All and Forward

TC0002

Reply, Reply-All and Forward emails and check for the following.

1.     Reply updates the form and populates the TO field with the sender’s email address

2.     Reply All updates the form and populates the TO field with the sender’s email address and puts everyone else in  the CC field

3.     Forward blanks out the contents of the TO and CC fields and puts the user’s address in the From field

 

Email – Subscribing to IMAP folders

TC0003

Add email from other email clients into Chandler. Add messages to Dashboard tasklist and calendar.

 

Email – Supporting POP mail users

TC0004

Test for POP-only email accounts (details in the email spec on how to)

 

Email Forwarding & Stamping

TC0005

Test forwarding a message that is stamped as an event

1.     Forward fields are added to the Title and Notes

2.      Original event attached to the message as an .ics file

3.     User receiving this forwarded message in Chandler should see it rendered as an event in Chandler

4.     Non-Chandler users receiving this forward will see the ics attachment and event details on the Forwarded message

 

Email Forwarding & Stamping

TC0006

Test forwarding a message that is stamped as a task.

1.     Notes field should be updated with ‘Begin forwarded task:’

2.     User receiving the forward in Chandler should see it rendered as a task

 

Email Reply/Reply-All & Stamping

TC0007

Replying to a message stamped as a task/event

1.     Reply should not inherit task/event stamp of the original email

2.     Title and Notes field should be updated with  annotations mentioned in the spec

 

Sendingemail in Chandler

TC0008

TC0009

TC0010

TC0011

1.     Create a basic email in Chandler and send it to others

2.     Create an event on the calendar, stamp as email and add recipients to the addressing fields and Send

3.     Create a task, stamp as mail, add recipients and Send

4.     Create a new item,stamp as task and event and fill in the details, stamp as mail, add recipients and Send

 

Forwarding a message in Chandler

TC0012

TC0013

TC0014

1.     Select a message and click Forward. Add recipients to To, CC and BCC fields and send

2.     Forward a message in Chandler that is also stamped as an event/task. If the item is an event an ics file should be attached to the mssage. If the item is only a task it should be treated as a regular message

 

Replying to a message in Chandler

TC0015

TC0016

TC0017

TC0018

1.     Select a message and Click on Reply/Reply All

2.     Reply/Reply All to a message stamped as an event/task. If the message is an event, the event details should be copied in the reply section of the body of the email. If the message is a task, taskness of the item should NOT preserved

 

Receiving messages in Chandler

TC0019

1.     Chandler user receives email from other Chandler users.  It should show up in Chandler as an item stamped as mail with all relevant details

 

Receiving replied email

TC0020

Chandler user received replied email from another Chandler user.

1.     This should show up as item stamped as email

2.     Notes field should contain all the previous message info

 

Receiving replied email that is an invite

TC0021

TC0022

Email received in Chandler is an invite from another Chandler user. The event details should show up in the notes field . Stamp the message as an event and put it on Calendar.

Stamp the message as a task and put it on tasklist

 

Receiving forwarded email

TC0023

Email forwarded to the Chandler user from another Chandler user with an invite invite should 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

 


 

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

CATS, Record/Playback scripting

Data

Test Data needed to perform this module test

Personnel

QA Team, Dev Team, PPD Team

 

VI. Sign Off Approval

 

Role

Name

Program Manager

Sheila Mooney

Development Team

Brian Kirsch

UI Designer

Mimi Yin

QA Team

Dan Stenicke, Mikeal Rogers, Aparna Kadakia