iBATIS 3 comes with about 1200 unit tests that cover about 85% of the codebase. However, unit testing does not equal field testing. Our process works like this:
* Committers write code or integrate code from the community. * Committers vote upon and release Betas. * The community field tests the Beta product and offers their vote of confidence in it. * Once we see a high vote of confidence, the Committers will vote to GA the product. So in a sense, it's up to the community to field test and ultimately GA the product. Clinton On Wed, Sep 30, 2009 at 4:26 AM, Dominik Mähl <emiss...@dsnine.com> wrote: > Hi, > > we're currently evaluating iBatis 3 for a project after using iBatis 2 in > its predecessor. > > One of our developers encountered that beta 3 does not honor the id > property (it is defined on a primary key) > so that no grouping takes place when using collections filled via joins. > > I've checked out the current svn trunk and the problem seems to be fixed > there. My remaining question is: How > thoroughly is iBatis 3 tested? Is it safe to build upon for a product which > will probably be released Q2/Q3 2010? > > We're happy to provide bug reports should we encounter other bugs but I was > surprised that a bug in such a > "critical" functionality still exists. I thought, collections via joins are > a often used feature :) > > On a side note: apparently trunk currently always enhances classes with > cglib. Why was the option to disable this removed? > > I hope I don't sound too rude or harsh, I'm just a great fan of iBatis. > > Thanks, > -- > Dominik <emiss...@dsnine.com> >
