[Bug 59157] New: Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

            Bug ID: 59157
           Summary: Add a new Menu Category called "Debug Listener"
           Product: JMeter
           Version: 2.13
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Main
          Assignee: issues@jmeter.apache.org
          Reporter: p.mouawad@ubik-ingenierie.com

Antonio Gomes Rodrigues proposed an idea which I find nice on a dev mailing
list discussion.

This idea is to create a Debug Listener and put in it:
- Assertion Results
- Comparison Assertions Visualizer
- View Results Tree
- View Results Table

This would make it easier for beginners to select the correct listener and
avoid the usual error to add a View Results Tree (leading to OOM).

Thoughts ?

I have implemented it and it could be commited before 3.0.

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

[Bug 59157] Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

--- Comment #4 from Alejandro <al...@gmail.com> ---
(In reply to Vladimir Sitnikov from comment #3)
> -1 for such a split.
Totally agree.

Those GUI-lovers, who will try to run multithreaded load test, will get OOM
despite that 'View Results in Tree' listener was added from 'Debug Listeners'
menu.
What than? Adding 'Turn Off Debug listeners' kind of button, making GUI more
cluttered?

> If the only aim of creating a debug listeners menu is to avoid OOM, then
> other ways should be explored:
> A1) Store just 50MiB of "View Results Tree" data, then start to drop new
> data.
+10 
As default setting for 'View Results Tree' listener, that will cover both
'debug' purpose and OOM prevention. 

> A2) Mark problematic listeners (and parent nodes in tree) with some kind of
> red.
Not sure that really will help. Those who run jmeter in non-GUI mode doesn't
need this at all, those who like to run load test in GUI ... i bet they will
ask for dedicated button.

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

[Bug 59157] Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

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

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

--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Created attachment 33657
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=33657&action=edit
Debug listeners

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

[Bug 59157] Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

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

[Bug 59157] Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

--- Comment #2 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
Created attachment 33658
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=33658&action=edit
Screenshot of Load Testing Listeners

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

[Bug 59157] Add a new Menu Category called "Debug Listener"

[bu...@apache.org]

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

--- Comment #3 from Vladimir Sitnikov <si...@gmail.com> ---
-1 for such a split.

1) Such a split would complicate day-to-day activities since noone would
remember which listeners are filed under which menu.

2) I'm not sure there is a consistent way to tell if a particular
listener is a "debug" listener or not.
In other words, "debuggness" of a listener might depend on the configuration.
For instance, "View results in tree" is somewhat fine if configured to log
errors only. 

3) I think UI should be designed around use cases.
I'm not sure there's a case like "I need a debug listener, thus I open
<<debug listeners>> menu".


If the only aim of creating a debug listeners menu is to avoid OOM, then other
ways should be explored:
A1) Store just 50MiB of "View Results Tree" data, then start to drop new data.
A2) Mark problematic listeners (and parent nodes in tree) with some kind of
red.

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