Re: [Bigdata-developers] [bigdata®] #72: Testing - Make changes to allow all tests of TestServiceStarter to pass when run using both ant & eclipse

[b. <no...@so...>]

#72: Testing - Make changes to allow all tests of TestServiceStarter to pass
when run using both ant & eclipse
--------------------------------+-------------------------------------------
 Reporter:  btmurphy            |       Owner:  btmurphy
     Type:  defect              |      Status:  new     
 Priority:  major               |   Milestone:          
Component:  Bigdata Federation  |     Version:          
 Keywords:                      |  
--------------------------------+-------------------------------------------

Comment(by btmurphy):

 To address the issues related to how the Zookeeper
 client and server handled in TestServiceStarter, the
 following changes are proposed for the
 TestServiceStarter.test_startServer test:

 1. Move the instantiation of the new serviceStarter
 to occur before the creation of the "physical services"
 znode.

 2. Change the creation of the "physical services" znode
 to take the serialized form of serviceStarter.UUID
 instead of an empty byte array.


 3. Change assertEquals(1, children.size()); to
 assertEquals(2, children.size());

 4. Prior to the call to ZNodeDeletedWatcher.awaitDelete,
 call com.bigdata.zookeeper.ZooHelper.destroyZNodes with
 a depth of 1. (Or simply remove the call to awaitDelete,
 and let tearDown remove the znodes.)

 5. In com.bigdata.jini.start.AbstractFedZooTestCase.setUp,
 remove the try-catch block in which
 zookeeper.create("/test", ... ) is called.

 6. In com.bigdata.jini.start.config.JiniServiceConfiguration,
 in the writeGroups and writeLocators methods, handle the
 case where there are more than one element in the set,
 by inserting a comma between each element that is written
 to the output file.

-- 
Ticket URL: <http://sourceforge.net/apps/trac/bigdata/ticket/72#comment:3>
bigdata® <http://www.bigdata.com/blog>
bigdata® is a scale-out storage and computing fabric supporting optional transactions, very high concurrency, and very high aggregate IO rates.