Feature Test Spec

5.0 Project (Sea-Monkey)
Mail and News Component
Folders: Subscribe (IMAP only)

Written by: Stacey Curtis

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

This test plan is broken into two sections. The first deals with subscription functionality while the preference to use subscription is turned on (in 4.5, this was represented by the preference to "show only subscribed folders" in the IMAP mail server Advanced tab preference dialog. The second deals with functionality while this preference is turned off.

With subscription turned on

.	Folder Type (tests defined in the following tables to be performed on these folder types as noted)	Notes	Expected Outcome (if not obvious)
1	top-level folder	.	.
2	subfolder in middle of hierarchy	.	.
3	subfolder at bottom of hierarchy (at least third level)	.	.
4	folder that contains many subfolders	.	.
5	many nested folders (20-30 deep) all at once	.	.
6	container (NoSelect) folder	Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a container folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder1 will be NoSelect.	.
7	message-only folder	Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a messages-only folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder2 will be messages only.	.
8	dual-use folder	Only relevant in server environments that support dual-use folders, like Messaging Server 4.0. To create a dual use folder, uncheck the preference "doesn't support dual-use folders" and use the standard New Folder dialog box.	.
9	folders with very long and very short names	Naming limitation: Win16: 8 characters Mac: 31 characters Unix: no limit Win32: 128 characters (? I think nbaca filed a bug on this)	.
10	folders with unusual ascii characters	Try several kinds.	.
11	IMAP folder	.	.
12	subfolder of Inbox	Only allowed for local inboxes and on some servers (e.g., Cyrus).	.
13	INBOX	.	.
14	sent folder	.	.
15	drafts folder	.	.
16	templates folder	.	.
17	subfolder of sent	.	.
18	subfolder of drafts	.	.
19	subfolder of templates	.	.
20	subfolder of trash (imap delete model)	Delete models may change in 5.0.	.
21	subfolder of trash (move-to-trash delete model)	.	.
22	subfolder of trash (really delete model)	.	.
23	Shared folder	.	.
24	Public folder	(if supported)	.
25	Folder with thousands of messages	.	.

.	Subscribe through the main Subscribe Dialog to the following types of folders	Notes	Expected Outcome (if not obvious)
1	Folder Type #1	.	.
2	Folder Type #2	.	.
3	Folder Type #3	.	.
4	Folder Type #4	.	.
5	Folder Type #5	.	.
6	Folder Type #6	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a container folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder1 will be NoSelect.	Subscribe should fail, if it is allowed at all.
7	Folder Type #7	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a messages-only folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder2 will be messages only.	.
8	Folder Type #8	IMAP only. Only relevant in server environments that support dual-use folders, like Messaging Server 4.0. To create a dual use folder, uncheck the preference "doesn't support dual-use folders" and use the standard New Folder dialog box.	.
9	Folder Type #9	Naming limitation: Win16: 8 characters Mac: 31 characters Unix: no limit Win32: 128 characters (? I think nbaca filed a bug on this)	.
10	Folder Type #10	Try several kinds.	.
11	Folder Type #11	.	.
12	Folder Type #12	Only allowed for local inboxes and on some servers (e.g., Cyrus).	.
13	Folder Type #13	.	.
14	Folder Type #14	.	.
15	Folder Type #15	.	.
16	Folder Type #16	.	.
17	Folder Type #17	.	.
18	Folder Type #18	.	.
19	Folder Type #19	.	.
20	Folder Type #20	Delete models may change in 5.0.	.
21	Folder Type #21	.	.
22	Folder Type #22	.	.
23	Folder Type #23	.	.
24	Folder Type #24	(if supported)	.
25	Folder Type #25	.	.

.	Unsubscribe through the main Subscribe Dialog to the following types of folders	Notes	Expected Outcome (if not obvious)
1	Folder Type #1	.	.
2	Folder Type #2	.	.
3	Folder Type #3	.	.
4	Folder Type #4	.	.
5	Folder Type #5	.	.
6	Folder Type #6	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a container folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder1 will be NoSelect.	.
7	Folder Type #7	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a messages-only folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder2 will be messages only.	.
8	Folder Type #8	IMAP only. Only relevant in server environments that support dual-use folders, like Messaging Server 4.0. To create a dual use folder, uncheck the preference "doesn't support dual-use folders" and use the standard New Folder dialog box.	.
9	Folder Type #9	Naming limitation: Win16: 8 characters Mac: 31 characters Unix: no limit Win32: 128 characters (? I think nbaca filed a bug on this)	.
10	Folder Type #10	Try several kinds.	.
11	Folder Type #11	.	.
12	Folder Type #12	Only allowed for local inboxes and on some servers (e.g., Cyrus).	.
13	Folder Type #13	.	The inbox can be unsubscribed to in a technical sense, but we will always continue to display it. There may be discoverability idiosyncracies if there are INBOXsubfolders, depending on the server. (If so, add to Interoperability test plan.)
14	Folder Type #14	.	.
15	Folder Type #15	.	.
16	Folder Type #16	.	.
17	Folder Type #17	.	.
18	Folder Type #18	.	.
19	Folder Type #19	.	.
20	Folder Type #20	Delete models may change in 5.0.	.
21	Folder Type #21	.	.
22	Folder Type #22	.	.
23	Folder Type #23	.	.
24	Folder Type #24	(if supported)	.
25	Folder Type #25	.	.

.	Subscribe through the main Subscribe Dialog to the following types of folders while using an account with an IMAPsubdirectory	Notes	Expected Outcome (if not obvious)
1	Folder Type #1	.	The message counts for all subscribed folders should be updated upon initial connect.
2	Folder Type #2	.	.
3	Folder Type #3	.	.
4	Folder Type #4	.	.
5	Folder Type #5	.	.
6	Folder Type #6	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a container folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder1 will be NoSelect.	Subscribe should fail, if it is allowed at all.
7	Folder Type #7	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a messages-only folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder2 will be messages only.	.
8	Folder Type #8	IMAP only. Only relevant in server environments that support dual-use folders, like Messaging Server 4.0. To create a dual use folder, uncheck the preference "doesn't support dual-use folders" and use the standard New Folder dialog box.	.
9	Folder Type #9	Naming limitation: Win16: 8 characters Mac: 31 characters Unix: no limit Win32: 128 characters (? I think nbaca filed a bug on this)	.
10	Folder Type #10	Try several kinds.	.
11	Folder Type #11	.	.
12	Folder Type #12	Only allowed for local inboxes and on some servers (e.g., Cyrus).	.
13	Folder Type #13	.	The inbox can be unsubscribed to in a technical sense, but we will always continue to display it. There may be discoverability idiosyncracies if there are INBOXsubfolders, depending on the server. (If so, add to Interoperability test plan.)
14	Folder Type #14	.	.
15	Folder Type #15	.	.
16	Folder Type #16	.	.
17	Folder Type #17	.	.
18	Folder Type #18	.	.
19	Folder Type #19	.	.
20	Folder Type #20	Delete models may change in 5.0.	.
21	Folder Type #21	.	.
22	Folder Type #22	.	.
23	Folder Type #23	.	.
24	Folder Type #24	(if supported)	.
25	Folder Type #25	.	.

.	Unsubscribe through the main Subscribe Dialog to the following types of folders while using an account with an IMAPsubdirectory	Notes	Expected Outcome (if not obvious)
1	Folder Type #1	.	.
2	Folder Type #2	.	.
3	Folder Type #3	.	.
4	Folder Type #4	.	.
5	Folder Type #5	.	.
6	Folder Type #6	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a container folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder1 will be NoSelect.	.
7	Folder Type #7	IMAP only. Only relevant in server environments that do not support dual-use folders (e.g., SIMS; UW using Unix mbox message storage type. Messaging Server does support both types). To create a messages-only folder on Unix, create a hierarchy all at once, e.g., "folder1/folder2". Folder2 will be messages only.	.
8	Folder Type #8	IMAP only. Only relevant in server environments that support dual-use folders, like Messaging Server 4.0. To create a dual use folder, uncheck the preference "doesn't support dual-use folders" and use the standard New Folder dialog box.	.
9	Folder Type #9	Naming limitation: Win16: 8 characters Mac: 31 characters Unix: no limit Win32: 128 characters (? I think nbaca filed a bug on this)	.
10	Folder Type #10	Try several kinds.	.
11	Folder Type #11	.	.
12	Folder Type #12	Only allowed for local inboxes and on some servers (e.g., Cyrus).	.
13	Folder Type #13	.	The inbox can be unsubscribed to in a technical sense, but we will always continue to display it. There may be discoverability idiosyncracies if there are INBOXsubfolders, depending on the server. (If so, add to Interoperability test plan.)
14	Folder Type #14	.	.
15	Folder Type #15	.	.
16	Folder Type #16	.	.
17	Folder Type #17	.	.
18	Folder Type #18	.	.
19	Folder Type #19	.	.
20	Folder Type #20	Delete models may change in 5.0.	.
21	Folder Type #21	.	.
22	Folder Type #22	.	.
23	Folder Type #23	.	.
24	Folder Type #24	(if supported)	.
25	Folder Type #25	.	.

	Perform these additional tasks	Notes	Expected Outcome (if not obvious)
1	Interrupt a subscribe and unsubscribe	.	The subscribe action may not take effect, but the application should not become unstable.
2	Upgrade from 4.0x	Some kind of subscription wizard should be present (Add more test cases about this wizard after it's defined).	.
3	Upgrade from 4.5	4.5 subscriptions should be honored.	.
4	Try each different access method for subscribing to folders	To be defined in the spec.	.
5	Rename a subscribed folder	.	Folder should still be subscribed
6	Delete a subscribed folder	.	Folder should be unsubscribed to.
7	Subscribe to a folder on a secure IMAP server	.	.
8	Subscribe to a folder while offline	.	Subscription should be carried out as soon as the user next connects to the mail server.
9	Subscribe to multiple, noncontiguous folders at once	.	.
10	Undo a folder subscription	This probably won't be a supported functionality, but check the spec when it comes out.	.
11	Change subscription status for a folder while another session holds a connection to that mailbox	.	Some actions should cause a re-reading of folder status and handling, like a collapse/expansion of the server name.
12	Go from using subscription to not using subscription, adding, moving, and deleting several folders while not using subscription, then go back to using subscription again	.	Once going back to using subscription, some folders may need to be resubscribed to, depending on what was done with them, but there should be no unexpected problems with folder existence or functionality.
13	Unsubscribe from a folder while it is selected	.	The next folder should become the selected folder, and the currently-viewed one should disappear from view.
14	Unsubscribe from the parent folder of a selected folder	.	No change in view should occur. The parent does not need to be subscribed in order to be displayed.
15	Unsubscribe from the child folder of a selected folder	.	No change in selection should occur, but the view will not show the child folder that was unsubscribed to.

With subscription turned off. This will be the less-common setting, but basic mail folder functionality should still work with it set as such.

.	.	Notes	Expected Outcome (if not obvious)
1	Create a top-level folder	.	.
2	Create a deep subfolder	.	.
3	Create a shared folder (if supported)	.	.
4	Rename a folder	.	.
5	Move a folder to a different part of the hierarchy	.	.
6	Delete a folder	.	.
7	Expand and collapse folders	.	.
8	File a message to an unsubscribed folder	.	.
9	Filter a message to an unsubscribed folder	.	.
10	Upgrade from 4.0x. Before opening Messenger in 5.0, set subscription setting to "off."	.	No subscription wizard should present itself.
11	Upgrade from 4.5, using a profile that already has subscription set to off.	.	Probably no subscription wizard should present itself, but the spec will ultimately define this.