I notice that the test just added below, and maybe other news ones
too, is explicitly creating a VMBroker in its setUp(). I forgot to
point out that in the refactored junit3 tests I recently committed, I
added a VMBrokerSetup class to do this. It's an instance of junit
TestSetup, which allows for once-per-test-class setup and teardown,
as opposed to the class setup and teardown that occur for every test
(i.e., TestSetup is like the junit4 @{Before,After}Class annotations).
To use it, just wrap the normal return from suite() with it, like this:
return new VMBrokerSetup(new junit.framework.TestSuite
(MapMessageTest.class));
The MapMessageTest class below already does this, which means that
its setUp() and tearDown() aren't really needed.
Martin, I can fix this test and any other new ones if you like, given
that I should have mentioned this earlier.
--steve
On Nov 22, 2006, at 12:46 PM, [EMAIL PROTECTED] wrote:
client/src/test/java/org/apache/qpid/test/unit/basic/
MapMessageTest.java
