On 10 March 2016 at 06:59, Antonio Gomes Rodrigues <ra0...@gmail.com> wrote: > Hi, > > The goal is to split the listener menu in 2 menu: Listener / Debug Listener > > Put in Debug Listener all the Listener quoted by Philippe > > A Debug Listener is a listener used for debug purpose (debug the script) > like Assertion Results. > > Debug Listener = debug your script > > Listener = visualize the load test result > > > It will help the beginners because: > Debug Listener have Debug in the name. Debug = not to be used in a Load > test > Less choice because we have split it in 2 Menu. Less choice = easiest to > choose >
However twice as many Listener menu items. I suspect it will make things worse having two separate menu items for Listeners. Note also that for a Load test, the user should be using non-GUI mode in which case the Listener GUIs don't get called. And some Listeners that are useful for visualising the test result are expensive in memory terms. I am against this proposal. > Antonio > > 2016-03-10 0:24 GMT+01:00 sebb <seb...@gmail.com>: > >> On 9 March 2016 at 22:25, Philippe Mouawad <philippe.moua...@gmail.com> >> wrote: >> > Hello, >> > Antonio Gomes Rodrigues proposed an idea which I find nice on dev mailing >> > list discussion. >> > >> > This idea is to create a Debug Listener and put in it (at least that's >> what >> > I propose): >> > - 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 ? >> >> Sorry, I've no idea what you are suggesting here. >> What is a Debug Listener? >> How can it help beginners to select the correct Listener? >> >> > I have implemented it and it could be commited before 3.0. >> > >> > Regards >> > Philippe M >>
