I hope to be able to finish MPT-4 in a the coming week.

mailbox-integration-tester is orphan for now (No web site, no release...) which is tricky since a lot time.

I wonder if mpt would be a good home for this orphan. mailbox-integration-tester is just a pratical usecase/application of the generic mpt library, so we could have a module in mpt like 'impl' and the first child on 'impl' would be the mailbox-integration-tester, which btw would be renamed 'james-imap' (it is about testing james imap with mpt).

Maybe you don't like it? Maybe you have a better idea? Just tell.

Thx, Eric


On 06/03/2013 05:39, Eric Charles wrote:
Hi,

MPT is a generic protocol test tool and mailbox-integration-tester aims
to test imap agains mailbox.

It's true that work need to be done to avoid class duplication (see
MPT-4), but in no way they should be merged.

MPT (generic protocol testing), Postage (specific james server testing)
need to be separated because they aim different goals.

Some work could be done to better integrate mailbox-integration-tester,
but this one depends on mailbox and imap. We put it apart to avoid the
circular reference.

Sorry to sound like relucent to any change, but this current project
split has not to change. It is not because they are 'test tools' that
they deserve to be integrated.

Thx, Eric

On 05/03/2013 23:36, Ioan Eugen Stan wrote:
Hello,

Releasing mailbox I spent some time looking MPT,
mailbox-integration-testing and Postage. They haven't received
attention in quite a while and I wish to see this changed. We need
more tests for James, especially integration testing.

Currently there seems to be no release for Postage and just a minor,
old release for MPT it's also true for mailbox-integration-testing.
Consuming SNAPSHOT versions is bad for health - you don't get a
history of artifacts that work together. I wish to provide releases
for MPT, Postage and Mailbox-integration-tester that work hand in hand
with James releases. This is one way to test our James releases and
have a history of artifafcts that work together.

MPT is needed for running mailbox-integration-testing and all of these
tools are email testing tools. They are a way to test James and James
components and some (Postage and MPT) can be used by others.

Following this rationale it makes sense to group them under a single
repo. I pledge to merge them and release a new version + website for
the new project and restore Jenkins builds for them.

Wdyt?


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to