Sure Vladimir :) As a performance engineer, I find it cumbersome to debug JMeter scripts.
Today, we all use the Debug Sampler, Writing to the log, Assertion message - in order to debug our scripts. It would be great if there will be a way (IMO) to have a debug listener which could: 1. Allow step by step debug 2. Allow us to see the current state of our variables 3. Allow us to change (on the fly) parameters without restarting the script 4. If a variable changed - by whom ? 5. Support the JMeter scoping rules 6. Include the view results tree in it for easier navigation 7. Support for multi thread display i.e - view each unique thread debug session 8. Export the current state to a file 9. Because it's a listener - support for headless run (which basically export to file each step) IMHO - I think, this will really help JMeter script developers :) On Mon, Mar 14, 2016 at 12:34 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > >I wanted to suggest an idea. > > Can you please describe the idea from "use case perspective"? > It is not clear what you mean behind "debug environment" > > For instance: > 1) As performance validation engineer, I have to debug JMeter scripts a lot > 2) "Debug sampler" does not help since ... > 3) The idea is ... > 4) Final end-to-end would be like ... > > Vladimir > -- Refael Botbol, BlazeMeter. Director of Professional Services
