You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by sebb <se...@gmail.com> on 2005/08/04 15:59:51 UTC
lib/junit directory specification
The latest version of JMeter generates an error message in the console
window unless the lib/junit directory exists. Presumably this is
intended for holding jars containing JUnit tests?
Seems unnecessary to have to create an empty junit directory even if
one is not using the JUnit sampler.
Would it not be better to provide the JUnit jar directory as a property?
The search for classes could then be restricted to the jars found in
that directory - if the property was defined.
The property could even be a list of absolute or relative directories.
It would need to be used to define both the classpath and the search path.
Might also be better if the junit classpath was kept separate from the
JMeter classpath.
WDYT?
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: lib/junit directory specification
Posted by sebb <se...@gmail.com>.
BTW, just noticed that the JUnit Sampler only checks for methods
called "test..." - should it not also allow for the suite() method?
Might also want to consider whether the junit classpath property
should allow both directory names and individual jar files.
E.g. split the string using the JVM classpath separator; if an element
is a directory, look for all jars therein, otherwise assume it is a
jar file.
Looks like findClassesThatExtend() already supports this, so would
just need to ensure that the classpath was appropriately updated.
S.
On 04/08/05, Peter Lin <wo...@gmail.com> wrote:
> that's a much better and more flexible way of handling it than my
> simple first attempt.
>
> I'll make that change tonight, and add the property to
> jmeter.properties. by the way, thanks for all of your suggestions.
> the sampler now provides default values.
>
>
> peter
>
>
> On 8/4/05, sebb <se...@gmail.com> wrote:
> > The latest version of JMeter generates an error message in the console
> > window unless the lib/junit directory exists. Presumably this is
> > intended for holding jars containing JUnit tests?
> >
> > Seems unnecessary to have to create an empty junit directory even if
> > one is not using the JUnit sampler.
> >
> > Would it not be better to provide the JUnit jar directory as a property?
> > The search for classes could then be restricted to the jars found in
> > that directory - if the property was defined.
> >
> > The property could even be a list of absolute or relative directories.
> > It would need to be used to define both the classpath and the search path.
> >
> > Might also be better if the junit classpath was kept separate from the
> > JMeter classpath.
> >
> > WDYT?
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: lib/junit directory specification
Posted by Peter Lin <wo...@gmail.com>.
that's a much better and more flexible way of handling it than my
simple first attempt.
I'll make that change tonight, and add the property to
jmeter.properties. by the way, thanks for all of your suggestions.
the sampler now provides default values.
peter
On 8/4/05, sebb <se...@gmail.com> wrote:
> The latest version of JMeter generates an error message in the console
> window unless the lib/junit directory exists. Presumably this is
> intended for holding jars containing JUnit tests?
>
> Seems unnecessary to have to create an empty junit directory even if
> one is not using the JUnit sampler.
>
> Would it not be better to provide the JUnit jar directory as a property?
> The search for classes could then be restricted to the jars found in
> that directory - if the property was defined.
>
> The property could even be a list of absolute or relative directories.
> It would need to be used to define both the classpath and the search path.
>
> Might also be better if the junit classpath was kept separate from the
> JMeter classpath.
>
> WDYT?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org