From dev-return-25385-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Jun 09 09:41:05 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 65102 invoked from network); 9 Jun 2008 09:41:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jun 2008 09:41:04 -0000 Received: (qmail 54339 invoked by uid 500); 9 Jun 2008 09:41:07 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 54204 invoked by uid 500); 9 Jun 2008 09:41:07 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 54193 invoked by uid 99); 9 Jun 2008 09:41:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2008 02:41:07 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of pajbam@gmail.com designates 209.85.198.225 as permitted sender) Received: from [209.85.198.225] (HELO rv-out-0506.google.com) (209.85.198.225) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2008 09:40:16 +0000 Received: by rv-out-0506.google.com with SMTP id g37so2094723rvb.25 for ; Mon, 09 Jun 2008 02:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=lKUm0JEGScbmnPeqy4HZFBBomdv639nPxI6SduRV2rE=; b=rnSFK9N7V+RClA9afIS0LH0vzcbjR425TdtqfeyDbirP4ndlyiotowzDO+CNtQbEhG yeh/v0+wn+FVakDctz6xn5y7xtiIFaVSTq7joWb4BUCmOL+mDT/Nd7dIM62c3C5H1Bjc lXBIF9Dzac6omUGsifksIyOzt8LwYbRJO5lNY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=rzfm06VAbdwgx0MzksIFh0CHEPitqoHqYrxqZcIEIkyazwEGgY7zbOg5hLz4kETACS s3fG5EGDJSpHE5OLFHZJm3ljHzLfdip0uoVtaGdZFgPrmIHm9NsiWOsZtqXW6PAzdsbE hNRFyJgnLXP04TO0IZ4EcxrmGBsAqeCSaghVI= Received: by 10.141.33.21 with SMTP id l21mr1910752rvj.251.1213004433457; Mon, 09 Jun 2008 02:40:33 -0700 (PDT) Received: by 10.140.125.21 with HTTP; Mon, 9 Jun 2008 02:40:33 -0700 (PDT) Message-ID: <98d8c0860806090240r67c8a351wb07dda6f2c1b454a@mail.gmail.com> Date: Mon, 9 Jun 2008 11:40:33 +0200 From: "Pierre-Arnaud Marcelot" Sender: pajbam@gmail.com To: "Apache Directory Developers List" Subject: Re: [Studio] Framework for Integration Tests In-Reply-To: <484BD9A7.80507@apache.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_8886_1051691.1213004433444" References: <4826ECDC.9090809@apache.org> <484BD9A7.80507@apache.org> X-Google-Sender-Auth: 31d3140b1807d838 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_8886_1051691.1213004433444 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Stefan, This looks very slick!!! I'm going to test that... Thanks a lot, Pierre-Arnaud On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann wrote: > Hi, > > here is an update. > > I finished the integration testing framework for Studio and I'm going to > merge it into trunk soon. > > How to use it: > > 1) > Building Studio with maven from command line works like before, there is > no change to the current process. > > 2) > To run the integration test with maven from command line you need a > local installation of Eclipse and to set a eclipse-home property that > points to the Eclipse installation path, see [1] > > Then the tests could be started with > - Core tests only: mvn -Pintegration-core test > - UI tests only: mvn -Pintegration-ui test > - Core and UI tests: mvn -Pintegration-core,integration-ui test > > When running the tests all relevant plugins are copied from different > locations to the "test-sandbox": > - from a previous "mvn install" the complete Studio distribution > - from the resource folder the SWTBot plugins > - the test-integration-[core|ui] plugin itself > - some additional plugins from the local eclipse installation > Then the tests are lauched. > > 3) > For development you need to install the SWTBot plugins because the > test-integration-ui plugin depends on the SWTBot plugins [2]. I added > two launch configurations that could be used to launch the tests within > Eclipse. > > > The next step is to create some more tests :-) > > > Kind Regards, > Stefan > > > [1] http://directory.apache.org/studio/building.html > [2] http://directory.apache.org/studio/working.html > > > Stefan Seelmann wrote: > > Hi Dev, > > > > I am working on a framework for integration tests for studio. I added > > two plugins into my sandbox, one for core and one for UI tests. > > > > > > Core Integration Tests > > ---------------------- > > > > The core tests don't depend on any UI code, but on the Eclipse runtime. > > So it is necessary to startup Eclipse in headless mode, then it is > > possible to access things like Jobs, Preferences, etc. > > > > It is already possible to run these test within eclipse or from maven. > > However in the maven pom there are some fixed paths, I need to remove > > them, maybe I need some help from a maven guru. > > > > > > UI Integration Tests > > -------------------- > > > > For UI test I selected SWTBot (http://www.swtbot.org). There are still > > some features missing in the current version 0.2, but it looks very > > stable and the API is very easy to use. An UI-Recorder is under > > development. Last not least it is licenced under ASLv2. > > > > Here is an example how a test looks like: http://tinyurl.com/3j5ujs > > It opens the New Connection wizard, enters all connection parameters, > > does some checks and closes the connection. > > > > There are some open issues: > > > > 1) We have to extend SWTBot, I already contacted the author that I am > > interested in contributing. > > > > 2) SWTBot depends on many Eclipse plugins. To run the tests from maven > > we need to add about 50MB of plugins to our repository. Atm I just have > > a tarball containing all these plugins, but I don't want to commit them > > to svn. > > > > > > I'll keep you informed. > > > > > > Kind Regards, > > Stefan Seelmann > > > ------=_Part_8886_1051691.1213004433444 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Stefan,

