The Mozilla
Organization
At A Glance
Feedback
Get Involved
Newsgroups
License Terms
Newsbot
Developer Docs
Roadmap
Projects
Ports
Module Owners
Hacking
Get the Source
Build It
Testing
Download
Bugzilla
Bug Writing
Tools
View Source
Tree Status
New Checkins
Submit A Bug
FAQ
Search

Feature Test Spec

5.0 Project (Sea-Monkey)
Mail and News Component
Folders: Special

Written by: Stacey Curtis

References:
UI Specification:
Other:
Approx. number of test cases: 486


Description: Special Folders (Drafts, Sent, Templates, Trash). This test plan will be broken down into four sections: one for each of the types of special folder. Each of the test cases below (with the exception of the few cases identified as movemail only) should be tested twice: once when the special folder is stored on an IMAP server, and once when the folder is stored locally.

Message Types/Conditions (these are to be tested as called for in the tables that follow)
Notes
 Expected Outcome (if not obvious)
1 Plain text message . .
2 Plain text message with attachment, vcard, signature, signed and encrypted . .
3 Plain text message with a cc:, bcc:, group:, reply-to:, followup-to: . .
4 Plain text message that is uuencoded . .
5 Plain text message that has a return receipt request . .
6 Plain text message that is a reply of another message . .
7 Plain text message that is a reply of another message that has already been deleted . .
8 Plain text message with different priorities . .
9 Plain text message that has some required fields not yet filled in (further definition will require more spec/UI detail) .
10 HTML message with attachment, vcard, signature, signed and encrypted . .
11 HTML message with a cc:, bcc:, group:, reply-to:, followup-to: . .
12 HTML message that is uuencoded . .
13 HTML message that has a return receipt request . .
14 HTML message that is a reply of another message . .
15 HTML message that is a reply of another message that has already been deleted . .
16 HTML message with different priorities . .
17 HTML message that has some required fields not yet filled in . .
18 HTML message with images, URLS, and tables . .
19 HTML message with a MAPI-type attachment e.g., Word .
20 HTML message with a Java attachment . .

. Draft Folder Creation
Notes
Expected Outcome (if not obvious)
1 Specify the Draft folder location before opening Messenger for the first time. . Depending on the preference specified, the Draft folder should be automatically created either on the IMAP server or locally. If subscription is turned on (IMAPpreference), the folder should also be automatically subscribed to.
2 Specify the Draft folder location after opening Messenger but before accessing any mail servers. . .
3 Change the Draft folder location (from IMAP to Local or vice versa) . .
4 Change the Draft folder location back to the original location after having changed it. . .
5 If the Draft folder in either location is deletable in 5.0, delete it, then respecify it in that location. . The Drafts folder should be recreated (and, if applicable, resubscribed to) in the designated location.
6 Specify the user's IMAP mail directory to be other than the default. Common with UW servers. The Drafts folder should be created in the specified subdirectory.
7 Confirm the column headers displayed when the Draft folder is selected . .
8 Use a Draft folder while using movemail. . .

. Save as Draft
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Open Draft Message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Edit/Resave Draft Message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 For this section, change some text, conditions, and attachments, and resave the message. Most of this type of testing will be done by the Compose tester, but try to get through a good variety of edits. .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Delete Draft message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Send Draft message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . Ensure that the message is received as expected.
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Template Folder Creation
Notes
Expected Outcome (if not obvious)
1 Specify the Template folder location before opening Messenger for the first time. . Depending on the preference specified, the Template folder should be automatically created either on the IMAP server or locally. If subscription is turned on (IMAPpreference), the folder should also be automatically subscribed to.
2 Specify the Template folder location after opening Messenger but before accessing any mail servers. . .
3 Change the Template folder location (from IMAP to Local or vice versa) . .
4 Change the Template folder location back to the original location after having changed it. . .
5 If the Template folder in either location is deletable in 5.0, delete it, then respecify it in that location. . The Template folder should be recreated (and, if applicable, resubscribed to) in the designated location.
6 Specify the user's IMAP mail directory to be other than the default. Common with UW servers. The Template folder should be created (and, if applicable, resubscribed to) in the specified subdirectory.
7 Confirm the column headers displayed when the Templates folder is selected . .
8 Use a Template folder while using movemail. . .

