db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: Regression testing
Date Tue, 10 May 2005 17:51:04 GMT
Hi, Andrew.   I see your point about increasing traffic on the list, but 
it's just one email a day, that really isn't going to inrease the noise 

Where I used to work, we got an email when the build or tests *failed*. 
   This was very useful, as it created an automatic impetus for all of 
us to be more careful, because everyone knows when you messed up :)  If 
our tools could support that, that would be fine with me.

Regarding the tinderbox, I'll talk around here to see what we can dig 
up; making the results available could be accomplished by posting the 
results to a public web site.  I think we should be able to work this 
out, it seems worth it if it increases the quality of the product.


Andrew McIntyre wrote:

> On May 4, 2005, at 2:44 PM, Ole Solberg wrote:
>> We also build and test on a few platforms daily and could provide 
>> those results.
>> My level of ambition would be to just send out the results without any 
>> deep analysis. (Just catching and filtering obvious local 
>> setup/enviroment blunders etc.)
>> I think communicating daily regression test results could be a good 
>> way to present the state of Derby.
> It's great to hear that other derby-dev'rs are building Derby nightly 
> and running the tests! I think it would be a very good thing to be 
> sharing test results, but I'm a bit concerned about sending them to 
> derby-dev itself. I personally feel that nightly automated mail to the 
> list would simply decrease the signal-to-noise ratio on the list and be 
> a bit of a nuisance (and ultimately not likely to be read). But there 
> are alternatives to sending nightly test results to the list, like 
> posting them in a specific location on the Derby website, as I'm 
> currently doing with the doc/javadoc build. Or we could have a page on 
> the Derby website with links to locations where derby-dev'rs are 
> publishing their test results.
> In an ideal situation, it would be great to have a tinderbox approach, 
> as David suggested, with constantly active build/test cycles running. 
> But there's always the complicated question of who's going to provide 
> the hardware and put the box out on the net for all to see when going 
> that route.
> andrew

View raw message