the subject of functional (black box) testing has been on my mind recently. this arises from thinking about IMAP and about supporting multiple variations on the same code base (for example, multiple mail repositories).
a functional test suite is important for IMAP. IMHO simulating real life email clients is the best way to ensure that JAMES IMAP works. it would also be a reasonable gauge for performance and on implementation completeness. one way to integrate functional test suites into JAMES would be to build artifacts in modules (either new or create new directories in existing ones) containing the code required to perform function testing. implementations and deployments would perform their functional tests using these artifacts. opinions? other options? - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
