Bug 52307 - Add sample numbering option to View Results Tree
Summary: Add sample numbering option to View Results Tree
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.5.1
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-09 02:46 UTC by Colin Jackson
Modified: 2012-03-11 11:30 UTC (History)
2 users (show)



Attachments
Explanatory screenshot (258.83 KB, image/jpeg)
2012-01-19 20:09 UTC, Colin Jackson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Colin Jackson 2011-12-09 02:46:07 UTC
I often need to compare an entry in the View Results Tree component to a list of Thread-specific test data. This would be made much easier if the entries in the View Results Tree could be numbered. It is hard to identify the 1027th entry in the list in the current component, for example.
Comment 1 Sebb 2011-12-09 03:12:29 UTC
Not quite sure what you want: the title refers to Thread Number, but the comment seems to want a sequence number.

What is required?
Comment 2 Colin Jackson 2012-01-19 20:09:47 UTC
Created attachment 28178 [details]
Explanatory screenshot

This screenshot explains the change request more explicitly.
Comment 3 Colin Jackson 2012-01-19 20:17:32 UTC
Please see the explanatory screenshot. The list of results per thread in the results tree is not numbered. In this case, for example, if I attempt to login using 5000 user login details, and user 3276 fails, it's hard to determine which thread has failed, as they are not numbered, just coloured differently. I have to manually count through the list to see which number failed. If they were numbered, I could immediately cross-reference the thread number with the line number in my accounts spreadsheet and examine the failed user details. 

This numbering might not always work (for example, if the thread step being examined does not complete in the same order as the thread was started, or other random elements are in play), but in many circumstances it would be very useful.
Comment 4 Colin Jackson 2012-01-19 20:21:00 UTC
To clarify, I only need the items in the results tree to be numbered sequentially to aid identification. It is not necessary that these numbers are tied into an actual explicit thread number.
Comment 5 Sebb 2012-01-20 00:05:58 UTC
Have you tried using a Counter variable in the sampler label?
Comment 6 Colin Jackson 2012-01-20 08:02:52 UTC
>Have you tried using a Counter variable in the sampler label?

Hi Sebb, I don't know what you mean but I'll have a look into it. I'm not a power user by any means so I don't know some of the intricacies of what's possible.
Comment 7 Sebb 2012-01-20 12:08:49 UTC
Presumably you are using a variable reference in the sampler to pass in the user name?

Why not just add that to the sampler name, e.g. "Login ${user}"
Comment 8 Colin Jackson 2012-01-22 19:52:09 UTC
(In reply to comment #7)
> Presumably you are using a variable reference in the sampler to pass in the
> user name?
> 
> Why not just add that to the sampler name, e.g. "Login ${user}"

Great that worked fine. Thanks for the tip - it never occurred to me.
Comment 9 Colin Jackson 2012-01-22 20:00:14 UTC
> Why not just add that to the sampler name, e.g. "Login ${user}"

The problem with this for me, and also with including a counter variable, is that it forces each action in each thread to be listed separately in the Aggregate Report (as each has a different name, effectively). This pretty much renders the report useless, as I'd have a report with thousands of different summaries. 

I really need a way to number these actions per thread, but for it not to be a name change for the action, just a display feature, because of these knock-on effects in Listeners.