db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Waagan <Kristian.Waa...@Sun.COM>
Subject Re: TDD and Derby project development
Date Wed, 22 Nov 2006 21:41:53 GMT
Marek Majchrzak wrote:
> Hi,
> So I understand TDD that you first write tests and then code to fulfill this
> tests. For not familiar with this method it could looks strange, but it
> gives sometimes good results :) - so I'm looking for such as projects,
> especially for opensource projects with well managed JIRA and SVN


I was involved in a rather small project (5-10 developers, used Python) 
using TDD, and I believe this approach is not used for Derby. Of course, 
individual developers might have tests drive development for small 
subareas of the code they are working on. The fact that we do not have 
parallel source trees for production code and the test code also 
complicate things, as you have to stick to the public interfaces.

I can't exactly say why, but it seemed a lot easier, and more natural, 
to use TDD for the small project I participated in earlier, than in 
Derby. My gut feeling is that generating the input and state needed for 
unit tests of subareas of the Derby code would require a lot of work 
(need a supporting infrastructure). Another factor is the programming 
language, as you are able to take a lot of shortcuts in Python compared 
to Java.

Further, I also learned that the tests need to be of a pretty good 
quality, and that sitting together with another developer often made 
both the tests and the code a lot better. Needless to say, this is not 
always possible or considered good use of time.


> For details about TDD: http://www.agiledata.org/essays/tdd.html
> Marek
> -----Original Message-----
> From: David.Vancouvering@Sun.COM [mailto:David.Vancouvering@Sun.COM] On
> Behalf Of David Van Couvering
> Sent: Wednesday, November 22, 2006 6:00 PM
> To: derby-dev@db.apache.org
> Subject: Re: TDD and Derby project development
> I'm not sure how you define TDD...
> We build unit/functional  tests around all our features, and run the full
> suite of unit tests in a "tinderbox" whose results are automatically
> reported.  We have a general policy of keeping success rate on these tests
> to 100%.
> David
> Marek Majchrzak wrote:
>> Hello,
>> Sorry for off topic post.
>> I'm looking for information about testing approach in Your project. I 
>> would like to know whether developers use in this project TDD (test 
>> driven
>> development) approach or not.
>> I need this information in order to perform some metrics comparison 
>> and research for University purpose.
>> With best regards
>> 	Marek Majchrzak

View raw message