You are currently viewing a snapshot of www.mozilla.org taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to www.mozilla.org, please file a bug.

Skip to main content

You are here: Mozilla MailNews Functional / UI Tests > Offline: Message Composition/Sending

Feature Test Spec: Mail and News Component

Mail and News Component: Offline: Message Composition/Sending

Written by Gary Chan

References:

UI and/or Functional Specifications: http://www.mozilla.org/mailnews/specs/offline/
Other: Laurel Carlson's original Offline message composition test plan: http://www.mozilla.org/quality/mailnews/tests/sea-mn-offline-comp.html

Disclaimer: This testplan is based on Laurel Carlson's original testplan originally written for Seamonkey. The wording and test plans will be very similar and changes to the test plan are made where appropriate.

The test cases outlined in this document are intended to cover overall mail and news message composition and send issues as they relate to offline usage. Some cases in this document may overlap with some sections in the separate offline:mail and offline:news functionality test specs, however this spec will provide the more comprehensive look at message content and handling.

Approximate number of test cases: 125 per platform or server configuration

Most of the cases below generally cover compose&send cases for messages covering mail and news and should be run against a variety of appropriate servers. For mail verification these cases should be run against both POP and IMAP servers. For news verification, these cases need to be run against secure and non-secure servers. Specific server cases/configurations will be outlined in separate test specs specific to mail and news functionality.

