Hi,
I downloaded the source from cvs and made changes to bin/jmeter script :
1. JAVAPROPS and JAVA_PROPS variables suppose to be the same. Changed JAVAPROPS to
JAVA_PROPS
2. Changed "org.apache.jmeter.NewDriver" to be after "$JAVA_PROPS" 'cos the -D
properties should come before the class to be run.
From
"java -classpath $CLASSPATH:`dirname $0`/../lib/xerces.jar:`dirname
$0`/../lib/util.jar:`dirname $0`/ApacheJMeter.jar org.apache.jmeter.NewDriver
$JAVA_PROPS $PROPERTIES"
to
"java -classpath $CLASSPATH:`dirname $0`/../lib/xerces.jar:`dirname
$0`/../lib/util.jar:`dirname $0`/ApacheJMeter.jar $JAVA_PROPS
org.apache.jmeter.NewDriver $PROPERTIES"
3. Added one echo line to print "java" statemet used to start jmeter.
Please update the cvs if you feel that the changes made is for the better.
Also while I was going thru' the codes, I decided that I might as well add in javadoc
comments which you marked as 'To Do' in
src/org/apache/jmeter/protocol/http/samplers/HTTPSampler.java
Both files are attached below.
I was about to embark on writing an extension of HTTPSampler.java to automatically
download images, applets etc so I wanted to write the test cases first using jUnit.
The src/org/apache/jmeter/junit/AllTests.java automatically creates a test suite based
on the classes which extend TestCase in ApacheJMeter.jar. Does this mean that my new
test cases has to be added to the .jar even during development? I know ways to
circumvent this but pls help me out by telling me how you do it 'cos I would rather
follow your standardized way.
Thanks.
-----Original Message-----
From: "Stover, Michael" <[EMAIL PROTECTED]>
Date: Fri, 06 Jul 2001 08:54:40 -0400
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: RE: JMeter extensions and browser emulation
> There is no such page - I don't think all that many "optional" features have
> been developed that aren't in the regular JMeter CVS. I don't know about
> them, in any case.
>
> Downloading images in a web page and recording those times as well would
> probably be useful to many people. It hasn't been developed, to my
> knowledge, so forge ahead!
>
> Regarding your idea of listening on a per-controller basis, that would
> probably be an excellent modification to JMeter's structure. It would allow
> people to extract more precise information about their web application if
> JMeter took into account where in the test plan tree you added the listener.
> I'll have to think about that.
>
> Regarding HttpUnit and following links, I'm not real familiar with what
> their components look like (I believe they use JTidy to parse HTML pages to
> extract the links). I've been working on such a module myself, and I've
> already finished anchor extraction. Now I'm working on forms. I'm not
> using JTidy because it appears to have zero javadocs, and I just stopped at
> that point. Easier to write my own. Also, my plan for link extraction is
> not so much to allow JMeter to spider on it's own, but rather to allow test
> plan writers maximum flexibility in dealing with dynamic sites. To that
> end, I'm working on a module that will combine a test sample with the
> previous server response to create a new test sample on the run. I'll keep
> ya'll informed of my progress.
>
> -Mike
--
__________________________________________________
Get FREE 50 MB email @ http://www.AtoZasia.com
Powered by Outblaze
jmeter
HTTPSampler.java
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
