qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Conway <acon...@redhat.com>
Subject Re: Create qpid-interop sub-project
Date Thu, 14 May 2015 19:56:52 GMT
On Thu, 2015-05-14 at 08:14 -0400, Rafael Schloming wrote:
> Hi Kim,
> How exactly are you picturing the dependencies working here? Is this
> project going to be an assemblage of other projects, i.e. an integration
> test suite, or do you intend other projects to depend on this one and pull
> it in as part of their standard test suite?

I sent a detailed email about this - I think the trick is to install the
projects you want to test and build/run interop against them. By using
multiple install trees you can do cross-tests between different

>     proton-new <-------> proton-old
> I was able to do this:
>     proton-new <-------> dumb-mimic
> Where dumb-mimic is constructed by simply pumping out the same bytes
> observed from proton-old "in the wild."

Dumb-mimic is very useful for in-project testing (I did it in the
proton/tests/interop also.) I think the new interop tests are for
inter-project and inter-version testing. Problems found by interop
testing could be fed back as component regression tests using dumb-mimic
as you describe.

> I guess the upshot is that I can see how an integration framework that
> makes it easy to assemble and test live endpoints could be useful, but I
> don't think it actually buys you interop testing without a fair amount of
> manual work, i.e. you would need to stand the thing up somewhere in a CI
> system and run it constantly in a configuration that tests current versions
> against prior ones.

Single version proton-proton tests do not warrant a new test framework,
but we have a bunch of other projects and they need to talk to each
other.  A complete cross-version matrix is not feasible but just testing
all the project trunks against each other and against all the last
releases would go a long way.

> --Rafael
> On Wed, May 13, 2015 at 10:52 AM, Kim van der Riet <kim.vdriet@redhat.com>
> wrote:
> > I would like to propose and start a vote on asking infa@ to create a Qpid
> > subproject called qpid-interop. The requested infrastructure will be
> > limited to a git repo "qpid-interop" and a JIRA. All mailing and other
> > communication would be performed through regular users@ and dev@ mailing
> > lists.
> >
> > What is qpid-interop?
> >
> > This project is a test framework for interoperability between various AMQP
> > 1.0 clients. This includes, but is not limited to Qpid clients such as
> > qpid-jms, proton python, c, c++ etc.  The tests will run on any running
> > AMQP broker, and should include:
> >
> > * AMQP types
> > * AMQP functionality
> > * Transactions
> >
> > The idea is to have a top-level control program which sends its requests
> > to specific clients to send or receive data to a "shim" or light-weight
> > send and receive client through the command-line and which performs narrow
> > specific tasks.  The process for editing and adding both clients and tests
> > will be well-documented so that anyone from the community can add to them.
> >
> > I have already have some code in Python and docs to share which focus on
> > the first category above, the AMQP types. This is intended to illustrate
> > the idea and open the way for others to contribute both other type tests
> > and other clients. These need a landing place, and I am proposing to start
> > by asking infra to create a git repo and a JIRA, and I'll check in the code
> > and docs I have so far.
> >
> > I would welcome your comments and ideas, and hope to start a vote in a day
> > or so.
> >
> > Kim van der Riet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message