Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-jmeter Wiki" for change notification.
The following page has been changed by AlfHogemark: http://wiki.apache.org/jakarta-jmeter/FutureReleases The comment on the change is: Mainly additonal comments related to "ab" replacement ------------------------------------------------------------------------------ * Will we really be testing Axis / XFire client side peformance here ? * Or could we make a nice GUI, so it is easier to test web services ? * Make command line option available, to easily performance test one url - * This is meant as a replacement for the "ab" command + * This is meant as a replacement for the "ab" command, and alternative to "faban" * I think it would broaden the user of JMeter a lot * I will look into making a "ab result listener", which presents the same statistics as "ab" initially (Alf Hogemark) + * One possible implementation is + * Add a simple jmeter test plan, with threadgroup, http sampler, and listener, using property values to control behavior to the bin/system_testfiles directory + * Add shell scripts, for example jmeter_test_http, which just calls the standard jmeter script, with additional "-J" arguments, for example "-Jiterations=10" + * Need a way of getting the listener output to the console, need some investigation * Restructure HTTP Sampler / Settings GUI. bugzilla 41917. A big job, but is becoming necessary, if we are adding more options to the HTTP Sampler * Add a "View only errors" setting in viewers. * Currently, there is a "Log only errors", but I want to have it as a general setting on each listener @@ -107, +111 @@ * component_reference is getting much too big. This will require changes to the help system. * sort functions and component ref into more logical order (currently chronological) * perhaps use separate XML files for each item, included by main pages ? + * Could we then add a "Help" button to each GUI element, which would bring up the correct help in the browser ? * Recode Save``Service so it does not load classes unnecessarily (code already developed and tested - not committed) * Re-write Class``Finder: * needs general tidyup / javadoc @@ -145, +150 @@ * introduce Generic HTTP Sampler which can do either Java or Http``Client or ... * could be new sampler GUI with new underlying test elements * but it would be nice if existing test plans were converted into the new sampler. Looked at this a while back, but got stuck with XStream aliasing, which has to be one-to-one at present. However, the code change to Save``Service to remove the class loading should make it possible to have multiple aliases for a single class. That might be sufficient, otherwise we'll need a suitable converter. - + * I think the GUI should just contain a dropdown "Client implementation", with values like "Java JRE", "HTTPClient 3.1", "HTTPClient 4.0" etc. + * Improve "org.apache.jmeter.JMeter" class by removing the hack in "ListenToTest", which causes JMeter to always sleep 5 seconds before exiting when run in batch + * I think this relates to how threads are closed and lingering samples are handled. How is it solved in the "GUI" mode ? = Release strategy = --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
