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/09 15:10:14 UTC
DO NOT REPLY [Bug 41913] - Let TransactionController create samples that contains the samples of the transaction
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=41913>.
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=41913
alf@i100.no changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #19777|0 |1
is obsolete| |
Attachment #19861|0 |1
is obsolete| |
------- Additional Comments From alf@i100.no 2007-05-09 06:10 -------
Created an attachment (id=20157)
--> (http://issues.apache.org/bugzilla/attachment.cgi?id=20157&action=view)
Patch for letting TransactionSample contain sub results
Suggested patch to let TransactionSample contain the samples of the transaction
as sub results, and avoid the subsamples to appear in sample listeners.
This suggested patch restructures the transaction handling code quite a bit.
The TransactionController and TransactionControllerGui is moved from components
to core, because the TransactionController is now referenced in JMeterThread,
which is in core.
The source code in TransactionControllerGUI is not changed at all.
I have made a new class TransactionSampler, which is responsible for handling
the sub sampler results.
The JMeterThread is changed, to handle transactions.
The transaction sample is only sent to listeners who do not receive the sub
samples. The transaction sample contains the sub samples as sub results.
It is also possible to have assertions for the transaction sample, for example
DurationAssertion, to check the duration for the transaction. This assertion
will also be applied to the sub samples.
The TransactionController code is simpler than before.
I will attach a test plan, to show one way of using the Transactions, Listeners
and Assertions.
It could also be possible to add an option in the TransactionControllerGUI, to
specify that the transaction sample should not contain sub results, for more
backwards compatibility.
For now, I would appreciate comments about the code restructuring and the
functionality. Do you think it makes sense, and does the code look ok to you,
or is the code becoming to complex with these changes ?
Ideally, I would have liked to handle everything inside the
TransactionSampler.sample method instead of in JMeterThread, but I do not see
how that is possible currently.
--
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