This looks very slick!!!

I'm going to test that...

Thanks a lot,
Pierre-Arnaud

On Sun, Jun 8, 2008 at 3:07 PM, Stefan Seelmann <seelmann@apache.org> wrote:
Hi,

here is an update.

I finished the integration testing framework for Studio and I'm going to
merge it into trunk soon.

How to use it:

1)
Building Studio with maven from command line works like before, there is
no change to the current process.

2)
To run the integration test with maven from command line you need a
local installation of Eclipse and to set a eclipse-home property that
points to the Eclipse installation path, see [1]

Then the tests could be started with
- Core tests only:   mvn -Pintegration-core test
- UI tests only:     mvn -Pintegration-ui test
- Core and UI tests: mvn -Pintegration-core,integration-ui test

When running the tests all relevant plugins are copied from different
locations to the "test-sandbox":
- from a previous "mvn install" the complete Studio distribution
- from the resource folder the SWTBot plugins
- the test-integration-[core|ui] plugin itself
- some additional plugins from the local eclipse installation
Then the tests are lauched.

3)
For development you need to install the SWTBot plugins because the
test-integration-ui plugin depends on the SWTBot plugins [2]. I added
two launch configurations that could be used to launch the tests within
Eclipse.


The next step is to create some more tests :-)


Kind Regards,
Stefan


[1] http://directory.apache.org/studio/building.html
[2] http://directory.apache.org/studio/working.html


Stefan Seelmann wrote:
> Hi Dev,
>
> I am working on a framework for integration tests for studio. I added
> two plugins into my sandbox, one for core and one for UI tests.
>
>
> Core Integration Tests
> ----------------------
>
> The core tests don't depend on any UI code, but on the Eclipse runtime.
> So it is necessary to startup Eclipse in headless mode, then it is
> possible to access things like Jobs, Preferences, etc.
>
> It is already possible to run these test within eclipse or from maven.
> However in the maven pom there are some fixed paths, I need to remove
> them, maybe I need some help from a maven guru.
>
>
> UI Integration Tests
> --------------------
>
> For UI test I selected SWTBot (http://www.swtbot.org). There are still
> some features missing in the current version 0.2, but it looks very
> stable and the API is very easy to use. An UI-Recorder is under
> development. Last not least it is licenced under ASLv2.
>
> Here is an example how a test looks like: http://tinyurl.com/3j5ujs
> It opens the New Connection wizard, enters all connection parameters,
> does some checks and closes the connection.
>
> There are some open issues:
>
> 1) We have to extend SWTBot, I already contacted the author that I am
> interested in contributing.
>
> 2) SWTBot depends on many Eclipse plugins. To run the tests from maven
> we need to add about 50MB of plugins to our repository. Atm I just have
> a tarball containing all these plugins, but I don't want to commit them
> to svn.
>
>
> I'll keep you informed.
>
>
> Kind Regards,
> Stefan Seelmann



------=_Part_8886_1051691.1213004433444--