You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Martin Ritchie <ri...@apache.org> on 2008/07/15 15:03:29 UTC

Java Test change

Hi,

Just wanted to give everyone a heads up that I've needed to make
changes in the tests to fix a few test failures.

The change to QpidTestCase etc have been discussed as part of
QPID-1079 and are assigned to Arnaud to to do:
http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Meeting+Minutes+2008-07-11

However, I'm trying to get trunk passing our tests(java and C++) 100%.

The code review change is to move QpidTestCase to a new shared module
that client can depend on for testing.

I would argue that the client module should not be dependant directly
or indirectly on the broker. So the large change I am looking to
commit is move all tests that utilise QpidTestCase to systests. This
will leave only pure unit tests in the client package.

Does anyone have any objections/thoughts?

Cheers

Martin

-- 
Martin Ritchie

Interesting example.

Posted by Carl Trieloff <cc...@redhat.com>.
I was playing with the check-ins that tross and gsim made recently. 
Thought it worth
a post to call out for others to play with.

QPID-1174 Remote Management Agent for management of external components

On trunk,

a.) go to in cpp/examples/qmf-agent

It allows any client to place management data into the same 
infrastructure as the broker
uses. really cool. this means that a client App can place it's mgnt 
commands and status along with
the broker info that it uses. You could even create links between say 
the client IP and
the managed objects running on that client.

There are still a few features needing implementation, but worth a look.

simply run the makefile. it is a 3 file example, that takes simple XML 
schema and generates everything

Start the broker, run qpidd-tool and look at schema and objects. then 
run the example and see the schema
and object appear in qpidd-tool.

b.) The second commit from gsim I am going to comment on, is that the 
broker now can support
plug-able exchanges. This means that any custom routing exchange can be 
supported in the
broker with the plug-in modules.

...
If anyone else writes or sees any other cool features of things as they 
go in, write a brief mail and copy
the user list :-)

Carl.


Interesting example.

Posted by Carl Trieloff <cc...@redhat.com>.
I was playing with the check-ins that tross and gsim made recently. 
Thought it worth
a post to call out for others to play with.

QPID-1174 Remote Management Agent for management of external components

On trunk,

a.) go to in cpp/examples/qmf-agent

It allows any client to place management data into the same 
infrastructure as the broker
uses. really cool. this means that a client App can place it's mgnt 
commands and status along with
the broker info that it uses. You could even create links between say 
the client IP and
the managed objects running on that client.

There are still a few features needing implementation, but worth a look.

simply run the makefile. it is a 3 file example, that takes simple XML 
schema and generates everything

Start the broker, run qpidd-tool and look at schema and objects. then 
run the example and see the schema
and object appear in qpidd-tool.

b.) The second commit from gsim I am going to comment on, is that the 
broker now can support
plug-able exchanges. This means that any custom routing exchange can be 
supported in the
broker with the plug-in modules.

...
If anyone else writes or sees any other cool features of things as they 
go in, write a brief mail and copy
the user list :-)

Carl.


Re: Java Test change

Posted by Rajith Attapattu <ra...@gmail.com>.
I am +1 with this change.
However we need to ensure that systests are run as part of a regular build.
(I believe this is currently the case).

Regards,

Rajith

On Tue, Jul 15, 2008 at 9:03 AM, Martin Ritchie <ri...@apache.org> wrote:

> Hi,
>
> Just wanted to give everyone a heads up that I've needed to make
> changes in the tests to fix a few test failures.
>
> The change to QpidTestCase etc have been discussed as part of
> QPID-1079 and are assigned to Arnaud to to do:
>
> http://cwiki.apache.org/confluence/display/qpid/Qpid+Java+Meeting+Minutes+2008-07-11
>
> However, I'm trying to get trunk passing our tests(java and C++) 100%.
>
> The code review change is to move QpidTestCase to a new shared module
> that client can depend on for testing.
>
> I would argue that the client module should not be dependant directly
> or indirectly on the broker. So the large change I am looking to
> commit is move all tests that utilise QpidTestCase to systests. This
> will leave only pure unit tests in the client package.
>
> Does anyone have any objections/thoughts?
>
> Cheers
>
> Martin
>
> --
> Martin Ritchie
>



-- 
Regards,

Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/