From dev-return-546-apmail-karaf-dev-archive=karaf.apache.org@karaf.apache.org Fri Nov 26 13:09:27 2010 Return-Path: Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: (qmail 49617 invoked from network); 26 Nov 2010 13:09:27 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Nov 2010 13:09:27 -0000 Received: (qmail 22895 invoked by uid 500); 26 Nov 2010 13:09:27 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 22835 invoked by uid 500); 26 Nov 2010 13:09:25 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 22827 invoked by uid 99); 26 Nov 2010 13:09:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 13:09:25 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gnodet@gmail.com designates 74.125.82.46 as permitted sender) Received: from [74.125.82.46] (HELO mail-ww0-f46.google.com) (74.125.82.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Nov 2010 13:09:20 +0000 Received: by wwb28 with SMTP id 28so1246284wwb.3 for ; Fri, 26 Nov 2010 05:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=DAnoq3Jdp1Wc7Wx+1aPpXcm3dldYGAf20O7ETqienz0=; b=NbukrL4sxTekbJONScRg3zNyGrJwJem6EiQc8NEWpMnlMmBb926T1Kmz1iyl70Oc1d nScpC8DY3V9KBAzWiYrhAjOyi2aFv3rB122jv9MNkdVFsBnVPwel2LdktpzkOESmu8dv cbXDX2kFtUvT3bJwcsrck5YOJqLVZCp5qcI7c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tr64pizefnx26rqTGa9Tei+88QlSXvdGAqBeHvCRgZ2GeBCJoYXHQw23uLhYmDsUoc Dyn50L6mj/t+8jJjoJMLgle9cd18+Yh1iegC3/ytN/q/xjJj/K3ktlti3ZW/Ox/habDR wNa6QiV1vsTkOLqdvBOtaRSJoiRRYttUSutMc= MIME-Version: 1.0 Received: by 10.227.133.15 with SMTP id d15mr2360546wbt.37.1290776938362; Fri, 26 Nov 2010 05:08:58 -0800 (PST) Received: by 10.227.132.139 with HTTP; Fri, 26 Nov 2010 05:08:58 -0800 (PST) In-Reply-To: References: Date: Fri, 26 Nov 2010 14:08:58 +0100 Message-ID: Subject: Re: [DISCUSS] Karaf distribution testing From: Guillaume Nodet To: dev@karaf.apache.org Content-Type: text/plain; charset=ISO-8859-1 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. 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 > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com