Overall testing instruction: each test should be run using both plain text and HTML composition windows unless otherwise noted. Each case should be checked for handling while in offline state and again when going back to online state.

  1. General UI tests: covered under separate test spec Offline: General UI.
  2. Basic UI and compose window access:
    1. In offline state, new message is available by all access methods:
      1. menu item
      2. toolbar button
      3. mnemonics aka access keys
      4. accelerators aka shortcut keys
    2. New message/Compose enabled and accessible when in offline state from:
      1. main mail window
        • no selection
        • mail selection
        • news server selection -- disabled in 4.x
        • newsgroup selection -- compose window should open addressed to newsgroup
      2. separate message window
          • mail message
          • news message --compose window should open addressed to newsgroup
      3. address book window
      4. account central 'compose message' link
      5. browser window
          • mail session open
          • mail session not open
    3. Reply commands disabled and inaccessible in offline state(nondownloaded mesgs) from:
      1. main mail window
        • single mail message selection
        • single news selection
        • enabled if you select a downloaded message (mail or news)
      2. separate message window
        • mail selection
        • news selection
        • enabled for single mail/news message selection that has been downloaded
    4. UI checks in the compose window:
      1. offline indicator should appear in compose window and toggle offline state when clicked
      2. offline indicator should change state when menu item is used to change state
      3. all panels (attachments, addressees, options) should be accessible in offline state
      4. all toolbar buttons should be accessible in offline state
      5. all tooltips for toolbar buttons should appear
      6. offline state: Send toolbar button should change appearance to Send Later state
      7. offline state: Send toolbar button default behavior is Send Later
      8. offline state: toolbar tip for 'Send later' button should display 'Send Later'
      9. online state: Send toolbar button appearance goes back to normal/Send state
      10. online state: Send toolbar default behavior goes back to Send Now
      11. online state: toolbar tip for 'Send' button should display 'Send '
  3. Basic composition tests using plain text and HTML compose windows:
    1. Create and Send (later) New Message
      1. mail message
        • verify in Unsent Messages folder
      2. news message
        • when newsgroup selected
        • with url typed in address line
        • cross-posted to a few groups
    2. Create messages using different address headers:
      1. To
      2. CC
      3. Bcc
      4. Reply to
      5. Follow-up to (Field allows only the word "poster" or newsgroup name. Email address format with @ sign not accepted.)
      6. NewsGroup
    3. Reply (to Sender, to Group) [only downloaded messages]
      1. general reply to:
        • mail message
        • news message
      2. reply to a mail message with reply-to header
      3. reply to a news message with follow-up to header, correct format for follow-up
        • group name
        • "poster"
    4. Reply All [only downloaded messages]
    5. Forward message [only downloaded messages]
      1. added attachments
        • text, html, jpeg, gif, doc, ppt, xls
        • different sized attachments
          • < 50kb
          • > 50kb
      2. web page in message
      3. signed
      4. encryption
    6. Message with no signature file or vcard
    7. Message with signature file
    8. Message with address card
    9. < TBD any other options which may wind up being integrated with compose window >
  4. Address Book compose
    1. Compose new message from address book when one address book is present (new msg context menu item on selection in address book will pre-address the message)
      • to a single addressee in address book
      • to multiple addressees
      • use mailing list
      • mix of mailing lists and address card in selection
    2. Compose new message from address book when more than one address book is present
      • to a single addressee in address book
      • to multiple addressees
      • use mailing list
      • mix of mailing lists and address card in selection
    3. Drag and drop from address book to an open compose window/addressee section
    4. < TBD any other options which may wind up being integrated with address book compose >
  5. Sending Mesgs
    1. Send from File Menu: Send Unsent Messages
    2. Send Via Preference: Ask me if I want to send my unsent messages
      • answer Send --> Mesgs are sent, Unsent Mesgs folder empty, online
      • answer Don't send --> Mesgs are not sent, still in Unsent mesgs folder, online
      • answer Cancel --> Mesg are not sent, still in Unsent mesgs folder, offline
    3. Send Via Preference: Automatically send my unsent mesgs
    4. Don't Send via Preference: Do not send my unsent messages
  6. Spell Check
    1. Spell check before send pref turned on
    2. Spell check manually (pref off)
    3. Spell with no errors
    4. Spell with errors, ignore
    5. Spell with errors, correct them
    6. Spell check, add text and spell check again
  7. Compose offline with attachments
    1. Microsoft Word
    2. Launch third party application
    3. File size greater than 4 meg
    4. Various graphic format (GIF/BMP/JPEG)
    5. Audio/Movie file
    6. Multiple attachments files
    7. 8-bit/MIME type
    8. Various priority
    9. Attach a web page
  8. Intelligent Send related tests
    1. Should behave the same offline as online. Please see the intelligent send test cases.
  9. Return Receipts (not currently implemented)
    1. Create message requesting Server receipt
    2. Create message requesting Display receipt
    3. Create message requesting both types receipt
  10. Drafts: check drafts are removed from draft folder upon send (when online) and check for erroneous multiple draft copies (note: to use any previous drafts that were created online in the online drafts folder, the user will have had to download that folder in order to access the folder offline)
    1. Save a draft: store drafts in local folder
    2. Save a draft: store drafts in online folder
    3. Open and Edit a draft: drafts stored locally
    4. Open and Edit a draft: drafts stored in online folder
    5. Open and Edit a previously saved draft that was created online: drafts stored in online folder
    6. store initial draft --> send
    7. edit open draft several times -->send
    8. open/edit/close/redit draft several times -->send
    9. draft with local attachment (files) -- check attachments are properly sent/received
    10. draft with online attachment (web page) --
      • try attaching web page when draft is open, since offline, can only attach a cached web page
      • try editing a draft which had previously (online) had web page attached
    11. Edit prefs to change where you store drafts
  11. Templates (note: to use any previous templates that were created online in the online template folder, the user will have had to download that folder in order to access the folder offline)
    1. Save a template: store templates in local folder
    2. Save a template: store templates in online folder
    3. Use a template stored locally
    4. Use a template stored in online folder
    5. Save a template with local attachment (files)
    6. Use a template which has previously saved local attachments (files)
    7. Save template with online attachment (web page)
    8. Use a template with online attachment (web page)
    9. Edit prefs to change where you store templates
  12. Copies
    Note: reference the pref setting in Mail&Newsaccount Settings|Account Name|Copies and Folders
    1. Verify copies are placed in appropriate folder when sent
      1. mail
      2. news
    2. Verify copies are sent via bcc to appropriate recipient upon send
      1. mail
      2. news
  13. Edit Message as New (note: will only work if the mesg has been downloaded for offline use)
    1. mail
    2. news: various destination groups
    3. authored by you
    4. authored by another user
    5. original messages having special headers set:
      • Reply-to
      • Followup-to
      • bcc
  14. Error condition composition tests using plain text and HTML compose windows:
    Note: in these cases it is anticipated that an error will occur when going online.
    1. News: create a new message and cross-post to groups covering more than one news server
    2. News: create a new message to bogus group
    3. News: create a message in the future
    4. News: incorrect format for follow-up header
    5. Reply to Group and Sender, newsgroup name invalid
    6. Forward message to invalid newsgroup
    7. Pinpoint addressing set for Directory when no directories available/offline (no LDAP should be allowed offline) Note: It is my understanding that offline LDAP will not be available, although this is subject to change
  15. Miscellaneous
    1. Send page from Browser in offline, no mailnews open
    2. MAPI Send when communicator offline
    3. Go online, connection interrupted. Verify error handling is smooth and no data/procedures lost or left hanging.