On Jun 30, 2008, at 12:34 PM, prabhat wrote:

> Thanks Mike.
>
> That works. I was hoping that not calling the constructor that takes
> method name would result into calling all test methods automatically.
> Most of the test cases that I have are already written and they do not
> have such constructors.
>
> Now that I know you are alive :-), is there a way to avoid setup/tear
> method? My use case is such that my setup and tear methods are very
> expensive so my unit load testing wont give me the right metrics that
> I want.

The design of JUnit only allows decoration around the setup/test/
teardown lifecycle, so it can't easily be avoided. If your setup
method is expensive because it's priming the database, for example,
you may want to refactor that step out into a method you can call
explicitly before running the performance tests.

Mike