r16 - 02 Mar 2007 - 13:17:05 - DanSteinickeYou are here: OSAF > Journal Web > ContributorNotes > DanSteinicke > DanSteinicke200702091
| Module | Test Case id | Description | Status/ Remark | |
| Email – receiving email in Chandler | TC0001 | Configure IMAP and SMTP accounts and get email into Chandler | passing r13260 | |
| Email – Reply | TC0002 | updates the form and populates the TO field with the sender’s email address | passing r13260 | |
| Email – Reply All | TC0003 | Updates the form and populates the TO field with the sender’s email address and puts everyone else in the CC field | passing r13260 | |
| Email – Forward | TC0004 | Blanks out the contents of the TO and CC fields and puts the user’s address in the From field | passing r13260 | |
| Email - Creating IMAP folders | TCXXXX | Click the 'add' Chandler folders button in the Account Prefs Incoming mail dialog. In another email client check that Chandler mail, Chandler Tasks and Chandler events folders appear | passing r13260 | |
| Email - Removing IMAP folders | TCXXXX | Click the 'remove' Chandler folders button in the Account Prefs Incoming mail dialog and in another mail client check that the folders added in the previous test case are removed | passing r13260 | |
| Email – IMAP Folders | TC0007 | Check that emails sent from another Chandler automatically show up in the dashboard and In collections stamped as mail | passing r13298 | |
| Email – IMAP Folders | TC0008 | In another mail app check that dragging a email not originating from another Chandler to the Chandler Mail IMAP folder causes the item to appear in Chandlers dashboard after a sync | passing r13260 | |
| Email – IMAP Folders | TC0009 | In another mail app check that dragging mail into Chandler Tasks IMAP folder causes it to show up in Chandlers dashboard as mail stamped as a task | passing r13260 | |
| Email – IMAP Folders | TC0010 | In another mail app check that dragging mail into Chandler Events IMAP folder causes the item to show up in Chandlers dashboard as a mail stamped as an event | passing r13260 | |
| Email – IMAP Folders | TC0011 | if a message contains attachments (EIM, ICS) that Chandler can process. The stamping info in the attachments takes precedence over what folder it was dragged into, that is a message containing an .ics will still be stamped as an event even if it is dragged into the Chandler Tasks or Chandler Mail folders over the users choice of which custom Chandler folder is selected. | passing r13267 for .ics attachment EIM attachments not testable yet r13267 | |
| Email – Supporting Chandler folders for POP mail users | TC0012 | Test for POP-only email accounts (details in the email spec on how to) | This feature has not been implemented (r13267). Is likely to be dropped from preview | |
| Email Forwarding & Stamping | TC0013 | Test forwarding a message that is stamped as an event Chandler to Chandler * Forward fields are added to the Title and Notes * Original event attached to the message as an .ics file * User receiving this forwarded message in Chandler should see it rendered as an event in Chandler * Non-Chandler users receiving this forward will see the ics attachment and event details as text in the body of the Forwarded message | passing r13267 | |
| Email Forwarding & Stamping | TC0014 | Test forwarding a message that is stamped as an event Chandler to Non-Chandler email client Non-Chandler users receiving this forward will see the ics attachment and event details on the Forwarded message | passing r13267 | |
| Email Forwarding & Stamping | TC0015 | Test forwarding a message that is stamped as a task. Notes field should be updated with ‘Begin forwarded task:’User receiving the forward in Chandler should see it rendered as a task | Blocked by  Bug #8190 | |
| Email Reply/Reply-All & Stamping | TC0016 | Replying to a message stamped as a task/event Reply should not inherit task/event stamp of the original emailTitle and Notes field should be updated with * xxx wrote on... to the top of the Notes field, 2 line breaks down from the top of the Notes field * fields from the detail view should be added to the text body: TITLE at LOCATION from/on DATE/TIME OPTIONAL TIME ZONE until OPTIONAL RECURRENCE END-DATE with a > token at the start of each line; | Replying to task stamped msg blocked by Bug #8190 | |
| Sending email in Chandler | TC0017 | Create a basic email in Chandler and send it to others | passing r13298 | |
| Sending email in Chandler | TC0018 | Create an event on the calendar, stamp as email and add recipients to the addressing fields and Send | passing r13278 | |
| Sending email in Chandler | TC0019 | Create a task, stamp as mail, add recipients and Send | Blocked by Bug #8190 | |
| Sending email in Chandler | TC0020 | Create a new item,stamp as task and event and fill in the details, stamp as mail, add recipients and Send | fails Bug #7764 | |
| Forwarding a message in Chandler | TC0021 | Select a message and click Forward. Add recipients to To and send | passing r13308 | |
| Forwarding a message in Chandler | TC0022 | Forward a msg stamped as a task, msg should be received as normal email (no ics or indication of taskness) | Replying to task stamped msg blocked by Bug #8190 | |
| Forwarding a message in Chandler | TC0023 | Forward a msg stamped as an event, when received an .ics file should be attached | passing r13308 | |
| Forwarding a message in Chandler | TC0024 | Repeat above (fwd) tests with all combinations of CC , BCC fields filled in with single/ multiple entries | passing r13298 stamped as mail only 1 address in each To, CC, BCC stamped as mail and event one address in each of To, CC, BCC Forwarding a task stamped msg blocked by Bug #8190 | |
| Replying to a message in Chandler | TC0025 | Select a unstamped message and Click on Reply and send | passing r13298 | |
| Replying to a message in Chandler | TC0026 | Reply to an mail stamped as a event, when received email should contain event details in text body | passing r13308 | |
| Replying to a message in Chandler | TC0027 | Reply to an event stamped as a task, when received email should not contain indications of taskness | I think Bug #8190 means there will be indications of taskness | |
| Replying to a message in Chandler | TC0028 | Repeat above (reply) tests using reply all | ||
| Replying to a message in Chandler | TC0029 | Repeat above (reply/ reply all) tests with all combinations of CC , BCC fields filled in with single/ multiple entries | ||
| Receiving messages in Chandler | TC0030 | Chandler user receives email from other Chandler users. It should show up in Chandler as an item stamped as mail with all relevant details | passing r13308 | |
| Receiving replied email | TC0031 | Chandler user received replied email from another Chandler user. This should show up as item stamped as email Notes field should contain all the previous message info | passing r13308 | |
| Receiving replied email that is an invite | TC0032 | Receive an invite from another Chandler. The event stamp should be retained and information preserved in detail view | passing r13329 | |
| Receiving forwarded email | TC0033 | Receive an invite forwarded from another Chandler user. Check that invite retains its event stamp and information in detail view is preserved | passing r13329 | |
| Non-Chandler user receiving email from Chandler user | TC0034 | 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 | passing r13329 | |
| Pulling in emails from Task, Event and Message IMAP folders | TC0035 | Chandler user brings in items from Task, Event and Message IMAP folders, they should be stamped in Chandler as the appropriate kind. | passing r13329 | |
| Item byline – Created by …on | TC0036 | 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 | passing r13329 | |
| Send as | TC0037 | 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 | passing r13329 | |
| Sent by…on | TC0038 | 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 | passing r13329 | |
| Edited by | TC0039 | “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. | Feature not yet implemented Bug #7363 | |
| Edited by…on | TC0040 | 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 | Feature not yet implemented Bug #7363 | |
| Updated by..on | TC0041 | “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 | Feature not yet implemented Bug #7363 | |
| In Collection | TC0042 | 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 | Fails to display in Inbox when "me" address in BBC Bug #8232 | |
| Out Collection | TC0043 | 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 | working for From rest not yet implemented | |
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.
See list of page contributors for attributions.