that's a good idea. I'll make that change later today along with some
other enhancements.

I thought about excluding the jmeter unit tests, but I couldn't
decide. basically, I took the easy way out and decided not to filter
them. I can always add them later.  I like the idea of slowly moving
the unit tests to some other jar, since it is just for the developers.

should we make the 2.1 RC and post it?

I can give it a try if others are busy.  It might take me a few hours
to figure out how to go about doing that.

peter


On 7/21/05, sebb <[EMAIL PROTECTED]> wrote:
> I think it would be better to use the Sampler name as the sample
> label, and save the junit class + method as the sampler data.
> 
> That way, one can aggregate multiple samples with different  class/method 
> names.
> 
> ==
> 
> Also, I'm not sure that many existing JMeter JUnit tests would make
> sense to test, so maybe jmeter classes should be excluded from the
> list?
> 
> Perhaps better would be to move all the JMeter tests to a separate
> source tree and/or separate jar file. This could then be excluded from
> the normal binary distribution, as the tests are only really needed by
> developers.
> 
> S.
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to