You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by bu...@apache.org on 2007/05/02 09:35:38 UTC
DO NOT REPLY [Bug 42226] - sample groups
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42226>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42226
------- Additional Comments From ralikwen@hotmail.com 2007-05-02 00:35 -------
Indeed TransactionController seems to be aiming at what I would like.
To me the name of the controller sounds a bit misleading though as you can
group arbitrary listeners.
It seems that you now have two ways of grouping listeners - through their
labels and by placing them under a TransactionController.
Having a Controller for the group is a better structure and GUI than grouping
by labels on the other hand I am not sure that treating the group as a
separate sample is a good model - as it is in fact not a separate sample but a
group of samples.
In summary reports could it not behave like labelgroups behave now? Only the
aggregate function must be different - I could even imagine selectable. Now
the summary function for labelgroups is AVERAGE, I would like to have SUM, but
I can imagine somebody need e.g. MOST or LEAST.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org