Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 54651 invoked from network); 11 Feb 2009 00:11:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Feb 2009 00:11:47 -0000 Received: (qmail 58673 invoked by uid 500); 11 Feb 2009 00:11:43 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 58641 invoked by uid 500); 11 Feb 2009 00:11:43 -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 58628 invoked by uid 99); 11 Feb 2009 00:11:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Feb 2009 16:11:43 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates 74.125.92.27 as permitted sender) Received: from [74.125.92.27] (HELO qw-out-2122.google.com) (74.125.92.27) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2009 00:11:35 +0000 Received: by qw-out-2122.google.com with SMTP id 3so107853qwe.31 for ; Tue, 10 Feb 2009 16:11:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=cc3ISDeoqnNs4MlA1FzFmXLlx12MYQ1tbEFLzTnEmDA=; b=hPYGxBwMOtW+VTyzlpdu6P/TxOz9m7+jTxwNTI/Nz/bGANkl1fvsomD7a6dxs2QxoF H49pIqE4w2wVtG2RX0E2GA/tSIOs02skr3KyIVs3IAwmursgpnjRXV/0Z4I4rclphCAi 6sv3lYCpylnxrYgdElNdKysJ/TyliTMoHdjPo= 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=RJFzPDuHUxO11ZBkS+Nz7skNQfCfJ5qMgYei51G7gheG2FY99S5VM4DFM2W5NcQFxu pQr9dwugYmXYsYgJsI1vn/BOcBLAjXdVvt+7qyRpHGjdJkCyfp9gWSwLICK47ZBKbBgc BQuPH6LASRU9Hs5T6M0G7pz2MuUPvx4nA/v9U= MIME-Version: 1.0 Received: by 10.231.16.197 with SMTP id p5mr2078370iba.51.1234311074320; Tue, 10 Feb 2009 16:11:14 -0800 (PST) In-Reply-To: References: Date: Tue, 10 Feb 2009 19:11:14 -0500 Message-ID: Subject: Re: About tests and Ldif injection annotations (completed) From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=00221532c5b420929104629971da X-Virus-Checked: Checked by ClamAV on apache.org --00221532c5b420929104629971da Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Mon, Feb 9, 2009 at 11:52 AM, Emmanuel Lecharny wrote: > Hi guys, > > the cool annotations we have, combined with the rollback system, > allows us to run tests without any problem. Each test can play with > data without interacting with the other tests. However, as the LDIF > injection is done globally for each test, the rollback is also done > globally. ie, if you inject a lot of data, you will have to revert a > lot of data too, for each single test. > > We are using it today for one of our client, and as we have around 400 > entries to inject for our tests, it takes more or less a couple of > seconds to run each test. At the end of the day, when we run our 150 > tests, we have to wait 10 minutes to run all of them. > Use suites and have a full cleanup take place between the suites. You have various cleanup levels (test level, class level, suite level etc) and you can set it up so that a suite class has an annotation which make it cleanup when the suite is started with a PRISTINE server. That's why all this was put in there. We use this today for the Apache DS tests. > > No need to tell that it's way faster ! I was able to run the > SearchITest in less than 5 seconds compared to the usual 15 seconds > for the very same tests (and i'm just talking of 4 entries injected > and rollbacked for every tests). > > So I think this is the way to go. The only difficult point is that we > have to deal with 5 different modes for tests : > - PRISTINE > - RESTART > - ROLLBACK (the default) > - CUMULATIVE > - NOSERVICE. > > To me, the RESTART, CUMULATIVE and NOSERVICE mode seems a bit useless. There are reasons for these - I can explain this tomorrow. Please don't nix this stuff until we discuss it somemore. > > The PRISTINE mode is used for one single test in which we declare two > different factories, hence the need to clean up completely the server. > > I would suggest we get rid of the RESTART, CUMULATIVE and NOSERVICE > mode in order to ease the implementation of my small improvement > (otehriwse, there are too many cases to deal with, and i don't realy > have time for that). > > wdyt? > I think it is a bad idea but I may be wrong. Shit cannot remember that far back when we did all this stuff. Alex --00221532c5b420929104629971da Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Mon, Feb 9, 2009 at 11:52 AM, Emmanue= l Lecharny <el= echarny@apache.org> wrote:
Hi guys,

the cool annotations we have, combined with the rollback system,
allows us to run tests without any problem. Each test can play with
data without interacting with the other tests. However, as the LDIF
injection is done globally for each test, the rollback is also done
globally. ie, if you inject a lot of data, you will have to revert a
lot of data too, for each single test.

We are using it today for one of our client, and as we have around 400
entries to inject for our tests, it takes more or less a couple of
seconds to run each test. At the end of the day, when we run our 150
tests, we have to wait 10 minutes to run all of them.

Use suites and have a full cleanup take place between= the suites. You have various cleanup levels (test level, class level, suit= e level etc) and you can set it up so that a suite class has an annotation = which make it cleanup when the suite is started with a PRISTINE server.&nbs= p; That's why all this was put in there.  We use this today for th= e Apache DS tests.
 

No need to tell that it's way faster ! I was able to run the
SearchITest in less than 5 seconds compared to the usual 15 seconds
for the very same tests (and i'm just talking of 4 entries injected
and rollbacked for every tests).

So I think this is the way to go. The only difficult point is that we
have to deal with 5 different modes for tests :
- PRISTINE
- RESTART
- ROLLBACK (the default)
- CUMULATIVE
- NOSERVICE.

To me, the RESTART, CUMULATIVE and NOSERVICE mode seems a bit useless.

There are reasons for these - I can explain this tomorrow.=   Please don't nix this stuff until we discuss it somemore.
&nb= sp;

The PRISTINE mode is used for one single test in which we declare two
different factories, hence the need to clean up completely the server.

I would suggest we get rid of the RESTART, CUMULATIVE and NOSERVICE
mode in order to ease the implementation of my small improvement
(otehriwse, there are too many cases to deal with, and i don't realy have time for that).

wdyt?

I think it is a bad idea but I may be wrong.  S= hit cannot remember that far back when we did all this stuff.

Alex --00221532c5b420929104629971da--