Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of dionne@dionne-associates.com
 designates 67.222.55.9 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default;
 d=dionne-associates.com;
	h=Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Identified-User;
	b=AZMjljQABAU6tB7SIlaJxV0Gpe3FyvOi9L0iIGd8RPT9QWDJjG7naCMQFsxXMLstXUMcE0bjPbmd7W6lNvQAXqtuDBFe4dNiYSSPjom2/hmsA3Z4bhsIAaCHuFtBrIKJ;
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [VOTE] Apache CouchDB 1.1.0 release, round 3.
From: Robert Dionne <dionne@dionne-associates.com>
In-Reply-To: <BANLkTinCwVTJMdBwnXtEuesiWEQYuNLBsQ@mail.gmail.com>
Date: Fri, 3 Jun 2011 05:09:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C1A6EE6-4962-4F2B-980A-C3992281A5D9@dionne-associates.com>
References: <BANLkTikiDSb6VVjee=BF-Nt=qSU7HY9VRQ@mail.gmail.com>
 <21358EB2-DEC6-4A27-AF3C-F9B31EAD6059@googlemail.com>
 <58A89F9C-7482-4117-9FC2-755603595070@apache.org>
 <BANLkTikOe9ftV4PA-FaOs40ENrLrynMfog@mail.gmail.com>
 <6BF4674D-1161-44D7-925E-E252CB358A70@apache.org>
 <BANLkTimPk-J3yAT+BdvYXszgyT+V+vJXXA@mail.gmail.com>
 <0FE7E5F7-6E69-4FA5-AD53-26397F0272D0@apache.org>
 <BANLkTinCwVTJMdBwnXtEuesiWEQYuNLBsQ@mail.gmail.com>
To: dev@couchdb.apache.org

Chris,

  This is an excellent idea. Currently the entire suite of browser tests =
are also run from the command line, where we overload the CouchDB =
definition and use couchjs. We could break the suite out with a subset =
staying in share/www/script/test  to be used as you suggest, and the =
lion's share of them moving to test/javascript  to be run as part of =
"make check". They serve a great role in testing end-end but go a little =
too far in making use of the browser.=20

   I'll take a closer look at this over the weekend.

Best,

Bob


On Jun 2, 2011, at 11:35 PM, Chris Anderson wrote:

> I agree, the browser tests should move to the command line, and a
> small subset (30 seconds tops) of tests should be in the browser
> (useful for debugging proxy config, installation, spidermonkey
> version, or whatever. I'd rather not block 1.1 on rewriting the test
> suite, even though I agree the browser suite has started to outgrow
> itself.
>=20
> I am happy to report that all tests pass on my machine (basically
> stock macbook air).
>=20
> +1 from me.
>=20
> Thanks to everyone who helped with 1.1.
>=20
> Chris
>=20
> On Wed, Jun 1, 2011 at 12:45 PM, Noah Slater <nslater@apache.org> =
wrote:
>>=20
>> On 1 Jun 2011, at 20:41, Paul Davis wrote:
>>=20
>>> On Wed, Jun 1, 2011 at 3:37 PM, Noah Slater <nslater@apache.org> =
wrote:
>>>> Considering that the tests work with Chrome, I'm going to change my =
vote to +1 now.
>>>>=20
>>>> I am also suggesting that we change our recommended test browser to =
Chrome.
>>>>=20
>>>> Firefox 4 seems to have a lot of trouble with it.
>>>=20
>>> Also, our documented test browser is FF3.5. I wonder if the update =
to
>>> 4 is also most of the issue.
>>=20
>> Could be. :)
>>=20
>> DOWN WITH ALL NON-DETERMINISTIC BROWSER TESTS, I SAY!
>>=20
>> (I, for one, welcome our new etap overlords.)
>>=20
>>=20
>=20
>=20
>=20
> --=20
> Chris Anderson
> http://jchrisa.net
> http://couchbase.com