commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz" <p...@steitz.com>
Subject Re: [lang] Lang 2.0 release?
Date Fri, 22 Aug 2003 02:46:04 GMT
Gary Gregory wrote:
> I have not looked at the "perf" test but the concept is not new and it is
> valid. A perf unit test, for example, would make sure that a certain bit of
> code performs within some time parameter, for example, faster than some JRE
> implementation or faster/slower if configured in certain ways. 
> 
> Gary
> 

I agree.  Performance tests are good -- just maybe not so good as part 
of the standard build, since to do them correctly (getting enough data 
to be meaningful) generally requires a bit of cpu time and that gets 
tedious as part of the standard build.  By "standard build", I mean the 
process that I at least go through each time I have made changes -- 
build, fire off tests, generate javadoc and basic reports, look at 
errors, say DOH!, repeat :).  Maven is very cool for this kind of thing 
-- you can see checkstyle, javadoc, clover reports "instantly" after 
making changes.

A complete set of perf tests for lang would be a good thing to add to 
the task list.  I would put these tests in a separate suite, fired by a 
separate task, however, similar to what Craig has started for BeanUtils. 
  I don't know exactly how this will work via maven. Maybe someone else 
does? What would be really cool would be to build/grab a maven 
performance test plugin. What I have in mind here is something that 
kicks off Junit tests repeatedly and (after some priming reps) 
accumlates completion time stats and displays these as the test report. 
Does anyone know if such a thing already exists?

Phil

> 
>>-----Original Message-----
>>From: Henri Yandell [mailto:bayard@generationjava.com]
>>Sent: Wednesday, August 20, 2003 22:03
>>To: Jakarta Commons Developers List
>>Subject: Re: [lang] Lang 2.0 release?
>>
>>
>>
>>On Wed, 20 Aug 2003, Phil Steitz wrote:
>>
>>
>>>the old .properties file format)  I was just writing a note asking if
>>>anyone had any objections to the following changes, which will fix this
>>>among other things:
>>>
>>>1. Mods to project.xml:
>>>
>>>* Restrict tests to Suites run by Ant build (so maven build does not
>>>have to run through perf and other tests each time)
>>
>>Not sure what you mean.
>>
>>Maven is supposed to run the tests each time we build, so removing some
>>from it would seem to be self-destructive?
>>
>>What is perf? That long test that takes ages?
>>
>>Maybe we should define a separate /src/perf for tests that are only to be
>>done at certain times?
>>
>>
>>>* Add a <reports> element to restrict reports
>>
>>Which would we restrict?
>>
>>
>>>2. Add checkstyle.xml "translating" (to the best of my limited
>>>abilities) the current checkstyle.properties (so maven will not generate
>>>so many checkstyle errors)
>>
>>+1
>>
>>
>>>3. Modify project.properties to refer to checkstyle.xml
>>
>>+1
>>
>>Hen
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> 




Mime
View raw message