Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates
 74.125.82.49 as permitted sender)
Message-ID: <54967E02.3050905@gmail.com>
Date: Sun, 21 Dec 2014 09:00:02 +0100
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: OSGi Tests for API
References: <54902E61.1020300@gmail.com> <54904CBD.7050702@stefan-seelmann.de>
 <5495B47E.6030302@stefan-seelmann.de>
In-Reply-To: <5495B47E.6030302@stefan-seelmann.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Le 20/12/14 18:40, Stefan Seelmann a écrit :
> On 12/16/2014 04:16 PM, Stefan Seelmann wrote:
>> re OSGi pax exam test:
>> That was a really good pointer, this tool is very helpful. It allows to
>> write tests that starts an OSGi container (Felix or Eclipse) and install
>> bundles. It is a bit tricky to configure because you need to define all
>> bundles it should install including transitive dependencies, but I found
>> a way to use the maven-dependency-plugin to generate a file containing
>> the dependencies (deps.txt) and then parse that file in the tests.
>> Currently its located in my sandbox, I create one test class for each
>> shared/api module, 50% is done, I'll do the rest within the next days.
>> Then I'd like to move it to shared project, either as its own
>> osgi-integrationtest module or if possible move each test directly to
>> the maven module it belongs to. Of course the same has to be done also
>> for ApacheDS.
> I'm finally done with creating the tests. The main thing they test is to
> start on OSGi container and install all bundles of the LDAP API to
> verify the the bundles are valid an and dependencies can be wired.
>
> I'll move it now from my sandbox to the API trunk as new maven module
> and make it part of the main build

Thanks a lot Stefan !