. Save as Template
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Open Template Message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Edit/Resave Template Message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 For this section, change some text, conditions, and attachments, and resave the message. Most of this type of testing will be done by the Compose tester, but try to get through a good variety of edits. .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Delete Template message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . .
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Send Template message
Notes
Expected Outcome (if not obvious)
1 Type/condition #1 . Ensure that the message is received as expected.
2 Type/condition #2 . .
3 Type/condition #3 . .
4 Type/condition #4 . .
5 Type/condition #5 . .
6 Type/condition #6 . .
7 Type/condition #7 . .
8 Type/condition #8 . .
9 Type/condition #9 . .
10 Type/condition #10 . .
11 Type/condition #11 . .
12 Type/condition #12 . .
13 Type/condition #13 . .
14 Type/condition #14 . .
15 Type/condition #15 . .
16 Type/condition #16 . .
17 Type/condition #17 . .
18 Type/condition #18 . .
19 Type/condition #19 . .
20 Type/condition #20 . .

. Trash Folder
Notes
Expected Outcome (if not obvious)
1 Specify the Trash folder location before opening Messenger for the first time. . Depending on the preference specified, the Trash folder should be automatically created either on the IMAP server or locally. If subscription is turned on (IMAPpreference), the folder should also be automatically subscribed to.
2 Specify the Trash folder location after opening Messenger but before accessing any mail servers. . .
3 Change the Trash folder location (from IMAP to Local or vice versa) . .
4 Change the Trash folder location back to the original location after having changed it. . .
5 If the Trash folder in either location is deletable in 5.0, delete it, then respecify it in that location. . The Trash folder should be recreated (and, if applicable, resubscribed to) in the designated location.
6 Specify the user's IMAP mail directory to be other than the default. IMAP only. This configuration is common with UW servers. The Trash folder should be created in the IMAP directory.
7 Empty the Trash folder . The messages in the Trash folder should disappear and the folder should be compacted (IMAP and POP).
8 Confirm that the Trash folder can hold subfolders . .
9 Empty the Trash folder while it is selected . .
10 Empty the Trash folder while it contains a subfolder . .
11 Empty the Trash folder while one of its subfolders is the selected folder . .
12 Fill the Trash folder with thousands of messages . There should be no realistic upper limit on the number of messages the folder can contain.
13 Empty the Trash folder when it contains thousands of messages. . .
14 Confirm the column headers displayed when the Trash folder is selected . .
15 Use a Trash folder while using movemail. . .

. Sent Folder
Notes
Expected Outcome (if not obvious)
1 Specify the Sent folder location before opening Messenger for the first time. . Depending on the preference specified, the Sent folder should be automatically created either on the IMAP server or locally. If subscription is turned on (IMAPpreference), the folder should also be automatically subscribed to.
2 Specify the Sent folder location after opening Messenger but before accessing any mail servers. . .
3 Change the Sent folder location (from IMAP to Local or vice versa) . .
4 Change the Sent folder location back to the original location after having changed it. . .
5 If the Sent folder in either location is deletable in 5.0, delete it, then respecify it in that location. . The Sent folder should be recreated (and, if applicable, resubscribed to) in the designated location.
6 Specify the user's IMAP mail directory to be other than the default. IMAP only. This configuration is common with UW servers. The Sent folder should be created (and, if applicable, resubscribed to) in the IMAP directory.
8 Confirm that the Sent folder can hold subfolders . .
12 Fill the Sent folder with thousands of messages . There should be no realistic upper limit on the number of messages the folder can contain.
13 Confirm the column headers displayed when the Sent folder is selected. . .
14 Use a Sent folder while using movemail. . .
Copyright © 1998-1999 The Mozilla Organization.
Last modified April 1, 1999.