karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [DISCUSS] Karaf distribution testing
Date Fri, 26 Nov 2010 13:15:17 GMT
Thanks for that Guillaume.

We start with this and extend it.


On 11/26/2010 02:08 PM, Guillaume Nodet wrote:
> I've just committed a first test to see what's possible.
> It's really easy and only unzip the distribution, start karaf, wait
> for it to be started, run the stop script, and wait for evrything to
> shutdown.
> We can build on that and add more tests for various scripts and
> expected behavior.
> We could even add some for demos if that makes sense ...
> Feel free to hack on that ....
> See http://svn.apache.org/viewvc?view=revision&revision=1039339
> The actual test is available at
> http://svn.apache.org/viewvc/karaf/trunk/itests/kittests/src/test/java/org/apache/karaf/kittests/KitTest.java?view=markup
> On Mon, Nov 22, 2010 at 21:39, Jamie G.<jamie.goodyear@gmail.com>  wrote:
>> Hi All,
>> After encountering some release issues with the Apache Karaf 2.1.x
>> branch it has come to the forefront that we need to improve our
>> distribution testing. The main target of distribution testing we need
>> is to try out the various scripts we include in each distribution kit.
>> These tests would ideally cover un-archiving the kit, launch
>> bin/karaf, bin/start, bin/stop, bin/client, and bin/admin.
>> To help build these tests we can make use of bin/client to help make
>> ssh connections (send commands), and admin/core process library to
>> control the various processed involved in each test. To uncompress the
>> different distributions we could use commons-compress or just ask
>> maven to do the work for us (this is done in the Servicemix NMR&
>> Features projects).
>> Regardless of which tools we use to build these tests a certain amount
>> of CI will be required. Most of us currently use unix based systems,
>> so Windows based issues for example tend to sneak by. Hopefully by
>> having such tests automated we'll be able to catch distribution issues
>> earlier.
>> Cheers,
>> Jamie

View raw message