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 kxepal@gmail.com designates
 209.85.220.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <F5FDD679DA03BA4D806BEA7CB6EBCD6F388A0AC3@VEREXCH01.harrisbroadcast.com>
References: 
 <F5FDD679DA03BA4D806BEA7CB6EBCD6F388A0AC3@VEREXCH01.harrisbroadcast.com>
Date: Thu, 20 Mar 2014 21:30:17 +0400
Message-ID: 
 <CAHdjipJNRPm-zXMUxgOLOkd63tdqrBY-GZd6+Z+2aNKY49k9Nw@mail.gmail.com>
Subject: Re: Unit Test logging with couchDB....
From: Alexander Shorin <kxepal@gmail.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

Do you mean under "unit test logging with CouchDB" actually storing
unittest results as CouchDB documents?
--
,,,^..^,,,


On Thu, Mar 20, 2014 at 6:08 PM, Knudsen, Ken
<Ken.Knudsen@imaginecommunications.com> wrote:
> Hi Everyone,
>
>    Obviously there's a thousand plus ways of doing this...Has anyone impl=
emented or worked with unit testing frameworks but instead of using that fr=
ameworks built in logging mechanism, broke out that logging part and used c=
ouchDB instead? With couchDB there wouldn't be much 'breaking out' given ho=
w easy it is to record log information during a UT run with couchDB...but I=
'm interested in anything someone may have to add outside of the obvious st=
uff...
>    I watched a talk from the MS guys where they incorporated couchDB into=
 one of their internal unit testing frameworks (Daylight?)...but I can't fi=
nd anything more on it so far as what they built on top of that data captur=
ed, etc.
>
> To keep the discussion as global as possible, the term 'Unit Testing' in =
this context envelopes all layers, from single component to integration tes=
ting.
>
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________