Marc Guillemot wrote:
Hi Michael,
are you sure that you don't have an other problem. I've made a small
test and once set with <setproxy>, the proxy system properties are still
available in build files called from the main one what seems logical.
the main problem seems to be that we really do start a new jvm calling:
---------
<java jar="${ant.home}/lib/ant-launcher.jar" fork="true" failonerror="true">
[...]
----------
I think this is caused by earlier OutOfMemory problems the colleagues had with running their
webtests. I'm not aware of the necessity of this construct. So far what I can see - while examining
the necessity of the second java-call the teamwork of setproxy and webtest are fine.
Btw, you've said that you run (or want to run) your webtest with a proxy
to record it and use it to perform load testing with the grinder. Does
it means that it reuses the sessions created by the webtests? Can you
give more details about the process?
[...]
Of course ;-)
On performance test with grinder the usual process in our project is:
1. Starting the grinder-proxy
2. Reconfigure the proxy for the browser and
3. Start using the web application (sending request to the server).
4. Shutdown the proxy
5. Save the result-file of the proxy
6. Configure grinder to use the result-file of the manual application-session
for the load test.
7. Configure cruisecontrol to run grinder with the result-file.
So while our webtests not only test our application but also create the main testdata our manually
recorded grinder-records (see process above) fails too often. This was the point we thought about
taking webtest to imput the record of our grinder-test.
--
Mit freundlichen Grüßen
------------------------------------------------------------------------
Michael Habbert
Senior Developer
Netpioneer GmbH, Beiertheimer Allee 18, D-76137 Karlsruhe
Geschäftsführer: Axel Jahn
HRB: 107521 Handelsregister Mannheim
Tel: 0721 / 920 60 21
Fax: 0721 / 920 60 30
E-Mail: [EMAIL PROTECTED]
www: http://www.netpioneer.de
_______________________________________________
WebTest mailing list
[email protected]
http://lists.canoo.com/mailman/listinfo/webtest
