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.

Regards,
Prabhat

--- In junitperf@yahoogroups.com, Mike Clark <mike@...> wrote:
>
>
> On Jun 27, 2008, at 10:59 AM, prabhat jha wrote:
>
> > Hi,
> >
> > I just downloaded junitperf version 1.9.1 and I am doing a POC with
> > jdk 6 (tried jdk1.5 as well) as stated in junitperf page. My simple
> > load test case not running properly.
> >
> > When I just want to run one iteration of the test, it goes to setup
> > and tear method but it does not run the actual test which is
> > testOneSecondResponse . You can take a look at my very simple test
athttp://anonsvn.jboss.org/repos/qa/junitperf/
> > . SampleTestCase.java is the test case and SampleLoadTestCase.java
> > is corresponding load test case.
>
>
> You'll need to call the constructor that takes a name and pass in the
> name of the test method, like so:
>
> LoadTest test = new LoadTest (new
> SampleTestCase("testOneSecondResponse"),1,1);
>
> Hope that helps.
>
> Mike
>