You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2017/08/28 13:26:41 UTC

[Bug 61466] New: Adding samplers comment to SamplerResult could be interesting for reporters

https://bz.apache.org/bugzilla/show_bug.cgi?id=61466

            Bug ID: 61466
           Summary: Adding samplers comment to SamplerResult could be
                    interesting for reporters
           Product: JMeter
           Version: 3.1
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: vherilier@gmail.com
  Target Milestone: ---

Publishing JMeter results directly under specific format like PerfPublisher is
possible from reporter elements but the test details (comment) is hardly
missing (especially the one of TransactionControllers) because not available in
the SampleResult class.

Does this data miss on purpose (memory or performance issues) or could it be
added to enhance JMeter to provide then more accurate reporters?

Sorry if the question was already rised and answered, but I don't find anything
about it.

Thanks for your feedback.

--Vincent

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61466] Adding samplers comment to SamplerResult could be interesting for reporters

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61466

Vincent HERILIER <vh...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW

--- Comment #2 from Vincent HERILIER <vh...@gmail.com> ---
Hi Philippe,

I'm not sure for the duplication (in my case), but at least, if the Transaction
Controller is able to "save" its comment (description) into its related
SampleResult, it could be great enough.
PerfPublisher does only work on the usecase/testcase level, so the
TransactionController is the right element to deal with it; the inner steps are
not relevant for it (other sampler results).

So, if the SampleResult object may have a new "comment" (String) property (like
the name) and always initialized as an empty one and related getter/setter.
The TransactionSampler can save its comment in its related sampleResult with 2
constructors to keep compatibility.
And the TransactionController just has to create a TransactionSampler with the
name and the comment.

Other Sampler elements could receive the same feature but I do not need that
currently.

I already have the code that I can propose in a PR.

Thank you for your feedbacks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61466] Adding samplers comment to SamplerResult could be interesting for reporters

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61466

Philippe Mouawad <p....@ubik-ingenierie.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |p.mouawad@ubik-ingenierie.c
                   |                            |om
             Status|NEW                         |NEEDINFO

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
I suppose the issue is that it would be duplicated a huge number of times no ?

How do you see the feature ?

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 61466] Adding samplers comment to SamplerResult could be interesting for reporters

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61466

Vincent HERILIER <vh...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|3.1                         |unspecified

-- 
You are receiving this mail because:
You are the assignee for the bug.