As far as other areas, please look at the clover report [1] or generate one yourself with Maven and feel free to up the %'s in any deficient area.
Thanks, Gary [1] http://people.apache.org/~ggregory/commons-lang/2.2-dev/docs/clover > -----Original Message----- > From: Nathan Beyer [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 30, 2005 2:57 PM > To: 'Jakarta Commons Developers List' > Subject: RE: [lang] Better coverage for StrBuilder and StrTokenizer. > > I'm willing to do some JUnit building. Any other areas that need more > testing? > > I presume you're working off the main trunk. > > -----Original Message----- > From: Gary Gregory [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 30, 2005 12:18 PM > To: Jakarta Commons Developers List > Subject: [lang] Better coverage for StrBuilder and StrTokenizer. > > Do any of the original authors of StrBuilder and StrTokenizer want to > provide more unit tests to improve the current ~50% code coverage? ;-) > > For current coverage, do a local Maven build or see: > > http://people.apache.org/~ggregory/commons-lang/2.2-dev/docs/clover/org/ > apache/commons/lang/text/pkg-summary.html > > Thanks, > > Gary > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
