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 ------------------------------------------------------------------------------ * a Summary listener only for errors * 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" ? + * Could we remove the "Write All Data to File" setting from all listeners, and instead make a "Write All Data listener" ? [The simple data writer?] * Listeners: * make distinction between open file for read and write. - * at present the browse button does both, which is confusing (given the heading) + * at present the browse button does both, which is confusing (given the heading) <= this has been changed * 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 @@ -86, +86 @@ * Would make it a lot easier to see what is what in the tree * Make menu options more context sensitive, so they are only enabled when they make sense * There seems to be some context sensitivity currently, but the code seems a bit odd, with explicit methods used by various parts of the code + * Prevent adding test elements to inappropriate parts of the tree - e.g. controller and sampler must be under a thread group. Should also prevent drag and drop. * Extend CSV Data Set to read via JDBC * Assertion Results (or similar) could be used to attach errors to samples - e.g. if a Post-Processor failed, the error could be shown there instead of in the log. Or just add string array for storing such errors? * Save Graphics should prompt before overwriting files @@ -103, +104 @@ * 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. + * Remote Mode selection: might be useful to be able to specify the remote mode for each listener. This would allow the use of immediate mode for a few listeners and statistical mode for most of traffic. + * Hostname is present in the SampleEvent class - can this be saved in the log files? + * easy for CSV: pass SampleEvent instead of SampleResult. + * harder for XML, as the default output depends on the class, so using SampleEvent would change the XML element. This would affect any stylesheets etc. However, using SampleEvent as the class would allow the use of a single element instead of both sample and httpSample (and any other future subclasses) = Non-functional improvements = --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
