protocol-tester -> mpt

[Robert Burrell Donkin <ro...@gmail.com>]

i've been working on the functional testing module extracted from
IMAP. this contains a lightweight scripting framework suitable for the
functional testing of the ASCII line based protocols common in mail.
the script contains a list of client sends and templated server
responses. the framework runs the client lines against a host system
and then compares the server lines received in response against the
templates (which may include regex's and so on).

for IMAP, the host system is programmatic, bypassing the socket work.
i've added a host system that runs against a port on a server. this
allows the scripts to be run against live systems running
independently of the test.

for IMAP, the framework is pure JUnit. functional tests extend an
abstract superclass which setups up and disposes of appropriate
fixtures. i'm adding an alternative way to run scripts that is more
suitable for running outside junit.

i plan to use this framework to create scripted smoke tests. the idea
is to run a basic script for each protocol against the running James
instance created during the smoke test. this should give confidence
that James is running and that the assembly works both for all
deployment types in the standard configuration.

opinions? objections? improvements?

anyway, i've decided that i think that protocol-tester is a bit of a
mouthful, and that i prefer the acronym MPT (Mail Protocol Tester).

opinions? objections? improvements?

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org