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 > Mail & News: Page Source (related to mail)

Feature Test Spec: Mail and News Component

Mail and News Component: Page Source (related to mail)

Written by Peter Mock
Updated by Esther Goes

References

UI Specification:
Other: Dogbert's New Message (Compose)
Gromit's Mail Compose Specification

Description: These tests applies to Mail and News.

  1. Start a new Plain Text message
    1. Type in some text then send the message.
      1. Verify the Content-Type is "text/plain; charset=us-ascii"
      2. Verify that there is no HTML comment tags
      3. Verify the time stamp from the server is correct. Example: 
        Received: from netscape.com ([208.12.40.134]) by dredd.mcom.com
(Netscape Messaging Server 4.0) with ESMTP id F57EWQ01.8R8 for 
<pmock@netscape.com>; Thu, 7 Jan 1999 11:17:14 -0800
      4. Verify the time zone is correct for your region
      5. Verify the date stamp for the message that is used to displayed in the Thread pane is correct. Example: Date: Thu, 07 Jan 1999 11:17:13 -0800
      6. Verify the X-Mailer information is correct for the platform. Example: X-Mailer: Mozilla 4.5 [en]C-NSCP (Win98; U)
      7. Verify the X-Accept-Language is correct. Example: X-Accept-Language: en
      8. Verify the MIME-Verision is correct. Example: MIME-Version: 1.0
      9. Verify the message contents is in Plain Text and not HTML
    2. Type in some rich text and the characters are not extended. Verify the Content-Transfer-Encoding is 7bit
    3. Type in some rich text with extended characters and send message. Verify the Content-Transfer-Encoding is 8bit
  2. Start with a new HTML message
    1. Type in some rich text then send the message.
      1. Verify the Content-Type is "text/html; charset=us-ascii"
      2. Verify the HTML comment read, "<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 transitional//EN"
      3. Verify the time stamp from the server is correct. Example: 
        Received: from netscape.com ([208.12.40.134]) by dredd.mcom.com
(Netscape Messaging Server 4.0) with ESMTP id F57EWQ01.8R8 for 
<pmock@netscape.com>; Thu, 7 Jan 1999 11:17:14 -0800
      4. Verify the time zone is correct for your region
      5. Verify the date stamp for the message that is used to displayed in the Thread pane is correct. Example: Date: Thu, 07 Jan 1999 11:17:13 -0800
      6. Verify the X-Mailer information is correct for the platform. Example: X-Mailer: Mozilla 4.5 [en]C-NSCP (Win98; U)
      7. Verify the X-Accept-Language is correct. Example: X-Accept-Language: en
      8. Verify the MIME-Verision is correct. Example: MIME-Version: 1.0
      9. Verify the message contents is in HTML and not plain text.
    2. Type in some rich text and the characters are not extended. Verify the Content-Transfer-Encoding is 7bit
    3. Type in some rich text with extended characters and send message. Verify the Content-Transfer-Encoding is 7bit
  3. Using Intelligent Send
    1. Send a new message as Plain Text only
      1. Verify the message is displayed as Plain Text
      2. Verify the message Content-Type is "text/plain; charset=us-ascii"
      3. Verify the message Content-Transfer-Encoding is 7 bit for non-extended character and 8 bit for any extended character.
    2. Send a new message as HTML only
      1. Verify the message is displayed as HTML
      2. Verify the message Content-Type is "text/html; charset=us-ascii"
      3. Verify the message Content-Transfer-Encoding is always 7 bit no matter if the message contains extended characters.
    1. Send a message as Plain Text and HTML
      1. Verify the message is displayed with a Plain Text and HTML sections for the message portion.
      2. Verify the Content-Type is correct. It will vary depending on the message content and whether it contains any attachments.