On Wed, 27 Feb 2002 12:09, Mark Woon wrote: > Leif Mortenson wrote: > > I agree, but try writing a performance test case. You can test both > > methods and > > get some solid numbers. Sometimes the code you think is fast is slow and > > visavera. Performance tests should be named xxxxProfile.java. > > > > Take a look at the following for example: > > scratchpad/org/apache/avalon/excalibur/system/test/ContainerProfile.java > > test/org/apache/avalon/excalibur/pool/test/SingleThreadedPoolComparisonPr > >ofile.java > > Speaking of which, are there any documents on how to actually go about > doing testing, either for functionality or performance? There seems to be > quite a bit of stuff in the way of a test harness, but before I go jumping > into the code, perhaps there's something else I can read?
Well we use JUnit and you can find all the documentation for that on www.junit.org. I don't know whether our profiling tests use this but there is a JUnit extension called JUnitPerf that I have heard good things about but never used. You may want to look at that because it is likely to have some good documentation about that sort of stuff. Is this what you were asking ? -- Cheers, Pete ----------------------------------------------- "You can't depend on your eyes when your imagination is out of focus." -Mark Twain ----------------------------------------------- -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
