Philippe> idea: Philippe> - send a signal to pause, signal to resume. Threads would sleep and wakeup Philippe> on a based timer to see if they were resumed. We could even notify them
bug_49974> Allow to pause and resume tests Philippe, you asked for ideas, you get some. I wonder how that "pause/resume request" interferes with 1) JMeter debugger ( https://www.blazemeter.com/blog/how-debug-your-apache-jmeter-script ) 2) Some debugger API. Suppose one day there will be an IDE for JMeter. E.g. like the following: http://recordit.co/0ngw6RSkm9 It will probably require some debugger API (step in, step over, watch variables) from JMeter. Does it make sense to think more of a debugger API rather than standalone pause/resume? PS. I've absolutely no idea how Blazemeter's debugger works (as in "if debugger API is required from JMeter core") Vladimir
