IMAP Interoperability Feature Test Plan

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
IMAP: Interoperability

Written by: Stacey Curtis

References:
UI Specification: TBD
Other: TBD
Approx. number of test cases: Lots

Description: This test plan includes test cases for IMAP functionalities of the mail5 client while running against different types of IMAP servers. The table below reflects the servers that we plan to test against. In an ideal world, we would be able to test all listed functionalities against all servers in a completed product.

This test plan is comprised of five nearly-identical sections. Each section contains the test cases for one server type (each version of a given server type does not have its own test plan section). I decided to break up the test plan in this way because not uncommonly, the "notes" and/or "expected outcome" columns are significantly different for different servers. Although the test plan sections have many redundancies, this structure will allow the tester to execute a single section at a time against a given server without picking and choosing from many detailed notes, and perhaps to more easily track the completion of testing for each server type in the test plan section itself. I've turned the server-specific details in each section a nifty shade of red to make them easy to spot.

The five sections are: Netscape Messaging Server, SIMS, University of Washington, Microsoft Exchange, and Cyrus.

More Information

RFCs

IMAP logging

Test Servers

About IMAP Logging with Netscape's mozilla mail application:

IMAP logging is turned on in the following manner:

Windows 95/98: Insert the following lines into your autoexec.bat file:

Set NSPR_LOG_MODULES=IMAP:5
Set NSPR_LOG_FILE=[filename]

Make sure the path to the file you specify really exists. Reboot.

WinNT: Use the Control Panel | System | Environment tool to set the PRLOG env variables as above.

Mac: TBD.

Unix (e.g., for csh shells):,

setenv NSPR_LOG_MODULES IMAP:5
setenv NSPR_LOG_FILE [filename]

(It's easiest to add those lines to your ~/.cshrc file.)

The 5 in the first variable above specifies the level of logging you want - the lower the number the less logging happens. (Temporarily, though, until further notice, it's going to use PR_LOG_ALWAYS.)

The numbers are supposed to have the following meaning:

PR_LOG_NONE = 0, /* nothing */
PR_LOG_ALWAYS = 1, /* always printed */
PR_LOG_ERROR = 2, /* error messages */
PR_LOG_WARNING = 3, /* warning messages */
PR_LOG_DEBUG = 4, /* debug messages */

On all platforms, the log is written over every time you re-launch Communicator.

Test Servers

	IMAP servers	Notes	Expected Outcome (if not obvious)
1	Netscape Messaging Server 4.1	TBD	.
2	Netscape Messaging Server 4.03	Example (example servers available only within Netscape; sorry!): tintin	.
3	Netscape Messaging Server 3.5	Example: poisonivy (internal to Netscape)	.
4	Netscape Messaging Server 3.0	Example: zia (internal to Netscape)	.
5	SIMS 3.5	Example: none.	.
6	SIMS 4.0	Example: none.	.
7	University of Washington v. 11.241	Example: wensleydale (internal to Netscape)	.
8	University of Washington v. 12.247	Example: UW's external server. See test accounts page (internal to Netscape).	.
9	Microsoft Exchange v. 5.5	Example: poisonoak (internal to Netscape)	.
10	Cyrus v. 1.5.2	Example: buggy (internal to Netscape) Note: Cyrus's public IMAP server is more recent: 1.5.21.	.
11	Innosoft v. PMDF5.2	Example: See internal test accounts page specified above.	.

Note: For another test that should be done, but which may not manifest against any of the commonly-supported servers, see Bugsplat bug 351810 (internal: old bug tracking system). We may need an ISOCOR server to test it, as it requires an unsolicited FETCH response from the server.