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.
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. > > I am happy to report that all tests pass on my machine (basically > stock macbook air). > > +1 from me. > > Thanks to everyone who helped with 1.1. > > Chris > > On Wed, Jun 1, 2011 at 12:45 PM, Noah Slater <nsla...@apache.org> wrote: >> >> On 1 Jun 2011, at 20:41, Paul Davis wrote: >> >>> On Wed, Jun 1, 2011 at 3:37 PM, Noah Slater <nsla...@apache.org> wrote: >>>> Considering that the tests work with Chrome, I'm going to change my vote >>>> to +1 now. >>>> >>>> I am also suggesting that we change our recommended test browser to Chrome. >>>> >>>> Firefox 4 seems to have a lot of trouble with it. >>> >>> Also, our documented test browser is FF3.5. I wonder if the update to >>> 4 is also most of the issue. >> >> Could be. :) >> >> DOWN WITH ALL NON-DETERMINISTIC BROWSER TESTS, I SAY! >> >> (I, for one, welcome our new etap overlords.) >> >> > > > > -- > Chris Anderson > http://jchrisa.net > http://couchbase.com
