Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of b.candler@pobox.com
 designates 208.72.237.25 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to
	:subject:message-id:references:mime-version:content-type
	:in-reply-to:content-transfer-encoding; q=dns; s=sasl; b=R2qddMy
	R/RN2ttCR8C57S9dpSq/hnCIm7tx93Io45POEa7PH3sxtJPF0XgSSylklgzmOjmX
	7w8nix3GQ7GhaC/qE+hqHBYxzZvI/P9P9iVZ0CIbq6xceAMIlemeFzPqESTEgNjl
	FevNnKYiCtw753l6gYEEACdYkPhl2VIXiP4s=
Date: Sat, 7 Nov 2009 21:58:41 +0000
From: Brian Candler <B.Candler@pobox.com>
To: user@couchdb.apache.org
Subject: Re: Tests/TDD for CouchDB views
Message-ID: <20091107215841.GC9046@uk.tiscali.com>
Mail-Followup-To: user@couchdb.apache.org
References: <177E2090-776A-4C2D-9BFB-89BF4F074DFB@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <177E2090-776A-4C2D-9BFB-89BF4F074DFB@gmail.com>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 07, 2009 at 02:31:04PM +0100, Karel Mina=C5=99=C3=ADk wrote:
> So, my questions are basically these:
>
> * How do would you write/implement tests for your views?

I don't see in principle why it can't be any different to normal tests. T=
hat
is, you write tests within your application testing framework which:
- setup a database and some sample data
- perform a view query
- check the results are what you expect

> * What is the recommended practice for writing the views? In Futon? In =
=20
> an editor and uploading them to db via couchapp or similar? Via =20
> CouchRest or similar layer?

I do the latter (using my own CouchTiny rather than CouchRest). Your view=
s
are source-controlled together with the rest of your application, your
application can populate the design docs when required, and you can
integrate your view tests with your application tests just as you wish.

> * Is it possible to write views "test-first|driven", ie. setting up som=
e=20
> fixtures, writing the view, etc? Does it even make sense in CouchDB=20
> context?

I think so, if the test is part of your application (e.g. your applicatio=
n
is in Ruby and you're using something like CouchRest to manage your desig=
n
docs). View tests are just exercising another part of your app.

> * Is there a way to automatically run such test suites? (Via browser, o=
r=20
> something like Rhino?)

Same.

> * Regarding application logic itself, what would be the best/preferred =
=20
> way to test CouchDB-backed models in eg. Rails app? Using eg. FakeWeb =20
> [4] to mock responses and work with those? Or setting up and using =20
> another CouchDB database (like Rails does for *SQL dbs)?

You can set up 'test', 'development' and 'production' environments for
CouchDB just as ActiveRecord does, and this is how I handle it. See
http://github.com/candlerb/couchtiny/blob/master/doc/RAILS.rdoc

Note: this is for my own CouchTiny, which is subject to change at my
personal whim so I wouldn't recommend anyone to depend on it right now, b=
ut
you should be able to apply the same approach to CouchRest.

Regards,

Brian.