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 JMeterAdmin: http://wiki.apache.org/jakarta-jmeter/FutureReleases ------------------------------------------------------------------------------ * I find the "Write All Data to File" setting on each listener confusing, since all listeners share the same possible log output, does it not ? * For example, the "Graph listener", it does not write graph files to the file does it ? It writes a CSV or XML file ? * Could we remove the "Write All Data to File" setting from all listeners, and instead make a "Write All Data listener" ? + * Listeners: + * make distinction between open file for read and write. + * at present the browse button does both, which is confusing (given the heading) + * a file that has just been read will then be used for writing if a test is run - is that sensible, or should the file name be cleared after it has been read? * Add a "Preview" button to "CSV Data Set Config", which would use the file name and parameter specification, and bring up a dialog or something to show an example of the variables available and their values. * Useful for easily checking that you have specified the columns and variables correctly * Could this limit the number of emails on the jmeter-user list asking how "CSV Data Set" works @@ -90, +94 @@ * Do not use Reader/Writer classes, which uses JVM default character encoding, causing mirrored content to differ * Add unit tests * HTTP Cookie Manager should not clear static cookies each iteration - + * Module Controller GUI + * should it omit leading path name elements as at present? + * it would be nice if it could check for ambiguous controller names: + * report error if ambig. name selected? OR + * flag ambiguous names in the drop-down list? + * user.properties and system.properties should be read from JMeter launch directory if not found in current directory. + * Java Sampler to invoke arbitrary Java method. Would need: + * classname, method name, params (and types) , classpath + * this can be done currently with BeanShell, but it would be simpler to have a dedicated GUI. = Non-functional improvements = @@ -157, +169 @@ * 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 ? + * GUI code refactor + * there are various table implementations, could they be combined? + * perhaps the table models could also be combined? + * Add SVN revision number to version? - or at least to Manifests. = Release strategy = --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
