Manual tests in zero.mail.tests

These tests do not apply to the 1.0.0.x service stream

The zero.mail.tests project contains manual build verification tests for the functionality contained in the zero.mail.* components. These packages have unit tests that are executed as part of the build process and will have passed before each new build is published. However, the build verification tests must be executed manually to verify the basic aspects of the functionality that are more difficult to test in an automated fashion.

Preparation

To run this test case you will need to provide:

• A user ID and password for a test account on a POP3 server. Both SSL and non-SSL connections are supported to the POP3 server.
• The address of an SMTP server to which an e-mail can be sent to arrive in the POP3 account. The SMTP server must not require authentication or SSL.
• The test account mail box must be empty before the test is executed.

IMPORTANT: Do not point this test application at your personal POP3 folder or it will consume and destroy all your messages!

In order to execute the tests you will also need an installation of the WebSphere sMash CLI, SVN and a web browser. The main zero.mail.tests test application can be started as follows:

1. Install the WebSphere sMash CLI and prepare the a fresh shared repository.
2. Extract zero.mail.tests from the ASSEMBLE component in SVN.
3. If you are using the CLI (rather than Eclipse) to run the test then:
   1. Delete the unnecessary Junit test classes:
      • /java/zero/mail/impl directory and contents
      • /java/zero/mail/kicker directory and contents
      • /java/zero/mail/receiver directory and contents
      • /java/zero/mail/test/*.java source files
   2. Make sure that the /java/zero/mail/test/manual directory and contents are preserved.
   3. Run zero resolve and then zero compile for the appilcation.
4. Edit the test application's zero.config file and complete the configuration identified at the top of the file (do not modify the any other configuration):
   • The connection details of your test POP3 account: /config/mail/stores/manualTestStore
   • The address to which e-mails must be sent to arrive at the test POP3 account: /config/test/emailAddress
   • The address of your SMTP server: /config/connection/defaults/smtp/hostname
   • Uncomment the manual test kicker timer task configuration: /config/timer/tasks/manualTestKicker
   • If you are using a private POP3 server with a self-signed SSL certification, uncomment /config/mail/sslconfig and enter the client SSL configuration details.

Executing the tests

POP3 test

NOTE When run under the CLI, this test case will currently have ClassNotFoundExceptions in the log: SEVERE [ CWPZC3001E: Class not found: zero.mail.kicker.MailKickerTest$TestHandler ] These are due to the deleted Junit classes during preparation. The test will be refactored in the future to avoid these (http://www.projectzero.org/bugzilla/show_bug.cgi?id=6495). In the meantime, please excuse these SEVERE messages for now as they are benign to the manual test being carried out. However, do still report any other unexpected SEVERE messages you may see.

Both SSL and non-SSL connections are supported to the POP3 server. If you are able to test both, please repeat the test using first SSL and then non-SSL connections. If your POP3 server does not support both, please run the test using the configuration it supports.

1. Start the zero.mail.tests application, using zero start
2. TEST Review the application error log to confirm there are no untoward SEVERE messages.
3. Access the zero.mail.tests home page at http://localhost:8081/
4. Select POP3 test from the main menu and then Run test.
5. Review the displayed configuration. If necessary, stop the application, correct zero.config and start again.
6. Press the button to proceed to the next test step. The test e-mail will now be sent the SMTP status code 250 should be displayed.
7. Press the button to proceed to the next test step. If the mail message has not yet arrived, press the button again until it has.
8. TEST Confirm that "Test successful" is displayed on the browser.
9. Stop the zero.mail.tests application, using zero stop
10. TEST Review the application error log to confirm there are no untoward SEVERE messages.